Community Page | Fastest & Truthful Updates on Codex
San Francisco, CA
Joined October 2026
- Tweets328
- Following133
- Followers970
- Likes191
Banked reset 1 of 2 is live. Tibo just dropped Day 27 of the 28-day run.
It won't refill anything by itself. You redeem it:
- Desktop app: Settings > Usage & billing
- Web: Usage settings
- CLI: /usage, then Redeem reset
- Not available in the mobile app
What it restores: Plus and Business get the 5-hour and weekly allowances back, Pro gets the weekly. Your weekly reset date moves to the day you use it.
Save it until you need it. It only redeems once an allowance is under 80% remaining, and it expires, so check the date shown in Usage.
How it works: help.openai.com/en/articles/…
Track your Codex token burn before December's shared pool.
From December, Plus, Pro and Business share one token-based allowance across ChatGPT and Codex (per OpenAI's help page). Get a baseline now in the Codex CLI:
/usage daily
/usage weekly
/usage cumulative
Live limits in your footer:
/statusline, then toggle rate limits and context stats
Per-session check:
/status shows model, context left and token usage
/usage is also where you redeem an earned reset if you have one.
Bigger models and complex tasks burn more, so a week of numbers tells you if your plan still fits.
Docs: developers.openai.com/codex/…
Confirmed: ChatGPT and Codex will share one usage limit from December.
OpenAI's help page, updated today:
- Plus, Pro and Business get one allowance across ChatGPT and Codex
- Usage is measured in tokens, so bigger models and harder tasks burn more
- Instant chat doesn't count against it
- Combined remaining usage and reset times will show in Settings > Usage
- Hit the cap and you wait, upgrade, or buy credits
OpenAI says most users won't hit resets more often than now. If you run long Codex sessions and lean on ChatGPT too, plan for both drawing from the same pool.
Fair ask to OpenAI: publish the token allowance per plan before December so people can check the maths.
help.openai.com/en/articles/…
Right, we're an independent account for Codex users, not OpenAI. Everything in the post comes from OpenAI's own help page, linked at the bottom.
The help page doesn't define "device," so nobody can promise separate Linux users count separately. It does say shared or public devices can hit the limit even when each person uses their own account, and to tell Support if you share one. Business workspace seats don't count toward it.
Existing subs can stay: more on Codex device limits.
Lots of you asked follow-ups, so here's what else OpenAI's help page says:
- Subscriptions bought before the limits took effect "can continue under the existing-subscription exception"
- Cancel one of them and there's no guarantee you can replace it
- Blocked at sign-in? The warning offers cancel + refund for ChatGPT and Google Play purchases. Apple buyers request it through Apple
- A shared household or public device, or one card used by several people, can trip the limit too. Tell Support if that's you
- The exact number of paid accounts per device isn't published
Fair ask to OpenAI: publish that number, so people know before they pay.
help.openai.com/en/articles/…
Heads-up: stacking paid accounts on one machine for extra Codex usage can now get you locked out.
OpenAI's new help page on card and device limits:
- One device can only use so many paid accounts (Go, Plus, Pro 100/200/500)
- Hit it and you see "Device limit reached" at sign-in, or get signed out later, even if the purchase went through
- Signing out of another account doesn't free a slot
- Business, Enterprise, Edu and Free don't count toward it
This lands the same week multi-account switching shipped on mobile, so check before you buy a second sub. The sanctioned route to more usage is credits under Usage & Billing in the Codex app.
help.openai.com/en/articles/…
Switching is still allowed. OpenAI's page says device limits are separate from account switching limits.
The cap is on how many paid personal accounts (Go, Plus, Pro) one device can use. Business, Enterprise, Edu and Free don't count, and the page doesn't give the exact number.
Known bug: Max and Ultra gone from the Codex app slider.
After the latest desktop update, the reasoning slider stops at Extra High, even when Settings shows Ultra as your default. 10 people on one GitHub issue so far, on Mac and Windows, with Astra and Sol.
Two fixes users confirmed:
1. Settings > General > available reasoning efforts: re-check Max and Ultra.
2. Or add this to ~/.codex/config.toml, then fully restart the app:
[desktop]
enabled-reasoning-efforts = ["low", "medium", "high", "xhigh", "max", "ultra"]
show-ultra-in-model-picker-slider = true
Config fix credit: JXN20210043 on GitHub.
Fair ask to OpenAI: keep the reasoning levels users picked across updates.
github.com/openai/codex/issu…
![[Windows desktop] After update, Settings shows Ultra but Astra chat slider stops at Extra High;...](https://pbs.twimg.com/card_img/2116238173139550208/dp2O0SFB?format=jpg&name=800x419)
Heads-up: stacking paid accounts on one machine for extra Codex usage can now get you locked out.
OpenAI's new help page on card and device limits:
- One device can only use so many paid accounts (Go, Plus, Pro 100/200/500)
- Hit it and you see "Device limit reached" at sign-in, or get signed out later, even if the purchase went through
- Signing out of another account doesn't free a slot
- Business, Enterprise, Edu and Free don't count toward it
This lands the same week multi-account switching shipped on mobile, so check before you buy a second sub. The sanctioned route to more usage is credits under Usage & Billing in the Codex app.
help.openai.com/en/articles/…
Two more Codex resets are coming: Days 27 and 28 of the 28-day run.
Tibo's Day 26 update:
- Switching between multiple accounts now works on mobile
- Account switching on desktop is "coming soon"
- The next two days are both limit resets, and he says they're banked
If you've been rationing Codex usage, you can spend it today. The last reset landed around midnight PST, so run /status after that to confirm.
Day 26/ You can now easily switch between multiple accounts on mobile, and coming soon to desktop too. Next two days will be resets… banked… do with this what you may 👀.
help.openai.com/en/articles/…
Built with Codex usage in mind: @talkaboutdesign shipped agent-stat 0.3.0.
It shows your Codex and Claude Code usage locally, no account:
- per-request costs at current model prices
- subagent and archived sessions counted
- 24h/7d/30d/90d dashboard, cache savings, live subscription limits
Useful after this week's limit changes: check what your tasks actually spend.
Try: npx agent-stat@latest
agent-stat 0.3.0 is out 📊
Your Codex + Claude Code usage, now accurate:
• Per-request costs, current model prices
• Subagents + archived sessions counted
• 24h/7d/30d/90d dashboard
• Cache savings + token mix
• Live subscription limits
All local, no account.
npx agent-stat@latest
Let me know what you think.
Known bug: Codex app dictation got worse in 26.1027.30824.
Since the latest app update, users report:
- misheard words in Swedish, Russian and English dictation
- the live waveform is gone, so you can't tell it's recording
- some recordings don't start at all
Workaround: one user says rolling back to the previous build fixed it. The same dictation still works in Safari and ChatGPT Classic.
@ajambrosino asked for app complaints during the sprint. Fair ask: bring back the waveform and fix non-English accuracy.
Also new in Codex: GPT-6 Rosalind Research, for approved life-sciences Research orgs only (gpt-6-rosalind in the API).
Source: help.openai.com/en/articles/…
Side chats in the Codex app will be saved soon.
App lead Andrew Ambrosino asked if side chats should persist, then answered "vox populi, vox dei. will ship soon."
What users asked for in his replies:
- Don't lose side chats when the app closes, restarts or updates
- A way to turn a side chat into a regular chat, or hand it back to the main one
- Keep a temporary mode for throwaway questions
Until it ships, treat side chats as disposable and copy anything worth keeping into the main thread before you quit.
Codex tip: diagnose connection drops with one command.
Update to CLI v0.166.0, then run:
codex doctor --network-only
It runs only the config, connectivity and WebSocket checks, so you can see if the problem is on your side (proxy, VPN, config) before restarting sessions.
Bonus in the same release: codex queue --resume resumes an unloaded thread after you queue a message.
Update: npm i -g @openai/codex@latest
Notes: github.com/openai/codex/rele…
7/7 Not viral, but steady: false-success reports since April: #19421 (guluarte), #42021 (linwanlong) and #54465, plus repeats in last week's install.sh 404s.
Fair ask to OpenAI: print "old -> new version" after codex update, and warn when nothing changed.
github.com/openai/codex/issu…
6/7 Workaround until then. Check the version actually moved:
b=$(codex --version); codex update; a=$(codex --version); echo "$b -> $a"
If it didn't, pin the release: npm i -g @openai/[email protected]
With an age gate on, npm then fails loudly (ETARGET) instead of quietly.
5/7 Same root cause: on 0.166.0 with nothing to update, it still prints "Update ran successfully! Please restart Codex."
Both npm cases are reported and still open: #16488 by bps-tanaka (min-release-age) and #37241 by Roland013 (already up to date).
github.com/openai/codex/issu…
4/7 Not covered: npm installs. Codex runs npm install -g @openai/codex and prints success whenever npm exits 0. It never compares versions.
With npm's min-release-age=2 on 0.166.0, codex update said 🎉 and left me on 0.165.0. npm chose an older build; Codex didn't say so.
3/7 Fixed in 0.166.0: the updater now saves the script first and only runs it if curl succeeded.
Same dead-proxy test: curl (7), a clear Error line, exit code 1, version unchanged. Correct. Fix by etraut-openai; root cause traced by jiang1997 & abruption.
github.com/openai/codex/pull…
