Codex CLI blocked by rate limits for unrelated org
What version of Codex is running?
codex-cli 0.92.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.2
What platform is your computer?
Darwin 24.3.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
iTerm2
What issue are you seeing?
I see this error when I try to use Codex CLI, but it is for an unrelated org. This org does not belong to any of my accounts, and I verified my auth and keys are good. I am not sure where it could be coming from - my codex cli has been correctly configured to my account:
■ stream disconnected before completion: Rate limit reached
for organization org-BOvpEHVcDPTe8h4lZnwMO5Ly on tokens per
min (TPM): Limit 250000, Used 250000, Requested 21649. Please
try again in 5.195s. Visit https://platform.openai.com/
account/rate-limits to learn more.
Separately, in another terminal, I got the same error, but it had different rate limits:
■ stream disconnected before completion: Rate limit reached
for organization org-BOvpEHVcDPTe8h4lZnwMO5Ly on requests per
min (RPM): Limit 3000, Used 3000, Requested 1. Please try
again in 20ms. Visit https://platform.openai.com/account/
rate-limits to learn more.
What steps can reproduce the bug?
Uploaded thread: 019c02bd-f7ce-7c31-8600-4f144a0ddb54
What is the expected behavior?
I should be able to use Codex as normal.
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
same
same.
<img width="756" height="114" alt="Image" src="https://github.com/user-attachments/assets/85ef7429-f8ad-4d10-b804-b6d061538a3e" />
if you also check https://platform.openai.com/settings/organization/limits
you will see that despite your subscription (i am on pro), they started billing you as well
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.