Only one Full reset shown after multiple days without GPT-6 Astra access
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the ChatGPT/Codex App are you using?
Windows desktop package 26.903.8094.0
What platform is your computer?
Windows x64
What issue are you seeing?
As of September 9, 2026, this account still does not have GPT-6 Astra in the model picker. The account's supported rate-limits response reports only one available Full reset:
availableCount: 1- granted: September 5, 2026
- expires: October 5, 2026
- status: available
No reset credit has been consumed.
OpenAI's rollout messaging was understood to mean that users would receive one reset for each additional day they had to wait for Astra access. The current account state shows only one reset despite several additional days without Astra.
Could the team please clarify:
- Whether reset credits are expected to accrue once per delayed day.
- Whether the account display/API has a holding cap of one.
- Whether the remaining credits are issued only after Astra access is provisioned.
- If daily accrual is intended, whether the missing credits can be reconciled.
Steps to reproduce
- Sign in to ChatGPT desktop/Codex on the affected account.
- Confirm that GPT-6 Astra is absent from the model picker.
- Read current account limits using the supported account rate-limits endpoint.
- Observe that
rateLimitResetCredits.availableCountis 1 and only one grant is present.
Expected behavior
The available reset count should match the published rollout-compensation terms, or the product/docs should clearly explain the eligibility window, issuance timing, accumulation cap, and settlement behavior.
Additional information
- The desktop app is current/newer than the publicly linked stable MSIX build.
- No local managed model restriction was found.
- No reset was consumed during investigation.
- No account identifiers, credit identifiers, session IDs, or private logs are included in this report.
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 by reviewing the supported account rate-limits endpoint response, the GPT-6 Astra model-picker state, and the published rollout-compensation terms. Determine whether daily accrual, a one-credit cap, delayed issuance, or reconciliation is intended; the issue is done when the behavior is clarified in the product or documentation, or the missing credits are accounted for.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100