Skip to content

Fallback not used when primary provider is in cooldown after adding Codex #1815

@KentaSUGAI

Description

@KentaSUGAI

Summary

After hitting Anthropic rate limits, the agent enters cooldown and does not fall back to Codex, even though Codex is configured as a fallback. The only way
I could recover was switching primary to Codex manually.

Environment

  • Clawdbot: 2026.1.22
  • OS: macOS 26.2 (arm64)
  • Primary: anthropic/claude-sonnet-4-5
  • Fallbacks: anthropic/claude-opus-4-5, openai-codex/gpt-5.2-codex, openai-codex/gpt-5.1-codex-mini
  • agents.defaults.models allowlist enabled (Codex added)

Steps to reproduce

  1. Set primary to Anthropic and fallbacks to include Codex.
  2. Hit Anthropic rate limit so all Anthropic profiles enter cooldown.
  3. Add Codex to allowlist + fallbacks after cooldown starts.
  4. Send a message.

Expected behavior

When all Anthropic profiles are in cooldown, the agent should fall back to Codex.

Actual behavior

Chat fails with:

Error: No available auth profile for anthropic (all in cooldown or unavailable).

No fallback occurs.

Workaround

Change primary to Codex:

clawdbot config set agents.defaults.model.primary "openai-codex/gpt-5.2-codex"

Logs (excerpt)

... lane task error: Error: No available auth profile for anthropic (all in cooldown or unavailable).
... Embedded agent failed before reply: No available auth profile for anthropic (all in cooldown or unavailable).

Notes

This seems to happen only if Codex is added after Anthropic enters cooldown. If Codex is configured before cooldown, fallback appears to work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions