Digest / March 5, 2026
Codex Issues Digest — March 5, 2026
66 new issues filed ·
26 resolved in openai/codex (UTC day).
New issues (66)
- Changes Aborted Hides Suggested Changes from View
- Codex app keep reconnection
- sandbox NextJS build goes for 20min+
- Codex app-server exited unexpectedly
- not able to response on even simple question
- resume sub-command and slash command should allow resuming a session from different path
- Oauth not working via CLI and Codex
- Slash command to compress conversation
- Codex app automations run at medium reasoning even when global model_reasoning_effort is xhigh
- Codex Windows app: Voice mode fails — “Unable to start dictation”
- Windows: bundled rg in Codex Desktop resolves on PATH but fails with Access Denied in integrated PowerShell
- Feature: Semantic narrative view as an alternative to raw execution logs
- Codex keeps stopping abruptly while running
- No slash pop-up prompts in vscode extension
- Windows app file references resolve to invalid c:\\C:\\ path and fail to open
- Codex App on Windows, when configured to use WSL, continues to reference the Windows-hosted config.toml
- Feature request: diff-like line focus and collapsible context for App source references
- Feature request: in-app fallback actions when source reference opening fails
- Rephrase ASCII requirement in system prompt: Generated content, not file encoding.
- Windows Store Codex app fails to start for Windows usernames containing non-ASCII characters.
- Entity-level merge for multi-agent parallel edits
- Bug: codex fails with "Missing optional dependency @openai/codex-linux-x64" on Ubuntu x86_64
- Codex App (WSL mode): Missing environment variable `AZURE_OPENAI_API_KEY` although variable exists in Windows and WSL
- quick switch between edit/think modes
- Do you want to make these changes? code changes prompt is absolutely useless!
- Markdown cant be rendered
- The conversation remained stuck in a thought process, unable to stop.
- Codex App (WSL mode on arm64 cpu not working)
- Codex Windows app (WSL): non-interactive shell doesn’t load NVM, so node/pnpm are missing from PATH (command not found)
- The week limit moved from March 9 to March 11 and usage did not get recalculated properly
- Usage dropping too quickly
- of type 'hidden_message' was provided without its required 'reasoning' item:
- Basic coding quality / AGENTS.md adherence issues
- 5.3 apply_patch fails under sandboxed default permission on Windows
- Error in Install from Microsoft Store with path unicode chars
- Inject worktree/root path environment variables into setup scripts
- [FEATURE] Preserve "Waiting" green pill until plan is responded to
- Support for pasting text with<Ctrl-v>
- NPM install blocked (403 / registry access)
- Ephrmale thread when starting a worktree
- VS Code extension 0.4.79: repeated thread-stream-state-changed warnings, missing tool-step streaming
- Smooth scrolling on Windows is hardcoded and can't be disabled
- Release-mode integration test fails to compile (core/tests/suite/view_image.rs missing wiremock imports)
- Feedback interrupted by permissions prompts in TUI
- WSL startup failure when /mnt/c automount disabled
- Windows App Freeze Bug
- Dictation stops (and appears to cancel) when command approval prompt appears during a session
- Restore immediate send on 'enter' and queueing of message via 'tab'
- Feature request: Limit Codex auto code review to default branch (or configurable branch allowlist)
- VS Code Codex: rename task in sidebar
- No file links on Unstaged screen
- brew codex 0.110.0 triggering Apple verification
- Display authorized commands
- gpt5.4 uses more limits than 5.3codex.
- /fast mode doesn't work
- [Feature Request] Add first-class Japanese language support (UI, docs, prompts)
- `codex exec --help` references `-a on-request` but `codex exec --ask-for-approval` is rejected
- Codex App worktree creation fails for WSL-backed repos with "Failed to resolve worktree git directory"
- wrong display result of context window after adjusting gpt5.4 to 1M context window size
- VS Code extension: wrong working directory after automatic context compaction
- Docs/schema mismatch: model_providers.<id>.wire_api default says 'chat' in docs but 'responses' in config schema
- Codex app: Display a badge count in the dock for awaiting approvals
- Cloud thread reply attaches to wrong local workspace
- bwrap: Can't mkdir .codex/memories: No such file or directory
- Accented characters not working in Codex on WSL2 terminal in VSCode
- Expose thread/read and thread/list as MCP tools for tool-only clients
Resolved issues (26)
- Codex deleted my entire Drive
- Not loading env vars from config.toml
- Codex app doesn't open in WSL with bash
- Codex app-server exited unexpectedly
- of type 'hidden_message' was provided without its required 'reasoning' item:
- "message": "Item 'rs_0e490cf22e7d78d4006981c96ea708819585b8e3e2caea0b9a' of type 'reasoning' was provided without its required following item.",
- invalid_request_error: reasoning item provided without required following item (Codex CLI 0.92)
- codex-rs/shell-escalation/README.md bash repo out of date (no longer public)
- resume sub-command and slash command should allow resuming a session from different path
- Slash command to compress conversation
- not able to response on even simple question
- Writing to an extremely large C++ file triggered Windows' command-line length limit
- No slash pop-up prompts in vscode extension
- Entity-level merge for multi-agent parallel edits
- `ansi` theme is rendered as explicit RGB colors instead of terminal ANSI palette indices
- Rephrase ASCII requirement in system prompt: Generated content, not file encoding.
- Markdown cant be rendered
- @filename autocomplete not working
- Basic coding quality / AGENTS.md adherence issues
- Feedback interrupted by permissions prompts in TUI
- Worktree feature for IDE
- of type 'hidden_message' was provided without its required 'reasoning' item:
- VS Code Codex: rename task in sidebar
- gpt5.4 uses more limits than 5.3codex.
- /fast mode doesn't work
- Restore immediate send on 'enter' and queueing of message via 'tab'