{"version":"2.1.304","anchor":"unreachable-remote-computer-errors-now-say-why","canonical_anchor":"unreachable-remote-computer-errors-now-say-why","heading":"Errors about an unreachable remote computer now say what went wrong","tier":"notice","area":"Remote Machines","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/unreachable-remote-computer-errors-now-say-why","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Errors about an unreachable remote computer now say what went wrong\n\nWhen a remote computer can't be reached, Claude now learns whether it is asleep, signed off, busy or silent\n\n**What**\n\nWhen Claude tries to use a remote computer that cannot be reached from the session, the error now depends on the cause:\n\n- asleep: the computer is asleep, and waking it is all you need to do.\n\n- signed off: nobody is signed in.\n\n- busy: the computer is occupied.\n\n- silent: the computer is not responding.\n\nEach message has its own advice, and each tells Claude not to try that computer again. Before, there was a special message for a sleeping computer and a general one for everything else.\n\n**Why**\n\nClaude can tell you exactly what to fix, such as waking the machine. It also stops retrying a computer that will not answer.\n\n- Area: Remote Machines\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}