What probably matters to youSection of the release
What
New "enable" tools were added for device/browser tool families that are already connected: enable__mcp__remote-devices__computer, enable__mcp__claude-in-chrome, and enable__mcp__remote-devices__Claude_Browser.
These tools do nothing by design — their descriptions and results tell Claude that the underlying mcp__ tools (such as mcp__remote-devices__computer_*) are already available and should be called directly, instead of trying to "enable" them first. They also include guidance on what to tell the user if the remote computer's Claude app isn't responding.
They are only registered as available tools when a remote/device session is actually active (a session config resolves).
Why
Without these no-op stand-ins, Claude could try to call a nonexistent "enable" step before using already-connected device or browser tools; now it's told directly to just use the real tools.
