{"version":"2.1.290","anchor":"remote-tools-device-bridge-machine-listings-no-longer-adopt","canonical_anchor":"remote-tools-device-bridge-machine-listings-no-longer-adopt","heading":"Remote machines offered by the device listing can now be set aside","tier":"notice","area":"Remote Machines","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-tools-device-bridge-machine-listings-no-longer-adopt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote machines offered by the device listing can now be set aside\n\nClaude Code can now decline machines offered by its device listing and take remote machines only from the session's own connection\n\n**Unclear.** It is not clear what condition decides whether listed machines are still used, or whether that condition is met by default.\n\n**What**\n\nClaude Code can work with remote machines, meaning other computers it connects to and runs tools on. One way it learns about them is a device listing that offers machines it could use. Previously, machines from that listing were taken on directly.\n\nNow, unless an internal condition is met, Claude Code sets those offered machines aside and does not use them. It notes this in its log with the message \"machines are taken from the session channel alone\". A session is one continuous conversation with Claude Code, and in this case remote machines come only through that session's own connection.\n\n**Why**\n\nThis changes how Claude Code finds the remote machines it can use. Machines that used to appear through the device listing may no longer be picked up from it.\n\n- Area: Remote Machines\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}