OpenClaw Agent Failure Due to Recurring OAuth Rate-Limit Cooldown Loop
The agent is failing because all authentication profiles for the provider are in cooldown.
Both models (openai-codex/gpt-5.2 and openai-codex/gpt-5.3-codex) use the same provider: openai-codex. There is only one configured authentication profile, and it is OAuth-based.
That OAuth profile hit the rate limit and entered cooldown. Since there is no API key profile, no secondary profile, and no fallback provider, the agent has no available authentication method. As a result, all models fail before generating a reply.
Additionally, the cooldown keeps renewing automatically. When the cooldown period ends, the agent immediately sends a new request. Because the account is still under the same rate limits, the request hits the limit again and triggers another one-hour cooldown. This creates a continuous loop where the provider never becomes effectively available.
In summary:
Single OAuth profile
→ Rate limit
→ Cooldown
→ Cooldown expires
→ Agent sends request
→ Rate limit again
→ Cooldown resets
This is an authentication rate-limit loop, not a model or connection issue.
@Krill 🦐
Both models (openai-codex/gpt-5.2 and openai-codex/gpt-5.3-codex) use the same provider: openai-codex. There is only one configured authentication profile, and it is OAuth-based.
That OAuth profile hit the rate limit and entered cooldown. Since there is no API key profile, no secondary profile, and no fallback provider, the agent has no available authentication method. As a result, all models fail before generating a reply.
Additionally, the cooldown keeps renewing automatically. When the cooldown period ends, the agent immediately sends a new request. Because the account is still under the same rate limits, the request hits the limit again and triggers another one-hour cooldown. This creates a continuous loop where the provider never becomes effectively available.
In summary:
Single OAuth profile
→ Rate limit
→ Cooldown
→ Cooldown expires
→ Agent sends request
→ Rate limit again
→ Cooldown resets
This is an authentication rate-limit loop, not a model or connection issue.
@Krill 🦐
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
