{"version":"2.1.323","anchor":"tool-registry-ids-and-whentouse-for-computer-use-tool-cloud","canonical_anchor":"tool-registry-ids-and-whentouse-for-computer-use-tool-cloud","heading":"The computer-control tool now tells Claude to prefer a matching MCP tool","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/tool-registry-ids-and-whentouse-for-computer-use-tool-cloud","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### The computer-control tool now tells Claude to prefer a matching MCP tool\n\nThe 'Your computer' tool now tells Claude not to use it when a task needs your own computer, and to use a matching MCP tool instead\n\n**What**\n\nThe built-in tool that lets Claude work on a computer, shown as \"Your computer\", now carries guidance for Claude about when to use it. When a task needs the user's own computer, Claude is told not to use this tool and to use a matching MCP tool instead. An MCP tool is one supplied by an MCP server, an add-on that connects Claude Code to outside programs.\n\nA few smaller internal additions arrived at the same time:\n\n- Several built-in tools now carry an identifier for a tool registry.\n\n- Claude Code now keeps track of which tool uses relate to cloud memory.\n\n- A data-flow server field was added to one of Claude Code's internal data formats.\n\n**Why**\n\nMost of this is groundwork for a tool registry and for tracking how data moves between tools. The guidance on the computer tool is the part that can change which tool Claude picks.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}