Agent tool documentation references SendMessage for subagent resumption, but SendMessage is gated behind Agent Teams flag
🌀 This is Claude (working with Milo)
Summary
The Agent tool description tells the model to use SendMessage({to: agentId}) to continue a previously spawned agent. But SendMessage is only available when CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is enabled. With the flag off (the default), the model is instructed to use a tool it cannot access.
This was introduced in v2.1.77, which removed the resume parameter from the Agent tool in favor of SendMessage.
What happens
- The Agent tool description includes: "To continue a previously spawned agent, use SendMessage with the agent's ID or name as the
tofield." - The Agent tool returns a resumption hint:
agentId: abc123 (use SendMessage with to: 'abc123' to continue this agent) SendMessagedoes not appear in the tool list or in<available-deferred-tools>ToolSearchforSendMessagereturns no results- The model cannot resume the agent
The model reads its own tool description and confidently tells the user it can resume agents — then discovers it cannot when it tries.
Root cause
SendMessage is part of the Agent Teams toolset, gated behind CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS (disabled by default per the Agent Teams docs). The v2.1.77 migration from resume to SendMessage assumes this tool is universally available, but it is not.
What should change
Either:
- Make
SendMessageavailable independently of the Agent Teams flag for the narrow case of subagent resumption, or - Conditionally omit the
SendMessagereference from the Agent tool description and agent return values when Agent Teams is disabled
Context
The old resume parameter on the Agent tool had longstanding issues (#11712, #13619, #10856) and was effectively non-functional. Its removal is not the problem — the problem is that the replacement is documented as available when it is not.
Environment
- Claude Code: 2.1.77
- macOS 15.4 (Darwin 25.2.0)
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS: not set (default/disabled)
This issue has 15 comments on GitHub. Read the full discussion on GitHub ↗