Summary

After upgrading to v2026.5.4, all cron jobs with payload.model = anthropic/claude-haiku-4-5 began failing immediately with:

cron payload.model 'anthropic/claude-haiku-4-5' rejected by agents.defaults.models allowlist: anthropic/claude-haiku-4-5

This is a silent breaking change — there is no migration path, no warning during upgrade, and no documentation on which model slugs are now valid for cron payloads.

Steps to Reproduce

1. Have one or more cron jobs with payload.model = "anthropic/claude-haiku-4-5"
2. Upgrade to v2026.5.4
3. All affected crons fail immediately on next scheduled run with the allowlist rejection error
4. consecutiveErrors increments silently — no user-facing alert

Expected Behaviour

Either:

• The upgrade migrates claude-haiku-4-5 → claude-haiku-4-7 (or equivalent) automatically, OR
• The upgrade documents clearly which model slugs are valid, OR
• The default agents.defaults.models config includes a haiku-tier model out of the box so lightweight crons don't have to fall back to sonnet

Actual Behaviour

• anthropic/claude-haiku-4-5 → rejected by allowlist
• anthropic/claude-haiku-4-7 → passes allowlist check but then fails with Unknown model: anthropic/claude-haiku-4-7 from the Anthropic API (model slug not recognised)
• Only anthropic/claude-sonnet-4-6, deepseek/deepseek-chat, and google/gemini-2.5-flash are in the default allowlist

Impact

• All lightweight crons that previously used haiku for cost efficiency are either broken or forced onto sonnet (~10x cost)
• No automatic detection or remediation — users must manually identify and patch each cron
• In our fleet: 7 Haderach crons affected, plus additional crons across other agents swept by fleet manager

Questions

1. What is the correct Anthropic haiku model slug for v2026.5.4?
2. Should claude-haiku-4-5 → claude-haiku-4-7 be an automatic migration on upgrade?
3. Will the default agents.defaults.models config include a haiku entry in future releases?

Environment

• OpenClaw v2026.5.4
• macOS (arm64)
• Anthropic provider
• Multiple cron jobs with sessionTarget: isolated and payload.kind: agentTurn