Codex automatically changed priority mode without permission, so i lost most of my usage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
0.147.0
What subscription do you have?
Pro
What platform is your computer?
Darwin 25.3.0 arm64 arm
What issue are you seeing?
The evidence supports an app/client settings bug—not a user-enabled Fast mode.
What the records show:
- No /fast, settings action, or user request enabling Fast mode exists.
- The thread oscillated automatically:
- 17:12 KST: default → priority
- 18:16 KST: priority → default
- 20:07 KST: default → priority
- Next day 12:11 KST: priority → default
- Changes occurred only at task boundaries, before ordinary user messages.
- The final goal ran entirely during the second priority interval.
- Your persisted configuration currently says service_tier = "default".
- Both active subagents were also default, so Fast was not inherited from them.
The strongest suspect is client/app state synchronization with version skew: - This thread is owned by a long-running Codex app-server 0.144.1 process started August 17.
- Codex 0.147.0 was subsequently installed, but the old daemon continued serving this thread.
- The frontend appears to have silently supplied or restored priority for some submissions while the visible/default configuration remained Standard.
What steps can reproduce the bug?
Feedback ID: 01a01e12-f6f4-7792-a869-b98ea71dc7d5
What is the expected behavior?
It should not enable fast mode without user permission. Reset my usage!
Additional information
Thread: 01a01e12-f6f4-7792-a869-b98ea71dc7d5
Issue: service_tier silently oscillated between default and priority
Expected: default; user never enabled Fast mode
Impact: final 11-hour goal ran entirely as priority, consuming approximately
50% of weekly usage
App-server: 0.144.1, while installed Codex was 0.147.0
First unexpected priority event: 2026-08-21 17:12:34 KST
Priority interval covering goal: 2026-08-21 20:07:28 KST through
2026-08-22 12:11:34 KST
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Feedback ID 01a01e12-f6f4-7792-a869-b98ea71dc7d5 and compare the reported service_tier transitions with the installed app and long-running app-server versions. Done means reproducing or explaining the unauthorized priority changes and ensuring the visible default configuration remains authoritative without consuming priority usage.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100