{"version":"2.1.309","anchor":"remote-machine-tool-hints-name-the-machine","canonical_anchor":"remote-machine-tool-hints-name-the-machine","heading":"Claude is told the name of an attached machine and how to check background commands","tier":"notice","area":"Attached Machines","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/remote-machine-tool-hints-name-the-machine","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Claude is told the name of an attached machine and how to check background commands\n\nInstructions about an attached machine now name it, and tell Claude to read a background command's output there because it never reports finishing\n\n**What**\n\nClaude can work on an attached machine, meaning another computer connected to the session. The instructions Claude gets about that machine now include its name. They also tell Claude that a background command started on the attached machine never tells the session when it finishes. To find out what happened, Claude should read the command's output file or run `cat` or `tail` on that machine.\n\n**Why**\n\nClaude is now told plainly to go and check a background command's output, rather than wait for a finished message that will never come. Naming the machine also makes it clear which computer the instructions are about.\n\n- Area: Attached Machines\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}