codex responses with 'Rate limit reached for organization'

Resolved 💬 7 comments Opened Jan 28, 2026 by stdhyh Closed Jan 28, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.92.0

What subscription do you have?

ChatGPT Pro

Which model were you using?

gpt-5.2

What platform is your computer?

Darwin 25.2.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Wrap

What issue are you seeing?

stream disconnected before completion: Rate limit reached for organization org-{xxx} on tokens per min (TPM): Limit 250000, Used 250000, Requested 22700. Please try
again in 5.448s. Visit https://platform.openai.com/account/rate-limits to learn more.

What steps can reproduce the bug?

Uploaded thread: 019c02cc-357d-7241-af90-2223cc90c508

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #10058
  • #10055
  • #10052
  • #10051

Powered by Codex Action

locainin · 5 months ago

it appears to be an issue relating to gpt-5.2, switching to codex resolved it for me

Daviswhistle · 5 months ago
it appears to be an issue relating to gpt-5.2, switching to codex resolved it for me

I love you

iwillwait4u · 5 months ago

Thank you so much I have a deadline to catch on!

ahmedelami · 5 months ago

This worked for me:

The issue was a stale, cached authentication session in the local config (it was prioritizing an old/limited API Org instead of my ChatGPT subscription).

  1. Kill lingering processes and remove the cached auth file:
pkill -f codex
rm ~/.codex/auth.json
  1. Start fresh (forcing no env vars to ensure a clean login):
env -u OPENAI_API_KEY -u OPENAI_ORGANIZATION codex
  1. Select "Sign in with ChatGPT" when prompted.

Lmk if it also works for you or helps?

neteroster · 5 months ago

seems to be fixed

etraut-openai contributor · 5 months ago

Thanks for reporting. There was a temporary service issue that caused the responses API to incorrectly report rate limit errors when it shouldn't. The issue has been mitigated. Everything should be back to normal now. Apologies for the disruption.