GPT-6 Astra: Usage limits consuming rapidly / short session length
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)?
Version 26.901.51231
What subscription do you have?
Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
I am writing to share feedback regarding the usage limits for the new GPT-6 Astra model. Currently, the rate limit is consumed far too quickly, making it nearly impossible to complete even minor tasks within a single session.
For context, I started a fresh session with 100% capacity at 2:51 PM IST, and by 3:11 PM IST, I had already hit the limit. A 20-minute window is simply too short to accomplish meaningful work. Having to constantly pause and wait for the next session creates a highly disruptive and frustrating workflow.
I strongly recommend reviewing the current limits for GPT-6 Astra, as these brief sessions significantly diminish the model's practical utility.
What steps can reproduce the bug?
- Open a fresh session with the GPT-6 Astra model showing 100% availability (Started at 2:51 PM IST).
- Begin working on standard development/text tasks.
- Observe that the session limit is completely exhausted within 20 minutes (Session went out of limit at 3:11 PM IST).
- The rapid consumption happens even during normal, small-scale usage without massive context inputs or heavy code generation.
What is the expected behavior?
The GPT-6 Astra session limit should be structured to allow for reasonable, continuous workflow chunks. A single session should last long enough to complete at least minor-to-moderate tasks (ideally extending beyond a 20-minute window) without abruptly cutting off and forcing the user into long wait times for the next session.
Additional information
This issue heavily impacts productivity. Having to repeatedly pause work and wait for the cooldown/refresh period creates a disjointed experience and introduces unnecessary stress when trying to maintain a steady workflow.
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
The report names Codex App version 26.901.51231, GPT-6 Astra, and Windows, but no source file, test, or entry point. Start by investigating how usage limits are accounted for and reproduce the reported 20-minute exhaustion from a fresh session. Done means confirming the consumption behavior and establishing an agreed limit or product change.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100