Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Tool RoutingArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
What
The internal logic that decides how a tool call gets dispatched now first checks whether that tool has an active state machine associated with it. For non-MCP tools (tools not provided via the Model Context Protocol) that do have one, the call is routed directly through that state machine, bypassing the previous logic based on a 'supported' flag and prefetch requests.
Why
This changes the underlying mechanism for dispatching tool calls, letting individual tools manage their own call-handling logic via a dedicated state machine rather than going through one shared routing path.
