{"version":"2.1.176","anchor":"explicit-fork-selection-for-agent-tool","canonical_anchor":"explicit-fork-selection-for-agent-tool","heading":"Explicit Fork Selection for Agent Tool","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.176\/e\/explicit-fork-selection-for-agent-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.176","markdown":"### Explicit Fork Selection for Agent Tool\n\n**What**\n\nThe `subagent_type: \"fork\"` value is now a named, explicitly-selectable agent type rather than the implicit default when no `subagent_type` is provided. This makes multi-agent code clearer and avoids accidental forking.\n\n**Details**\n\n- Omitting `subagent_type` (when the fork experiment is active) previously implicitly created a fork; now the behavior is documented as explicit opt-in via `\"fork\"`\n- Remote sessions cannot use `isolation: \"remote\"` with fork \u2014 a clear error is returned\n- Other named agent types still start with zero context\n- The Agent tool description has been updated to reflect this\n\n**Evidence**\n\nUpdated Agent tool description (search for `\"(except subagent_type: \\\"fork\\\")\"` and `\"Fork cannot use isolation: \\\"remote\\\"\"`)"}