claude-code - 💡(How to fix) Fix SendMessage for continuing spawned sub-agents is documented but not callable

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Code Example

Agent({ subagent_type: "general-purpose", prompt: "Hello, how are you?" })

---

agentId: af9219c00828602bd (use SendMessage with to: 'af9219c00828602bd' to continue this agent)
RAW_BUFFERClick to expand / collapse

The system prompt and the Agent tool result both tell the model to use SendMessage to follow up with a previously spawned sub-agent, but the tool is never actually exposed on the tool surface — so multi-turn sub-agent conversations are advertised but unusable.

Repro

  1. Open a Claude Code session (Opus 4.7, 1M context build).
  2. Have the model call the Agent tool, e.g.:
    Agent({ subagent_type: "general-purpose", prompt: "Hello, how are you?" })
  3. The tool result comes back with a trailer like:
    agentId: af9219c00828602bd (use SendMessage with to: 'af9219c00828602bd' to continue this agent)
  4. On the next turn, try to use SendMessage:
    • ToolSearch with select:SendMessageNo matching deferred tools found
    • ToolSearch with keyword queries (send message agent, continue spawned agent follow-up, +SendMessage) → returns Slack/QBO senders, RemoteTrigger, Monitor, etc., but no SendMessage.
  5. Net effect: the only way to "follow up" with the prior agent is to spawn a brand-new one with Agent and re-pass all the context, which the Agent tool description itself warns about ("A new Agent call starts a fresh agent with no memory of prior runs").

Expected

Either:

  • (a) SendMessage is actually wired up and ToolSearch surfaces it (ideally after the first Agent call so it doesn't clutter the default tool list), or
  • (b) the system prompt and the post-spawn trailer stop mentioning SendMessage and instead document the real continuation mechanism (or its absence).

Actual

The model is told to use a tool that does not exist in the harness, wastes turns probing for it, and either has to give up or invisibly start a fresh agent (losing the prior conversation state without telling the user).

Why it matters

Multi-turn sub-agent conversations are useful for protecting the parent context window while iterating with a specialist — e.g., handing a research agent a follow-up question after it returns initial findings. Without SendMessage, every follow-up either pollutes the parent context or restarts cold.

Env

  • Model: claude-opus-4-7 (1M context)
  • Platform: darwin 24.6.0
  • Claude Code CLI in terminal

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING