18 people reported
All time, since Oct 3, including 14 thumbs-up on GitHub.
Stale thread_context warning
“Desktop logs show the warning recurring alongside local thread initialization/resume after restarting.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/10950/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Deprecated thread_context warning persists with clean config.toml.
Is this your bug?
File my report- Where
- Desktop app settings
- Error text
[features.guardianv2].thread_context is deprecated and ignored. Thread-owned Guardian context is always enabled. Remove thread_context from [features.guardianv2] in config.toml, including profile overrides.- Versions
- 0.162.0 to 26.1013.31256
- Platforms
- macOS, Windows
- How bad
- Cosmetic: looks wrong, still works.
Not quite your bug?
- Unrecognized thread_tools warning9 people
- Approval table flagged as ignored3 people
- Invalid codex_app MCP transport3 people
Original reports5, newest first
- Deprecated thread_context warning persists despite setting being absent from user configOn GitHub#54502
- Codex configuration warning under settingsOn GitHub#54499
- [App] Deprecation notice for [features.guardianv2].thread_context cannot be removed when injected by enterprise/cloud-managed policyOn GitHub#53293
- Windows Desktop: unknown injected code_mode_tool_description_first and opaque forced-cleanup denialOn GitHub#52747
- Desktop: Guardian experiment reintroduces deprecated thread_context despite clean config.tomlOn GitHub#50526