openai / openai/codex

GPT-6 Astra still unavailable on September 15, zero reset credits, and at least nine promotional credits missing

Open
#45,570 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug rate-limits
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.908.70816

What subscription do you have?

ChatGPT Pro (5x / $100 per month), using Codex with my ChatGPT account.

What platform is your computer?

No response

What issue are you seeing?

Hello OpenAI Codex Support Team,
I am providing another update regarding my unresolved GPT-6 Astra access issue, missing promotional rate-limit reset credits, two apparent credit redemptions, and unexplained changes to my Codex weekly rate-limit window.
Current status as of September 15, 2026 at approximately 9:42 AM (UTC+8):

  • GPT-6 Astra, model ID gpt-6-astra, is still unavailable in my current Codex model list.
  • I am now running OpenAI Codex for Windows version 26.908.9136.0.
  • The application architecture is x64.
  • The Windows package status is reported as OK.
  • My account has zero available rate-limit reset credits.
  • The available-credit details list is empty.
  • My current Codex weekly usage is 10%.
  • My next weekly reset is scheduled for September 21, 2026 at approximately 9:22:13 AM (UTC+8).
  1. GPT-6 Astra remains unavailable after multiple Codex updates
    GPT-6 Astra has remained unavailable to me since September 4, 2026.
    During this period, my Codex desktop application has been updated multiple times:
  • Version 26.903.9818.0
  • Version 26.908.4834.0
  • Current version 26.908.9136.0
    I restarted and continued using Codex after these updates, but GPT-6 Astra remained absent from my available model list.
    Updating the client has therefore not resolved the issue.
    Please investigate whether my ChatGPT identity, account plan, rollout cohort, server-side model entitlement, workspace, seat, geographic region, or another account-level condition is preventing GPT-6 Astra from appearing.
    Please also confirm whether Codex desktop version 26.908.9136.0 supports GPT-6 Astra for eligible ChatGPT users.
  1. At least nine promotional reset credits appear never to have been granted
    According to the in-product rollout notice shown to me, eligible users should receive one full Codex rate-limit reset credit for every day they remain without access to GPT-6 Astra.
    GPT-6 Astra remained unavailable to me for every completed date from September 4 through September 14:
  • September 4: 1 credit expected
  • September 5: 1 credit expected
  • September 6: 1 credit expected
  • September 7: 1 credit expected
  • September 8: 1 credit expected
  • September 9: 1 credit expected
  • September 10: 1 credit expected
  • September 11: 1 credit expected
  • September 12: 1 credit expected
  • September 13: 1 credit expected
  • September 14: 1 credit expected
    This represents eleven completed calendar days without GPT-6 Astra access.
    However, I only observed two credits being granted:
  • September 4, 2026 at approximately 1:41 PM (UTC+8)
  • September 5, 2026 at 12:23:25 PM (UTC+8)
    I did not observe any additional promotional credits being granted for September 6 through September 14.
    Therefore, based on the promotion as it was presented to me, at least nine promotional reset credits appear never to have been granted.
    This calculation excludes September 15 and only counts dates that had fully ended before the current report.
  1. No September 15 credit has appeared so far
    As of approximately 9:42 AM on September 15, my account still shows zero available reset credits.
    If September 15 is counted as another eligible calendar day, the expected total becomes twelve credits. Because only two grants were observed, the number of missing promotional grants would become ten.
    I understand that there may be an undisclosed daily processing time or cutoff. The two credits I previously received appeared at approximately 12:23 PM and 1:41 PM (UTC+8), so the September 15 processing window may not yet have completed at the time of this report.
    Therefore:
  • The confirmed shortfall through September 14 is at least nine credits.
  • If no September 15 credit is granted by the applicable processing cutoff, the shortfall becomes ten credits.
    Please confirm the exact time zone, daily cutoff, grant-processing time, processing delay, accumulation cap, expiration policy, eligibility period, promotion start date, and promotion end date.
  1. Both previously granted credits appear to have been consumed during unexplained resets
    Both of the credits that were previously issued appear to have been consumed during two separate rate-limit reset events.
    First apparent redemption — September 9
  • My account previously showed two available reset credits.
  • On September 9 at approximately 12:08 PM (UTC+8), the available-credit count dropped from two to one.
  • At approximately the same time, my Codex weekly usage reset to 0%.
  • The next weekly reset changed to September 16 at approximately 12:08 PM.
  • I did not intentionally request or initiate this redemption.
    Second apparent redemption — September 10
    At approximately 3:46 PM on September 10, my account showed:
  • One available reset credit
  • Codex weekly usage at 87%
    At approximately 6:43 PM on September 10, it instead showed:
  • Zero available reset credits
  • An empty available-credit details list
  • Codex weekly usage at 6%
  • A new seven-day usage window
  • The next reset scheduled for September 17 at approximately 5:55:52 PM (UTC+8)
    These correlated changes strongly suggest that the final available credit was consumed to perform another full rate-limit reset at approximately 5:55:52 PM on September 10.
    I did not intentionally request or initiate this second redemption either.
    Please audit the complete server-side redemption history and determine whether these resets were triggered by me, automatically triggered by Codex, initiated by another client or session, or performed by an internal server-side process.
  1. Unexplained rate-limit-window change on September 14
    On September 11 at approximately 9:37 AM (UTC+8), my account showed:
  • Zero available reset credits
  • Codex weekly usage at 12%
  • The next reset scheduled for September 17 at approximately 5:55:52 PM
    On September 14 at approximately 9:22 AM, it instead showed:
  • Zero available reset credits
  • Codex weekly usage at 0%
  • The next reset scheduled for September 21 at approximately 9:22:13 AM
    This indicates that a new seven-day rate-limit window was established on September 14, even though the previous window was not scheduled to reset until September 17.
    Because the available-credit count was already zero before this change, I am not assuming that another reset credit was consumed. However, this remains an unexplained server-side account-state change.
    As of September 15 at approximately 9:42 AM:
  • The available-credit count remains zero.
  • Weekly usage has increased from 0% to 10%.
  • The next reset remains September 21 at approximately 9:22:13 AM.
    This confirms that the September 14 window remains the currently active weekly rate-limit window.
    Please explain whether the September 14 change was caused by a server-side administrative reset, plan migration, rollout adjustment, sliding-window recalculation, client update, reauthentication, billing change, or another internal process.
  1. Requested investigation and resolution
    Could you please:
  2. Verify whether my ChatGPT identity is eligible for GPT-6 Astra.
  3. Check whether the necessary GPT-6 Astra server-side entitlement is enabled for my account.
  4. Explain why GPT-6 Astra remains unavailable after multiple Codex desktop updates.
  5. Confirm whether Codex desktop version 26.908.9136.0 supports GPT-6 Astra for eligible ChatGPT accounts.
  6. Confirm the exact eligibility requirements, time zone, daily cutoff, delivery schedule, processing delay, accumulation cap, expiration policy, start date, and end date of the rollout-compensation promotion.
  7. Audit my complete server-side promotional eligibility and reset-credit grant history.
  8. Restore the nine promotional credits that appear not to have been granted for September 6 through September 14, or explain specifically why my account was considered ineligible on each date.
  9. Grant the September 15 credit if my account remains eligible, GPT-6 Astra remains unavailable, and today’s processing cutoff passes without a grant.
  10. Audit the two apparent credit redemptions on September 9 and September 10.
  11. For each apparent redemption, internally verify the exact timestamp, triggering client, session, request source, credit ID, redemption reason, and idempotency key.
  12. Confirm whether Codex can automatically consume a reset credit when a user approaches a rate limit, updates or restarts the application, signs in again, or continues an existing task.
  13. Restore either or both previously granted credits if the corresponding redemption was unauthorized or caused by a client-side or server-side error.
  14. Investigate and explain the September 14 rate-limit-window change while the available-credit count was already zero.
  15. Confirm when GPT-6 Astra is expected to become available to my account.
    Please do not respond only with my current available-credit balance. The current balance is zero, but that does not explain:
  • Why at least nine expected promotional grants never appeared
  • Whether the two previously issued credits were automatically or manually consumed
  • Which client, session, or server-side operation initiated each reset
  • Why the weekly rate-limit window changed again on September 14
  • Why GPT-6 Astra remains unavailable after multiple client updates
    I am specifically requesting:
  • A complete promotional eligibility review
  • A complete grant-history audit
  • A complete redemption-history audit
  • A review of the unexplained September 14 rate-limit-window change
  • A review of my GPT-6 Astra account entitlement
  • Restoration of all missing or incorrectly consumed credits
    I can provide screenshots, application logs, the in-app feedback session ID, timestamps, and additional account information through a secure support channel if required.
    Thank you.
