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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

TaskOutput no longer honours the legacy wait_up_to parameter

You'll notice
Useful2 Signal0
Tool Use

TaskOutput ignores the old wait_up_to setting and just uses the 30 second default timeout.

timeout
What

The TaskOutput input normalizer dropped its conversion of the old wait_up_to seconds value into a timeout.

Details
  • task_id still falls back to agentId or bash_id.
  • Timeout is now n.timeout ?? 30000, so a call passing only wait_up_to gets the 30 second default.
Evidence

block: n.block ?? !0,

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.221 →