Repository navigation
Automatically run automation after rate limit window allows continued usage #12503
Closed as not planned
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.217.1959 (669)
What subscription do you have?
Plus
What platform is your computer?
Darwin 24.1.0 arm64 arm
What issue are you seeing?
Automations start and then spin despite being out of Codex messages. This can lead to dozens of Automation threads open and running.
I haven't checked this but it might be that if I left them in this running but blocked state they would immediately consume messages when the limit resets (despite being stale and useless at that point).
What steps can reproduce the bug?
Create an automation that burns through your messages limit
Wait for the automation to start again.
What is the expected behavior?
The automation checks for available messages before starting and reports an error if none are available but does not start a spinning thread.
Additional information
No response
Activity
etraut-openai commentedon Feb 22, 2026
When you say "out of codex messages", do you mean that you've reached your usage limit?
The app (and harness) have no way of knowing whether you've reached your usage limit until a prompt is sent to the service.
As a clarification, usage isn't based on the number of messages you send; it's based on the number of tokens consumed (input, output and reasoning).
iandanforth commentedon Feb 22, 2026
@etraut-openai Thank you for your response. The app displays the following
that's where the messages terminology comes from.
If the app has hit this state the expected behavior would be for automations to either 1. Wait until the displayed reset time has passed or 2. Check before running that messages / tokens / credits are available to the logged in account.
etraut-openai commentedon Feb 22, 2026
Ah thanks, I didn't realize we were using that terminology in the app. It's a little misleading.
The automation isn't "hanging" in this case. It's simply blocked from running because of the usage limit.
The app is working as intended here, so I don't think we'd consider this a bug. I'm going to change this to a feature request.
[-]Automations start and hang despite being out of Codex messages[/-][+]Automatically run automation after rate limit window allows continued usage[/+]vjain419 commentedon Mar 5, 2026
+1 This seems related to #8310. Both issues point to rate-limit window handling and resume behavior that disrupts long-running sessions.
etraut-openai commentedon Apr 3, 2026
This feature request hasn't received enough upvotes, so closing.
Taimylife commentedon May 16, 2026
I sure wish codex would just kick back in with what ever it was doing before the usage limit was hit.
KrisCris commentedon Sep 5, 2026
This feature should be supported same like Claude Code