Digest / March 3, 2026
Codex Issues Digest — March 3, 2026
63 new issues filed ·
40 resolved in openai/codex (UTC day).
New issues (63)
- Missing CODEX_APP from Codex Workspace analytics usage
- User's access to gpt-5.3-codex-1p-codexswic-ev3 has been temporarily limited for potentially suspicious activity related to cybersecurity
- cyber security block
- gpt-5.3-codex usage benign cybersecurity flagging
- Cybersecurity rate limit
- Misidentified cybersecurity issue
- windows11 review failed
- This user's access to gpt-5.3-codex has been temporarily limited for potentially suspicious activity related to cybersecurity
- Benign perf comparison work resulted in `potentially suspicious activity related to cybersecurity`
- Incorrectly identified cybersecurity limit
- Cybersecurity Block for Benign Python Test Development Use
- TThis user's access to gpt-5.3-codex-1p-codexswic-ev3 has been temporarily limited for potentially suspicious activity related to cybersecurity
- temporarily limited for potentially suspicious activity related to cybersecurity.
- 5.3 access revoked and flagged
- stream disconnected before completion: This user's access to gpt-5.3-codex-1p-codexswic-ev3 has b een temporarily limited for potentially suspicious activity related to cybersecurity.
- access limited for safety check
- `stream disconnected before completion: This user's access to gpt-5.3-codex-premium-1p-codexswic-ev3 has been temporarily limited for potentially suspicious activity related to cybersecurity` false positive error
- access to gpt-5.3-codex-premium-1p-codexswic-ev3 blocked?
- Memory not reclaimed after codex-cli exits in non-interactive mode
- Cybersecurity false positive
- This user's access to gpt-5.4-ab-arm3-840-1p-codexswic-ev3 has been temporarily limited
- Drain Faster 5 hour usage limit Weekly usage limit
- Temporary cybersecurity restriction – review request (Thread ID: 019cb08e-466a-73c2-8b98-d64723a6602a)
- Working on my app, a wrapper, and got flagged for potentially suspicious activity.
- codex extension in vscode can not use slash command
- Upgrading plan to pro after reaching usage limit for plus doesn't reset the 5hr window usage limit. Unable to continue.
- the codex no response
- Codex app reseting weekly usage not at reported time from /status
- Windows client
- fetch/rebase is blocked by network policy in Codex Web
- CLI: resume/fork on WSL can restore lowercased cwd from SQLite-normalized path
- Codex Desktop cloud task creation fails (Internal Server Error) while CLI/web succeed
- Regression on Windows in v0.4.79: `absolute_path:line:column` no longer opens file location (worked in v0.4.73)
- windows: All shell commands crash with "Could not load netstandard 2.0.0.0" at PowerShell startup stage
- Authentication fails in VS Code Remote-WSL (works locally on Windows)
- [VS Code extension][Windows 11] Streaming UI stalls/no token-by-token updates; repeated `thread-stream-state-changed` broadcasts with no handler
- Synchronously add update notes for each Codex IDE release
- Cannot manually set Codex language to English
- Suggestion: add an optional troubleshooting reference for context, retrieval, and multi-step agent workflow failures
- Command for deleting conversation history
- Flag --worktree to create a new worktree inside `.codex/worktree`
- Codex app shows: Reconnecting... 1/5 stream disconnected before completion: This user's access to gpt-5.4-ab-arm1-1020-1p-codexswic-ev3 has been....
- A sandbox mode that restricts file access but allows free network access (with or without cached web searches)
- False negative repo detection: reports no git repo in directory with .git
- Deeper worktree config options and worktree subthreads
- Bug: @ file picker surfaces .git refs/logs entries
- let codex use different models for subagents
- {"detail":"Bad Request"} after codex cli update
- Codex App does not honor `[sandbox_workspace_write] network_access = true` from `config.toml` (works in CLI)
- I keep getting ■ {"detail":"Bad Request"} in most of my threads
- Support Plan mode in the CLI and TS SDK
- v0.107.0 Windows Sandbox ACL Failure (Error 5) and Unintended Permission Pollution on User Home Directory
- VSCode Codex chat stuck on "thinking" after system crash
- Codex TUI's Bug Report Links Still Broken
- Unclear if Codex is working
- AGENTS.md is silently truncated and instructions near the end ignored
- Worktree indicator / dropdown menu in Codex App (next to the branch)
- Codex prompts per-file permission when worktree differs from opened folder
- Worktree feature for IDE
- Codex should never read or print environment variables
- Elicitation support
- ChatGPT-auth websocket connect to chatgpt.com hangs before upgrade; local diagnostics point to IPv6-first address selection
- Configurable App Server WebSocket port/endpoint to connect from VS Code to a Codex instance running inside a Dev Container (one container per worktree)
Resolved issues (40)
- Cybersecurity Block for Benign Python Test Development Use
- This user's access to gpt-5.4-ab-arm3-840-1p-codexswic-ev3 has been temporarily limited
- Cybersecurity false positive
- access to gpt-5.3-codex-premium-1p-codexswic-ev3 blocked?
- `stream disconnected before completion: This user's access to gpt-5.3-codex-premium-1p-codexswic-ev3 has been temporarily limited for potentially suspicious activity related to cybersecurity` false positive error
- access limited for safety check
- stream disconnected before completion: This user's access to gpt-5.3-codex-1p-codexswic-ev3 has b een temporarily limited for potentially suspicious activity related to cybersecurity.
- 5.3 access revoked and flagged
- temporarily limited for potentially suspicious activity related to cybersecurity.
- TThis user's access to gpt-5.3-codex-1p-codexswic-ev3 has been temporarily limited for potentially suspicious activity related to cybersecurity
- Incorrectly identified cybersecurity limit
- This user's access to gpt-5.3-codex has been temporarily limited for potentially suspicious activity related to cybersecurity
- Misidentified cybersecurity issue
- Cybersecurity rate limit
- gpt-5.3-codex usage benign cybersecurity flagging
- cyber security block
- User's access to gpt-5.3-codex-1p-codexswic-ev3 has been temporarily limited for potentially suspicious activity related to cybersecurity
- Benign perf comparison work resulted in `potentially suspicious activity related to cybersecurity`
- Temporary cybersecurity restriction – review request (Thread ID: 019cb08e-466a-73c2-8b98-d64723a6602a)
- Shortcut to clear Terminal in Codex App
- Working on my app, a wrapper, and got flagged for potentially suspicious activity.
- codex extension in vscode can not use slash command
- Codex app reseting weekly usage not at reported time from /status
- Upgrading plan to pro after reaching usage limit for plus doesn't reset the 5hr window usage limit. Unable to continue.
- Windows client
- Cannot manually set Codex language to English
- Suggestion: add an optional troubleshooting reference for context, retrieval, and multi-step agent workflow failures
- Flag --worktree to create a new worktree inside `.codex/worktree`
- Command for deleting conversation history
- Add automatic lifecycle cleanup for completed/idle sub-agents (and unused MCP clients)
- CLI: resume/fork on WSL can restore lowercased cwd from SQLite-normalized path
- Codex app shows: Reconnecting... 1/5 stream disconnected before completion: This user's access to gpt-5.4-ab-arm1-1020-1p-codexswic-ev3 has been....
- Apply_Patch is not working at all on windows system
- False negative repo detection: reports no git repo in directory with .git
- {"detail":"Bad Request"} after codex cli update
- let codex use different models for subagents
- Model sees [Pasted Content N chars] placeholder rather than the actual pasted content
- Memory not reclaimed after codex-cli exits in non-interactive mode
- Codex TUI's Bug Report Links Still Broken
- Codex should never read or print environment variables