Please REOPEN Issue 88 - It is not fixed.
Resolved 💬 4 comments Opened Apr 21, 2025 by mathusiast Closed Apr 22, 2025
💡 Likely answer: A maintainer (tibo-openai, collaborator)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.1.2504172351
Which model were you using?
o4-mini-2025-04-16
What platform is your computer?
Darwin 24.5.0 arm64 arm
What steps can reproduce the bug?
Just one of many in recent two days...
e [Error]: Rate limit reached for o4-mini in organization org-FaKQtnywbKBWxbRbD5wCG53p on tokens per min (TPM): Limit 200000, Used 150405, Requested 51478. Please try again in 564ms. Visit https://platform.openai.com/account/rate-limits to learn more.
at e.a [as iterator] (file:///opt/homebrew/lib/node_modules/@openai/codex/dist/cli.js:449:1514)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async T0.run (file:///opt/homebrew/lib/node_modules/@openai/codex/dist/cli.js:466:2933) {
status: undefined,
headers: undefined,
request_id: undefined,
error: {
type: 'tokens',
code: 'rate_limit_exceeded',
message: 'Rate limit reached for o4-mini in organization org-FaKQtnywbKBWxbRbD5wCG53p on tokens per min (TPM): Limit 200000, Used 150405, Requested 51478. Please try again in 564ms. Visit https://platform.openai.com/account/rate-limits to learn more.',
param: null
},
code: 'rate_limit_exceeded',
param: null,
type: 'tokens'
}
What is the expected behavior?
Simply sleep for the specified amount of time mentioned in the try again, e.g.
sleep for buffer + 564ms in case of
Please try again in 564ms
What do you see instead?
_No response_
Additional information
_No response_
4 Comments
Lots of bugs open for this one issue?!?
https://github.com/openai/codex/issues?q=is%3Aissue%20state%3Aopen%20rate%20limit
indeed. they closed it #88 while it is still amongst us.
This should now be fixed in the latest release, please install it and let me know if you still encounter issues by opening a new issue with context. The implementation has changed a lot, so whatever possible new failure you would encounter we would have to investigate with the new context, thanks for the patience here!
See https://github.com/openai/codex/pull/559