Implement backoff policy when 429 would have happened

Resolved 💬 5 comments Opened Feb 11, 2026 by anupammukherjee Closed Apr 3, 2026

What variant of Codex are you using?

CLI

What feature would you like to see?

We get the 429 error when we exceed some number of requests per minute. When orchestrating multi-agent workflows, maybe we can set some parameter to artificially slow down requests till it meets the 20 req/min threshold rather than returning the error to facilitate hands-free workflows. Basically, I, as a human, don't want to have to wait for a while and re-issue the last command. Instead it would be much more useful to have it slow down the interval between requests and meet the rate limit without facing the 429 error.

Additional information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