{"version":"2.1.323","anchor":"remote-machine-notices-adapt-when-the-machines-own-tools-ar","canonical_anchor":"remote-machine-notices-adapt-when-the-machines-own-tools-ar","heading":"Remote-machine notices reworded when a machine's tools are offered as MCP tools","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remote-machine-notices-adapt-when-the-machines-own-tools-ar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote-machine notices reworded when a machine's tools are offered as MCP tools\n\nNotices about remote machines now explain that tools work again after reconnecting and add a note for single-machine sessions with no listed tools\n\n**What**\n\nIn some sessions, Claude Code can run tools on another machine. That machine's own tools can be offered to Claude as MCP tools, which are add-on tools connected through the Model Context Protocol. The notices Claude receives about these machines were reworded:\n\n- They now say the machine's own tools work again once it reconnects.\n\n- They now say \"every tool runs here\". Before, they told Claude to name the machine with a parameter, and to leave it out to \"run commands here\".\n\n- A new notice for single-machine sessions says the session has no listed tools on that machine.\n\n- A new name, `rtc_mcp_tools_alone_note`, is registered as a system reminder. A system reminder is a note Claude Code adds to the conversation for Claude to read.\n\nThe message about memory files that are too large to sync was also looked at. Its wording is unchanged and only internal code around it differs.\n\n**Why**\n\nThese notices guide where Claude runs commands in remote-machine sessions. The new wording should make it clearer which tools are available and that a disconnected machine's tools return once it reconnects.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}