Codex Usage Drain and fluctuation, Server Error, and remote issue
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)?
26.903.71938
What subscription do you have?
pro 20x $200
What platform is your computer?
Windows
What issue are you seeing?
Yesterday 9/9/2026, my usage drained from 65%to 25 % with less actual usage in the analytics than previous days. Then it fluctuated like crazy and then within a short time after I was out of usage. Also throughout the day I kept getting server error messages that would take my usage then force me to use the same if not more over and over until it finally would go through. Then when trying to access my remote session from my phone, it never brought the current session into play it would never show me what as going on and only showed up until I updated the app from desktop. still to this day it wipes out anything new i add to it except short term memory on the phone. desktop is fine and collects everything but the phone doesn't work. thats the main reason i used the damn desktop app as opposed ot the cli so that i could remote in from my phone. this is my profile @patterson0407
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a08b96-7730-7b91-913e-20cd26b0164e
What is the expected behavior?
No response
Additional information
No response
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 the feedback ID no-active-thread-01a08b96-7730-7b91-913e-20cd26b0164e and compare the reported desktop and phone remote-session behavior. The report names no source file or test; done should include a confirmed explanation or fix for usage fluctuations, server errors, and missing updates on the phone client.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100