{"version":"2.1.232","anchor":"forked-slash-commands-fall-back-to-an-available-agent-and-sa","canonical_anchor":"forked-slash-commands-fall-back-to-an-available-agent-and-sa","heading":"Forked slash commands fall back to an available agent and say so","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/forked-slash-commands-fall-back-to-an-available-agent-and-sa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Forked slash commands fall back to an available agent and say so\n\nForked slash commands now fall back to an available agent and log which one ran.\n\n**What**\n\nA forked command asking for an agent that cannot host a fork now runs on general-purpose (or the first available agent) and logs which agent it actually used, rather than substituting silently.\n\n**Details**\n\n- The built-in web-fetch agent is now excluded from the pool of valid fork bases.\n\n**Evidence**\n\n`is not available as a fork base, running on`\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}