Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.235 Home All releases ←olderv2.1.234 v2.1.236newer→
Claude Code v2.1.235

Launching a subagent without naming one now fails with the list of agents

You'll notice
Useful3 Signal2
Subagents

Launching a subagent without naming one now errors and lists the agents you can pick.

subagent_type
What

Omitting subagent_type on the Task tool used to fall through to a default agent. It is now rejected, unless your agent set leaves only one possibility, with an error naming the available agents, or "none" when there are none.

Details
  • Reported as subagent_type_missing, with a tengu_subagent_type_miss event recording how many agents were available.
  • The refusals specific to forking (remote isolation, recursive fork) moved into one shared check, so the same wording is reused when that agent list is built.
Evidence

subagent_type_missing

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.235 →