canUseTool construction now checks whether the permission-prompt-tool server name is the literal sentinel "none". When it is, or when no MCP prompt tool was configured, requests can go through an ask-based fallback path that resolves ask behaviors via a new resolver before falling through to normal permission-denied handling.
Permission-prompt-tool routing gets a bypass for an explicit "none" sentinel
A permission-prompt tool named none now routes through an ask-based fallback resolver instead of the MCP prompt tool.
Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.259,
Internal ChangesSection of the release