Claude Code v2.1.221 ·
TaskOutput no longer honours the legacy wait_up_to parameter
TaskOutput ignores the old wait_up_to setting and just uses the 30 second default timeout.
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Tool UseArea: what it touches
RemovedKind: in v2.1.221,
RemovedSection of the release
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.
See this entry in the whole of v2.1.221 →
