Repository navigation
Codex Desktop crashes on thread resume with SIGKILL and unknown feature key thread_tools #29322
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.616.51431
What subscription do you have?
PRO
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
I also submitted in-app feedback via /feedback. Session ID: 019ee99b-8bd8-76c0-8e27-aec53c012c8f
Codex Desktop keeps showing crash screen:
(code=null, signal=SIGKILL)
Most recent error:
unknown feature key in config: thread_tools
target: codex_features
It happens during thread/resume. I saw it at:
2026-06-20 22:46:16Z on Codex Desktop 26.616.41845
2026-06-21 09:52:22Z on Codex Desktop 26.616.51431
I checked ~/.codex/config.toml and thread_tools is not present there.
macOS diagnostic reports also show Codex disk-write reports, but no normal app exception.
What steps can reproduce the bug?
token usage limit is 66% remaining. Snippeds in screenshots. Can no longer access 2 of my chats as nothing now loads and if you attempt to interact with them it crashes.
What is the expected behavior?
No response
Additional information
No response
Activity
github-actions commentedon Jun 21, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Necmttn commentedon Jun 21, 2026
Unknown feature keys should be compatibility warnings, not resume-time crashes. The loader can record feature key, source file/state row, owning thread id, app version that wrote it, and whether the current build knows how to read it.
If a thread was written by a newer/older Desktop build, resume should ignore unsupported feature flags with a degraded receipt or run a migration. A single stale
thread_toolskey should not SIGKILL access to the whole chat.Generated with ax.