{"version":"2.1.280","anchor":"tool-call-routing-gains-a-per-tool-machine-path-bypassed","canonical_anchor":"tool-call-routing-gains-a-per-tool-machine-path-bypassed","heading":"Tool-call routing gains a per-tool 'machine' path, bypassed for MCP tools","tier":"internal","area":"Tool Routing","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/tool-call-routing-gains-a-per-tool-machine-path-bypassed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Tool-call routing gains a per-tool 'machine' path, bypassed for MCP tools\n\nTool calls can now be routed through a registered per-tool state machine before falling back to the old dispatch path\n\n**What**\n\nWhen Claude Code dispatches a tool call, it now first checks whether a state machine has been registered for that specific tool. If one exists, the call is routed through it instead of the older logic that handles local tools and tools passed through from a host. This new routing is explicitly skipped for MCP (Model Context Protocol, a standard way external tools connect to Claude Code) tools, which continue to use the previous path.\n\n**Why**\n\nThis lets individual tools define their own custom handling logic for how their calls are processed, without disturbing how MCP tool calls are dispatched.\n\n- Area: Tool Routing\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}