Digest / March 23, 2026
Codex Issues Digest — March 23, 2026
51 new issues filed ·
28 resolved in openai/codex (UTC day).
New issues (51)
- After running the Codex APP in Win11 for a long time, the client freezes severely, causing the whole machine to freeze severely
- Feature Request: Built-in Remote Session Management and Interactive Prompts
- Add cursors to `thread/read` in the codex app-server
- Expose CollabAgentSpawn{Begin,End} as hook events
- Popup window stays above macOS IME candidate window while typing
- Falling back from WebSockets to HTTPS transport. Token data is not available.
- codex stuck after switching network
- Expose AfterToolUse in hooks.json and support codex_hooks on Windows
- Codex
- Authorization header lost when falling back from WebSocket to HTTPS with custom openai_base_url
- Persisted session titles can become multi-kilobyte prompt blobs
- Switching model_provider hides existing local sessions from resume/fork/history
- Windows App WSL: Opening Codex causes ubuntu to not be able to execute .exe files
- Sandbox failure on Linux (bwrap loopback RTM_NEWADDR error) in 0.116.0
- Support suppressing hook status messages in TUI (suppressOutput is a no-op)
- 【 vsCode Extension】Adding line numbers from different files as input context is not supported.
- Bug: Markdown local file links render percent-encoded non-ASCII paths in transcript output
- "Open in Rider" leads to Rider-sided exception
- spawn_agent model override to gpt-5.4-mini is ignored; spawned subagent runs as gpt-5.4
- Codex CLI auth.json copy flow is broken: refresh succeeds but session still rejected (docs misleading)
- CPU spikes during normal use
- VS Code: support external workflow / local-controller notifications into Codex sessions
- .git is mounted read-only even though Codex is configured for workspace-write
- Add a --proxy flag to the app-server launch parameters
- Sandboxed tool calls fail on Ubuntu 22.04 bubblewrap 0.6.1 because codex-linux-sandbox always passes --argv0
- MCP tools disappear in existing Codex sessions after reload or time, but work in new sessions
- Weird symbols and lines being printed in terminal on each answer
- Extremely high token burn: 13.6K tokens wasted on a single "Hi"
- bwrap namespace error when using apply_patch
- Permissions button labels should be verbs, not "Yes" or "No"
- Mysterious Exec usage eats entire 5h and weekly budget in 30 minutes upon reset
- codex exec -s read-only allows filesystem writes when nested under external sandbox
- Nested codex exec commands inherit parent CODEX_THREAD_ID instead of nested thread id
- apply_patch in nested read-only exec misreports in-project files as outside of the project
- Add ability to rename Codex chat/session titles (CLI + VS Code)
- codex sandbox linux --full-auto reports successful writes that do not persist to host filesystem
- codex exec --help advertises a second positional [COMMAND] but parser rejects it
- codex exec exits 0 even when command_execution fails with nonzero exit code
- codex exec resume silently starts a new thread when given an ephemeral session id
- codex exec resume accepts nonexistent session ids and starts a new thread instead of failing
- codex exec review --skip-git-repo-check scans child repos when run outside Git
- codex apply help hides Cloud task semantics and lacks --attempt parity with codex cloud apply
- codex cloud list --json hides missing cloud environments as an empty task list
- codex cloud fails with opaque 'Permission denied (os error 13)' when run headlessly
- Sandbox failure on Ubuntu 22.04: bwrap --argv0 not supported (bubblewrap 0.6.1)
- Regression: Recent fix results in limit to 1 New Codex Agent window
- Compact Error
- codex is using random other tools to do file system manipulations like gh cli and chrome (it did an ls by opening the local folder in chrome)
- Hyphenated MCP server names cause working servers to render as 'Tools: (none)'
- Thread closes when PowerShell integrated terminal exits (Windows native agent)
- Command T to switch conversation tabs
Resolved issues (28)
- Feature Request: Built-in Remote Session Management and Interactive Prompts
- Automatic approval review failed: guardian review completed without an assessment payload
- Codex
- Codex created a GitHub repository as public without explicit visibility instruction
- Falling back from WebSockets to HTTPS transport. Token data is not available.
- Expose AfterToolUse in hooks.json and support codex_hooks on Windows
- Proposal: add PreToolUse/PostToolUse lifecycle hooks to Codex hooks engine
- Sandbox failure on Linux (bwrap loopback RTM_NEWADDR error) in 0.116.0
- 【 vsCode Extension】Adding line numbers from different files as input context is not supported.
- Persisted session titles can become multi-kilobyte prompt blobs
- Sandboxed tool calls fail on Ubuntu 22.04 bubblewrap 0.6.1 because codex-linux-sandbox always passes --argv0
- spawn_agent model override to gpt-5.4-mini is ignored; spawned subagent runs as gpt-5.4
- Weird symbols and lines being printed in terminal on each answer
- Extremely high token burn: 13.6K tokens wasted on a single "Hi"
- Sandboxed tool calls fail on Ubuntu 20.04 with bubblewrap 0.4.0 ('bwrap: Unknown option --argv0')
- Mysterious Exec usage eats entire 5h and weekly budget in 30 minutes upon reset
- Add ability to rename Codex chat/session titles (CLI + VS Code)
- codex exec review --skip-git-repo-check scans child repos when run outside Git
- codex apply help hides Cloud task semantics and lacks --attempt parity with codex cloud apply
- codex cloud list --json hides missing cloud environments as an empty task list
- codex cloud fails with opaque 'Permission denied (os error 13)' when run headlessly
- Sandbox failure on Ubuntu 22.04: bwrap --argv0 not supported (bubblewrap 0.6.1)
- Regression: Recent fix results in limit to 1 New Codex Agent window
- Compact Error
- codex is using random other tools to do file system manipulations like gh cli and chrome (it did an ls by opening the local folder in chrome)
- Cosmético
- Urgent pending data loss, Sora 1, all other support channels broken
- Bottom row of controls can get squished, not responsive