Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Usage limit incorrectly shared across different accounts

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

After reaching the 5-hour usage limit on Account A (Plus subscription), I switched to Account B (Team subscription). However, Account B immediately showed the same “5-hour limit reached” message, even though Account B had not been used at all during that period.

This makes it appear that the usage quota is being shared or cached across accounts unexpectedly.

Root Cause

After reaching the 5-hour usage limit on Account A (Plus subscription), I switched to Account B (Team subscription). However, Account B immediately showed the same “5-hour limit reached” message, even though Account B had not been used at all during that period.

This makes it appear that the usage quota is being shared or cached across accounts unexpectedly.

RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.513.31313 (2867)

What subscription do you have?

plus & team

What platform is your computer?

No response

What issue are you seeing?

Environment

  • Platform: Codex / ChatGPT
  • Account A: ChatGPT Plus
  • Account B: ChatGPT Team
  • OS: macOS
  • Browser: Chrome
  • Region: Japan

Description

After reaching the 5-hour usage limit on Account A (Plus subscription), I switched to Account B (Team subscription). However, Account B immediately showed the same “5-hour limit reached” message, even though Account B had not been used at all during that period.

This makes it appear that the usage quota is being shared or cached across accounts unexpectedly.

Steps to Reproduce

  1. Log into Account A with a Plus subscription
  2. Use Codex until the 5-hour usage limit is reached
  3. Log out of Account A
  4. Log into Account B with a Team subscription
  5. Open Codex
  6. Observe that Account B also shows the “usage limit reached” message immediately

Expected Behavior

Account B should have its own independent usage quota and should not inherit the usage limit status from another account.

Actual Behavior

Account B incorrectly shows that the 5-hour limit has already been reached, despite having no usage during that time window.

Additional Context

  • The issue may be related to:
    • browser session caching
    • device-level rate limiting
    • IP-based quota enforcement
    • shared authentication/session state
  • Tried:
    • logging out/in
    • refreshing browser
    • switching accounts
  • Issue still persists

Impact

This prevents access to Codex on a separate paid Team account and blocks normal usage.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019e45f5-b69e-7cc2-a5b2-2815a8fcd390

What is the expected behavior?

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Usage limit incorrectly shared across different accounts