{"version":"2.1.221","anchor":"taskoutput-no-longer-honours-the-legacy-wait-up-to-parameter","canonical_anchor":"taskoutput-no-longer-honours-the-legacy-wait-up-to-parameter","heading":"TaskOutput no longer honours the legacy wait_up_to parameter","tier":"notice","area":"Tool Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/taskoutput-no-longer-honours-the-legacy-wait-up-to-parameter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### TaskOutput no longer honours the legacy wait_up_to parameter\n\nTaskOutput ignores the old wait_up_to setting and just uses the 30 second default timeout.\n\n**What**\n\nThe TaskOutput input normalizer dropped its conversion of the old wait_up_to seconds value into a timeout.\n\n**Details**\n\n- task_id still falls back to agentId or bash_id.\n- Timeout is now `n.timeout ?? 30000`, so a call passing only wait_up_to gets the 30 second default.\n\n**Evidence**\n\n`block: n.block ?? !0,`\n\n- Area: Tool Use\n- Names: `timeout`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}