{"version":"2.1.265","anchor":"no-op-enable-tools-for-already-connected-device-tool-famil","canonical_anchor":"no-op-enable-tools-for-already-connected-device-tool-famil","heading":"No-op 'enable' tools added for already-connected device tools","tier":"use","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/no-op-enable-tools-for-already-connected-device-tool-famil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### No-op 'enable' tools added for already-connected device tools\n\nNew no-op enable tools tell Claude to just use already-connected device\/browser tools directly\n\n**What**\n\n- 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`.\n\n- These tools do nothing by design \u2014 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.\n\n- They are only registered as available tools when a remote\/device session is actually active (a session config resolves).\n\n**Why**\n\nWithout 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.\n\n- Area: Elsewhere\n- Names: `enable__mcp__claude-in-chrome`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}