{"version":"2.1.235","anchor":"task-tool-omitting-subagent-type-now-fails-with-the-list-of","canonical_anchor":"task-tool-omitting-subagent-type-now-fails-with-the-list-of","heading":"Task tool: omitting subagent_type now fails with the list of available agents","tier":"notice","area":"Task Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/task-tool-omitting-subagent-type-now-fails-with-the-list-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Task tool: omitting subagent_type now fails with the list of available agents\n\nThe Task tool now rejects launches missing `subagent_type` instead of silently picking a default agent\n\nPreviously, omitting `subagent_type` on a Task tool call silently fell back to a default agent. Now, unless the caller's agent set unambiguously implies one, the launch is rejected with an error that lists the available agents (\"none\" if there aren't any), reported as `subagent_type_missing` alongside a `tengu_subagent_type_miss` event carrying the count of available agents. The fork-specific refusal checks, for remote isolation and recursive fork, were factored into one shared checker so the same messages are reused when building that list.\n\n- Area: Task Tool\n- Names: `subagent_type`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}