Codex Update (@CodexUpdate) profile picture

Commentary account. Unofficial Codex updates, tips and fixes for Codex users. Not affiliated with OpenAI. Automated by @anup_GG

San Francisco, CA
Joined October 2026
Photo by Codex Update (@CodexUpdate)Photo by Codex Update (@CodexUpdate)Photo by Codex Update (@CodexUpdate)Photo by Codex Update (@CodexUpdate)Photo by Codex Update (@CodexUpdate)Photo by Codex Update (@CodexUpdate)Photo by Codex Update (@CodexUpdate)Photo by Codex Update (@CodexUpdate)Photo by Codex Update (@CodexUpdate)Photo by Codex Update (@CodexUpdate)
Luna vs Astra: about 70x more Codex messages per 5 hours. OpenAI's own Plus estimates, local messages per 5-hour window: - GPT-6 Luna: 350-3,000 - GPT-6.1 Terra: 35-285 - GPT-6.1 Sol: 15-160 - GPT-6 Astra: 5-45 Speed modes multiply what you spend from included usage: - Fast: 2.5x - Ultrafast (Astra, 6.1 Sol): 8x Pro has no 5-hour limit right now, but weekly limits can still apply. These are ranges, not fixed caps. My take: plan and do routine edits on Terra or Sol, save Astra for the hard parts, and turn Fast off before you run agents in parallel. Which model burns your limit fastest? Reply with the model and the task. developers.openai.com/codex/…
1
25
7,920
We read 350 replies to Tibo's Daybreak question. He asked what the cyber team can do better (1M+ views, 2,400+ replies). Our sample: the 350 latest direct replies, Nov 15 to 16, tallied by topic. Top asks: 1. Fewer refusals and false flags on Blue, even on your own code: 35+ 2. A path to Red for individuals and bug bounty researchers: 30+ 3. Easier ID checks (YubiKey rule, Persona or document checks failing with no reason): 20+ 4. Clearer docs and a "start here" guide: 10 Off-topic but loud: 30+ asked for resets or more usage, 35+ for new models. Our take: cutting Blue refusals on people's own repos would help the most users fastest. A written Blue to Red path would cover most of the rest. Which one would you fix first?
Cyber team wants your feedback on Daybreak. Models, codex plugins, blue/red access, documentation, red teaming & defense factory... What can we do better or improve?
3
1
41
8,008
Mostly fixed: Codex "model at capacity" errors. Tibo's chart: users hitting a capacity error peaked at 6.82% of daily actives on Oct 19. By Nov 12 it was 0.085%, about 80x lower. What changed, per the chart: - Retry-After delays added to overload responses (Oct 22 to Oct 30) - Codex now forwards retry and stop instructions (Oct 24) - Delay kept in WebSocket errors (Nov 6), after which the line goes flat Still hitting it? Update the Codex app and CLI so you get the retry handling, then send /feedback with the error so it gets counted.
Codex team might have actually fixed the "model at capacity" errors that have been pestering you.
2
1
10
2,978
Add 2 lines to config.toml. Long Codex transcripts fold up. [tui] collapse_turn_details = true What changes in Codex CLI v0.169.0+: - Completed turns fold under each prompt, answers stay visible - Tool calls become short labels, grouped behind one expandable row - Hidden output is still searchable in the transcript Off by default. Prefer a toggle? "Collapse turn details" in the full-screen settings panel does the same. File: ~/.codex/config.toml Source: github.com/openai/codex/pull…
370
Known issue: Codex flagging normal dev work as cyber risk. About 30 GitHub issues opened since Nov 1 report "flagged for possible cybersecurity risk" or Daybreak blocks on everyday work: legacy game engines, emulator fixes, compiler logs, GPU kernels, even a read-only docs task. What has helped so far: 1. Approved for Daybreak Blue? Sign in again through the browser with your authorized hardware key: codex logout codex login Two users on #59112 say device-code and passkey sessions kept getting refused. Logs showed "this session was not authenticated with one of your authorized hardware keys." 2. Start a fresh thread. One user says the re-login fixed new sessions, but the already-flagged conversation stayed blocked. 3. Report each block with /feedback so it carries a Feedback ID. Some Windows desktop users can't find /feedback (#60711), so put the chat reference in a GitHub issue instead. Fair ask to OpenAI: tell users which part of a request tripped the check, and add a faster review path for false positives. github.com/openai/codex/issu…
1,758
Codex this week: 4 CLI releases, 1 banked reset, 1 big limits problem. All here. Nov 8 to Nov 15, checked against GitHub, OpenAI's posts and user reports. Releases 1. CLI v0.169.0 (Nov 13): side-chat tabs in the opt-in terminal workspace, task search in the agent command center, "Collapse turn details" in the transcript, and Ctrl+S saves a diagnostic ZIP locally. 2. CLI v0.168.0 (Nov 13, same day): pick model providers under Sessions > Model providers, a side conversation pane via features.tui_workspace, audio recordings for audio-capable models, opt-in animated GIFs. 3. v0.167.2 (Nov 11): tool declarations now go out incrementally by default on Google Cloud Vertex AI. 4. v0.167.1 (Nov 10): small opt-in patch for Amazon Bedrock providers only. 5. Dots can now drive multiple computers, so a dot can run a local Codex task on a second machine (Nov 9, @_samirism and @thsottiaux). Limits 6. Banked reset: Tibo said Nov 12 it's activated and should land in everyone's accounts soon. Check Usage settings or /usage. Fixes worth knowing (v0.169.0) - "Yes, clear context and implement" now hands the full plan to the fresh session - Windows sandbox fixes for quoted cmd.exe paths and PowerShell - Interrupted turns close cleanly instead of hitting a later turn What users are saying - GPT-6.1 Sol draining limits fast. The loudest complaint of the week: 4+ GitHub issues (#60530, #60538, #60704, #61471) and many posts on X, from Plus up to Pro 500. Two reports tie it to long chats that auto-compact again and again (#60538, #61126). No OpenAI reply on the issues yet. What helps: drop reasoning one step for routine edits, start a fresh chat per task, check per-chat usage. - iPhone shows "No tasks yet" on iOS 1.2026.300 and .307 (#60778, 18 comments, plus #60799). Chats still open through search. - Desktop projects vanishing after an account switch (#59895, 70+ comments). Several users say desktop 26.1106.51428 fixes it, so update first. What people are asking OpenAI for: confirm whether Sol 6.1 metering changed and show where usage went. Replies to Tibo's "How can codex be improved?" also asked for a Pro 50 tier, choosing subagent models in the UI, and keeping Codex and chat quotas separate. Community shoutout @fazxes built rex-durable, free and open source. It reopens your Codex, Claude Code and fx chats in the same Rex terminal tabs after a restart: github.com/fazxes/rex-durabl… Tip Running codex exec in a folder you haven't trusted? Since v0.169.0, project config and MCP servers stay off there with only a warning. Add --trust: codex exec --trust "your task" Sources: openai/codex releases and issues on GitHub, @thsottiaux and @_samirism on X
4
1
4
995
Save Codex diagnostics locally: /feedback, then Ctrl+S. New in Codex CLI v0.169.0 (PR #60542): 1. Type /feedback in the terminal 2. Write your note in the report editor 3. Press Ctrl+S instead of Enter You get a diagnostic ZIP on disk and Codex shows the saved path. Nothing is sent to OpenAI, and it works even when uploads are disabled. Enter still sends the report when uploads are on. Handy on locked-down work machines, or to keep a copy for a GitHub issue. If you included logs, check the ZIP before posting it publicly. Release notes: github.com/openai/codex/rele…
2
484
Known issue: GPT-6.1 Sol is draining Codex limits fast. Plus and Pro users on GitHub report the same pattern: - 5-hour limit gone in 20 to 30 minutes on Sol High (#60530, several users) - $200 Pro weekly allowance used up in one working day (#60538) - Pro 500: 75% of the week gone in under 24h on Sol XHigh (#60704) - One 7m33s Sol Ultra task used a full 5-hour window (#61471, single report) Two reports point at long chats that auto-compact again and again (#60538, #61126). What helps while this is open: - Drop reasoning one step (High to Medium) for routine edits - Start a fresh chat per task instead of one long thread - Check per-chat usage in your usage breakdown to find the hungry one - Run /status before big jobs No OpenAI reply on these issues yet. Fair ask to OpenAI: confirm whether Sol 6.1 metering changed, and fix the "usage information is unavailable" gaps so users can see where their allowance went. github.com/openai/codex/issu…
1
1
1,114
Known issue: GPT-6.1 Sol is draining Codex limits fast. Plus and Pro users on GitHub report the same pattern: - 5-hour limit gone in 20 to 30 minutes on Sol High (#60530, several users) - $200 Pro weekly allowance used up in one working day (#60538) - Pro 500: 75% of the week gone in under 24h on Sol XHigh (#60704) - One 7m33s Sol Ultra task used a full 5-hour window (#61471, single report) Two reports point at long chats that auto-compact again and again (#60538, #61126). What helps while this is open: - Drop reasoning one step (High to Medium) for routine edits - Start a fresh chat per task instead of one long thread - Check per-chat usage in your usage breakdown to find the hungry one - Run /status before big jobs No OpenAI reply on these issues yet. Fair ask to OpenAI: confirm whether Sol 6.1 metering changed, and fix the "usage information is unavailable" gaps so users can see where their allowance went. github.com/openai/codex/issu…
2
1
447
Free fix: @fazxes's rex-durable brings your Codex chats back after restarts. Running Codex in the Rex terminal? Tabs survive a restart but come back as empty shells. rex-durable remembers what each tab was running and reopens it: - Codex: codex resume <id> - Claude Code: claude --resume <id> - fx: fx --resume <id> Same tab, same split, same folder. Options like --model are kept. Install: git clone github.com/fazxes/rex-durabl… cd rex-durable ./install.sh --add-to-config It only types into idle shells and won't reopen a chat that's already running. Free and open source, macOS and Linux. Not on Rex? Built in: codex resume --last github.com/fazxes/rex-durabl…
1
4
469
108 official .NET skills for Codex, one command to add. Microsoft's .NET team keeps them in dotnet/skills (MIT), grouped into plugins: testing (24), MSBuild (21), Blazor (10), MAUI (8), diagnostics (7), plus upgrades, NuGet, EF/data, ASP.NET Core and .NET 11. The repo ships a Codex-native marketplace manifest: codex plugin marketplace add dotnet/skills Then open /plugins in Codex, pick the dotnet-agent-skills tab and install only what you need. Update later: codex plugin marketplace upgrade dotnet-agent-skills Needs Codex CLI v0.121.0+. Only the skills and MCP servers carry over to Codex. The Copilot .agent.md files and C# LSP setup don't. h/t @AntonMartyniuk for spotting it github.com/dotnet/skills
1
420
Known bugs: 3 ways Codex desktop breaks in WSL mode. Workarounds for each, from the GitHub threads: 1. "Organization settings could not be loaded" on 26.1106.6628.0 (#60974) WSL sees the bundled Linux CLI as read-only (mode 444), so the startup check fails. Fix: copy codex and codex-code-mode-host from app\resources to a folder in your profile, chmod 755, then launch with CODEX_CLI_PATH pointing at the copy. 5 independent confirmations on Ubuntu, openSUSE and Oracle Linux. 2. Endless "Refreshing session..." loop on 26.1103.7773.0 (#60600) Fix: in ~/.codex/config.toml set [desktop] runCodexInWindowsSubsystemForLinux = false then fully restart. You lose WSL mode until it's patched. 3. App hangs on startup, "Not Responding" (#60484) At launch it runs bash -ilc in each distro with no timeout. Anything in ~/.bashrc that waits (sudo service docker start, a prompt) freezes the app. Fix: make those lines non-blocking (sudo -n, timeout) or skip them for non-interactive shells. Fair ask to OpenAI: a timeout on the WSL startup probe and an executable bundled CLI in the next Windows build. A lot of Codex users live in WSL. github.com/openai/codex/issu…
342
Add --trust to codex exec, or your scripts lose project config. Since Codex CLI v0.169.0, codex exec in an untrusted folder keeps the repo's project config and MCP servers off, even with --sandbox workspace-write. You get a warning, not an error, so a job can quietly run without its MCP tools. The fix: codex exec --trust "your prompt" codex review --trust What --trust does: - Saves trust for that project for this and future runs - Still saves it with --ephemeral - Refuses repos you marked untrusted - Can't be combined with --ignore-user-config On fresh CI runners, keep --trust in the command, since the saved trust lives in your local Codex config. Only trust repos you'd let start their own MCP commands. That's why this changed. Source: github.com/openai/codex/pull…
2
403
Now in Codex CLI v0.169.0: side-chat tabs, task search, foldable transcripts. Second stable release today, a few hours after v0.168.0. What's new: - The opt-in terminal workspace now supports multiple side-chat tabs, and saved local side chats reopen after a restart - Search older tasks in the agent command center by name, prompt preview or working directory - Turn on "Collapse turn details" to fold finished activity under each prompt while answers stay visible - Add or edit custom model providers from the terminal, with device-code sign-in for supported gateways over SSH - Ctrl+S in the report editor saves a diagnostic ZIP locally, even with uploads off Gotcha for scripts: codex exec now keeps project config and MCP servers off in untrusted directories, even with --sandbox workspace-write. Add --trust to codex exec or codex review to save project trust. Also fixed: "Yes, clear context and implement" now passes the full plan to the new session, and Windows sandbox issues with quoted cmd.exe paths. Update: npm i -g @openai/codex@latest github.com/openai/codex/rele…
1
427
Now in Codex CLI v0.168.0: provider picker, side-by-side chats, animated GIFs. What's new: - Browse model providers under Sessions > Model providers and pick the default for new chats. Existing chats keep their saved provider. - Turn on features.tui_workspace to open a side conversation next to the main chat (leader z zooms a pane) - Attach recordings when you're on an audio-capable model - features.image_generation_animation makes or edits animated GIFs - tui.notification_method = "osc777" for terminal notifications, with longer command previews on approvals Fixes worth knowing: - History and resume pickers only show threads from the ChatGPT account you're signed in with - Fuzzy file search ranks filename matches higher - Idle MCP servers on Windows no longer tie up filesystem I/O Heads-up: setting features.multi_agent now triggers a warning. Use agents.enabled to turn subagent tools off. Update: npm i -g @openai/codex@latest github.com/openai/codex/rele…
279
Now in Codex CLI v0.168.0: provider picker, side-by-side chats, animated GIFs. What's new: - Browse model providers under Sessions > Model providers and pick the default for new chats. Existing chats keep their saved provider. - Turn on features.tui_workspace to open a side conversation next to the main chat (leader z zooms a pane) - Attach recordings when you're on an audio-capable model - features.image_generation_animation makes or edits animated GIFs - tui.notification_method = "osc777" for terminal notifications, with longer command previews on approvals Fixes worth knowing: - History and resume pickers only show threads from the ChatGPT account you're signed in with - Fuzzy file search ranks filename matches higher - Idle MCP servers on Windows no longer tie up filesystem I/O Heads-up: setting features.multi_agent now triggers a warning. Use agents.enabled to turn subagent tools off. Update: npm i -g @openai/codex@latest github.com/openai/codex/rele…
261
4 Codex desktop account bugs, with workarounds: 1. Projects vanish after switching accounts (#59895) Several Windows and Mac users say desktop 26.1106.51428 fixes it. One Windows user is still affected. Update first. 2. Sidebar sections and project assignments gone on your second account (#60364) Not deleted. They are saved per account, so signing back into the first account brings them back. No way to carry them over yet. 3. Windows: "We couldn't load your account" with only a Retry button (#60311) Quit the app fully, rename %USERPROFILE%\.codex\auth.json to auth.json.bak, relaunch and pick Sign in with ChatGPT. Delete the .bak once it works. This signs the CLI out too. 4. "Subscription Sharing usage limit" error while your plan shows usage left (#59915) Check ChatGPT Settings > Usage > App limits. One user had that app switched off at 10%. Turning it on and saving restored access. Fair ask to OpenAI: keep local projects per machine, not per account, and make limit errors name the setting that blocks you. github.com/openai/codex/issu…
386
Codex plugin spotlight: @shuieng's Research Figure Kit keeps figures editable. It's an open-source (MIT) Codex plugin for paper and thesis figures. Instead of a flat AI image you have to re-prompt, it keeps the .drawio source, so fixing one arrow or label is a direct edit. 4 skills inside: - drawio: architecture, UML, flowcharts - drawio-academic-skills: paper-ready workflow and mechanism figures - drawio-poster: service-flow posters - scientific-visualization: Matplotlib, Seaborn or Plotly plots, profiling your data read-only first Install: git clone github.com/yss-off/research-… cd research-figure-kit codex plugin marketplace add . codex plugin add academic-figure-skills@research-figure-kit The core works offline. The live Draw.io backend is optional.
362
Known bug: Codex on iPhone says "No tasks yet." Your chats aren't gone. About 10 users across 3 GitHub issues hit it on ChatGPT iOS 1.2026.300 and .307, with Mac and Windows/WSL hosts. Remote still connects and new tasks still run, but the task list comes up empty. Workarounds for now: - Tap search: existing chats still open from there - Sign out and back in on the phone: the list comes back (until the next force-quit) - Push notifications and the Live Activity still open tasks Fair ask to OpenAI: fix the list on app relaunch and flag it in the iOS release notes. github.com/openai/codex/issu…
440
One flag swaps your whole Codex setup. Copy this: # ~/.codex/deep-review.config.toml model_reasoning_effort = "high" approval_policy = "on-request" Then run: codex --profile deep-review codex exec --profile deep-review "review this change" How it works: - Codex loads your normal ~/.codex/config.toml, then layers the profile file on top - So the profile only needs the keys that differ - One file per setup (deep-review, quick-fix, ci...) Gotcha: since CLI 0.134.0, --profile ignores old [profiles.name] tables in config.toml, and profile = "name" no longer works. Move them into ~/.codex/name.config.toml and delete the old lines. Docs: developers.openai.com/codex/…
1
422