[BUG] haiku subagent delegates to 3.5
Status Closed — not planned
Maintainer reply ✓ Yes — km-anthropic
Workaround ✓ Mentioned in thread ↓
Activity 12 comments · opened Oct 16, 2025 · closed Jan 11, 2026
💡 Likely answer: A maintainer (km-anthropic, contributor)
responded on this thread — see the highlighted reply below.
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
model: haiku on subagent definition delegates to haiku-3.5, not the recent model.
What Should Happen?
delegate to haiku-4.5
Error Messages/Logs
Steps to Reproduce
define sub agent with model: haiku
Claude Model
None
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.0.19
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Non-interactive/CI environment
Additional Information
still model: claude-haiku-4-5-20251001 seems work
12 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
hi @sorryhyun, how are you checking that it's delegating to haiku 3.5? We upgrade all first party users to haiku 4.5 (whereas we haven't upgraded third party users -- AWS & GCP -- yet as they need to provision separate quota).
@km-anthropic oh, I've set model to haiku in github project directly by modifying
.claude/agents/*.mdand I met the following issue, so I thought this would be caused by delegation.Could you please see if you've set
ANTHROPIC_DEFAULT_HAIKU_MODELanywhere? possibly toclaude-3-5-haiku-20241022? orANTHROPIC_SMALL_FAST_MODEL? And lastly if you can runclaude --versionI couldnt find any env variables you mentioned and I always use the recent version.
Also, claude code sdk has the same problem, when
ClaudeAgentOption(model="haiku")@km-anthropic
Gotcha, could you check
claude --version? I think if you update it to your latest version you should be set.Confirmation:
--model haikustill defaults to Haiku 3.5I can confirm this behavior. Testing with Claude Code 2.0.27 on Bedrock backend:
Current Behavior
Using
--model haikuwith the recommended Bedrock configuration:Results in:
Error:
The
haikualias resolves to Haiku 3.5 (October 2024), which doesn't support thinking - causing errors with the recommended configuration from the documentation.Workaround
As documented at https://docs.claude.com/en/docs/claude-code/amazon-bedrock#4-model-configuration, set the environment variable:
This successfully resolves to Haiku 4.5.
Question
While the documentation correctly states this variable must be set manually, why does the
haikualias still default to a year-old model (3.5) that's incompatible with the recommended configuration?Given that:
MAX_THINKING_TOKENSsetting)sonnetpoint to the latest version (4.5)Shouldn't the
haikualias be updated to point to 4.5 by default now, with users explicitly opting into 3.5 if needed?I also confirmed out-of-date haiku alias with Claude Code (v2.0.27) on Bedrock. Regarding quota provisioning, my understanding is that Bedrock's Haiku 4.5 quota is adjusted to their past Haiku 3.5 usage, so this shouldn't be a blocking factor for updating the default mapping. I hope the default can be changed to Haiku 4.5 for Bedrock users soon.
Yeah the current default is set to 3.5 for 3p (Bedrock + GCP) because we don't want to cause errors due to quota provisioning. The simplest fix right now would be to set
ANTHROPIC_DEFAULT_HAIKU_MODEL=anthropic.claude-haiku-4-5-20251001-v1:0in your environment variables if you're confident you have quota.This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.