What steps can reproduce the bug?

Hello OpenAI Codex Support Team,
I am providing another update regarding my unresolved GPT-6 Astra access issue, missing promotional rate-limit reset credits, two apparent credit redemptions, and unexplained changes to my Codex weekly rate-limit window.
Current status as of September 15, 2026 at approximately 9:42 AM (UTC+8):

  • GPT-6 Astra, model ID gpt-6-astra, is still unavailable in my current Codex model list.
  • I am now running OpenAI Codex for Windows version 26.908.9136.0.
  • The application architecture is x64.
  • The Windows package status is reported as OK.
  • My account has zero available rate-limit reset credits.
  • The available-credit details list is empty.
  • My current Codex weekly usage is 10%.
  • My next weekly reset is scheduled for September 21, 2026 at approximately 9:22:13 AM (UTC+8).
  1. GPT-6 Astra remains unavailable after multiple Codex updates
    GPT-6 Astra has remained unavailable to me since September 4, 2026.
    During this period, my Codex desktop application has been updated multiple times:
  • Version 26.903.9818.0
  • Version 26.908.4834.0
  • Current version 26.908.9136.0
    I restarted and continued using Codex after these updates, but GPT-6 Astra remained absent from my available model list.
    Updating the client has therefore not resolved the issue.
    Please investigate whether my ChatGPT identity, account plan, rollout cohort, server-side model entitlement, workspace, seat, geographic region, or another account-level condition is preventing GPT-6 Astra from appearing.
    Please also confirm whether Codex desktop version 26.908.9136.0 supports GPT-6 Astra for eligible ChatGPT users.
  1. At least nine promotional reset credits appear never to have been granted
    According to the in-product rollout notice shown to me, eligible users should receive one full Codex rate-limit reset credit for every day they remain without access to GPT-6 Astra.
    GPT-6 Astra remained unavailable to me for every completed date from September 4 through September 14:
  • September 4: 1 credit expected
  • September 5: 1 credit expected
  • September 6: 1 credit expected
  • September 7: 1 credit expected
  • September 8: 1 credit expected
  • September 9: 1 credit expected
  • September 10: 1 credit expected
  • September 11: 1 credit expected
  • September 12: 1 credit expected
  • September 13: 1 credit expected
  • September 14: 1 credit expected
    This represents eleven completed calendar days without GPT-6 Astra access.
    However, I only observed two credits being granted:
  • September 4, 2026 at approximately 1:41 PM (UTC+8)
  • September 5, 2026 at 12:23:25 PM (UTC+8)
    I did not observe any additional promotional credits being granted for September 6 through September 14.
    Therefore, based on the promotion as it was presented to me, at least nine promotional reset credits appear never to have been granted.
    This calculation excludes September 15 and only counts dates that had fully ended before the current report.
  1. No September 15 credit has appeared so far
    As of approximately 9:42 AM on September 15, my account still shows zero available reset credits.
    If September 15 is counted as another eligible calendar day, the expected total becomes twelve credits. Because only two grants were observed, the number of missing promotional grants would become ten.
    I understand that there may be an undisclosed daily processing time or cutoff. The two credits I previously received appeared at approximately 12:23 PM and 1:41 PM (UTC+8), so the September 15 processing window may not yet have completed at the time of this report.
    Therefore:
  • The confirmed shortfall through September 14 is at least nine credits.
  • If no September 15 credit is granted by the applicable processing cutoff, the shortfall becomes ten credits.
    Please confirm the exact time zone, daily cutoff, grant-processing time, processing delay, accumulation cap, expiration policy, eligibility period, promotion start date, and promotion end date.
  1. Both previously granted credits appear to have been consumed during unexplained resets
    Both of the credits that were previously issued appear to have been consumed during two separate rate-limit reset events.
    First apparent redemption — September 9
  • My account previously showed two available reset credits.
  • On September 9 at approximately 12:08 PM (UTC+8), the available-credit count dropped from two to one.
  • At approximately the same time, my Codex weekly usage reset to 0%.
  • The next weekly reset changed to September 16 at approximately 12:08 PM.
  • I did not intentionally request or initiate this redemption.
    Second apparent redemption — September 10
    At approximately 3:46 PM on September 10, my account showed:
  • One available reset credit
  • Codex weekly usage at 87%
    At approximately 6:43 PM on September 10, it instead showed:
  • Zero available reset credits
  • An empty available-credit details list
  • Codex weekly usage at 6%
  • A new seven-day usage window
  • The next reset scheduled for September 17 at approximately 5:55:52 PM (UTC+8)
    These correlated changes strongly suggest that the final available credit was consumed to perform another full rate-limit reset at approximately 5:55:52 PM on September 10.
    I did not intentionally request or initiate this second redemption either.
    Please audit the complete server-side redemption history and determine whether these resets were triggered by me, automatically triggered by Codex, initiated by another client or session, or performed by an internal server-side process.
  1. Unexplained rate-limit-window change on September 14
    On September 11 at approximately 9:37 AM (UTC+8), my account showed:
  • Zero available reset credits
  • Codex weekly usage at 12%
  • The next reset scheduled for September 17 at approximately 5:55:52 PM
    On September 14 at approximately 9:22 AM, it instead showed:
  • Zero available reset credits
  • Codex weekly usage at 0%
  • The next reset scheduled for September 21 at approximately 9:22:13 AM
    This indicates that a new seven-day rate-limit window was established on September 14, even though the previous window was not scheduled to reset until September 17.
    Because the available-credit count was already zero before this change, I am not assuming that another reset credit was consumed. However, this remains an unexplained server-side account-state change.
    As of September 15 at approximately 9:42 AM:
  • The available-credit count remains zero.
  • Weekly usage has increased from 0% to 10%.
  • The next reset remains September 21 at approximately 9:22:13 AM.
    This confirms that the September 14 window remains the currently active weekly rate-limit window.
    Please explain whether the September 14 change was caused by a server-side administrative reset, plan migration, rollout adjustment, sliding-window recalculation, client update, reauthentication, billing change, or another internal process.
  1. Requested investigation and resolution
    Could you please:
  2. Verify whether my ChatGPT identity is eligible for GPT-6 Astra.
  3. Check whether the necessary GPT-6 Astra server-side entitlement is enabled for my account.
  4. Explain why GPT-6 Astra remains unavailable after multiple Codex desktop updates.
  5. Confirm whether Codex desktop version 26.908.9136.0 supports GPT-6 Astra for eligible ChatGPT accounts.
  6. Confirm the exact eligibility requirements, time zone, daily cutoff, delivery schedule, processing delay, accumulation cap, expiration policy, start date, and end date of the rollout-compensation promotion.
  7. Audit my complete server-side promotional eligibility and reset-credit grant history.
  8. Restore the nine promotional credits that appear not to have been granted for September 6 through September 14, or explain specifically why my account was considered ineligible on each date.
  9. Grant the September 15 credit if my account remains eligible, GPT-6 Astra remains unavailable, and today’s processing cutoff passes without a grant.
  10. Audit the two apparent credit redemptions on September 9 and September 10.
  11. For each apparent redemption, internally verify the exact timestamp, triggering client, session, request source, credit ID, redemption reason, and idempotency key.
  12. Confirm whether Codex can automatically consume a reset credit when a user approaches a rate limit, updates or restarts the application, signs in again, or continues an existing task.
  13. Restore either or both previously granted credits if the corresponding redemption was unauthorized or caused by a client-side or server-side error.
  14. Investigate and explain the September 14 rate-limit-window change while the available-credit count was already zero.
  15. Confirm when GPT-6 Astra is expected to become available to my account.
    Please do not respond only with my current available-credit balance. The current balance is zero, but that does not explain:
  • Why at least nine expected promotional grants never appeared
  • Whether the two previously issued credits were automatically or manually consumed
  • Which client, session, or server-side operation initiated each reset
  • Why the weekly rate-limit window changed again on September 14
  • Why GPT-6 Astra remains unavailable after multiple client updates
    I am specifically requesting:
  • A complete promotional eligibility review
  • A complete grant-history audit
  • A complete redemption-history audit
  • A review of the unexplained September 14 rate-limit-window change
  • A review of my GPT-6 Astra account entitlement
  • Restoration of all missing or incorrectly consumed credits
    I can provide screenshots, application logs, the in-app feedback session ID, timestamps, and additional account information through a secure support channel if required.
    Thank you.
What is the expected behavior?

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or code entry point is identified; the report is centered on the Windows Codex client, the GPT-6 Astra model list, and server-side account state. Start by determining whether this repository handles model entitlements or rate-limit credits, then verify that the requested outcome would explain the missing grants, apparent redemptions, and September 14 window change.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.