{"version":"2.1.283","anchor":"claude-remote-can-now-serve-this-machines-tools-to-the","canonical_anchor":"claude-remote-can-now-serve-this-machines-tools-to-the","heading":"claude --remote can now offer this machine's tools to the cloud session","tier":"use","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/claude-remote-can-now-serve-this-machines-tools-to-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### `claude --remote` can now offer this machine's tools to the cloud session\n\nWhen `claude --remote` starts a cloud session and stays attached, it can now make tools on your own machine available to that session\n\n**Unclear.** It is not clear whether further conditions, such as a server-side switch, can still stop the tools from being served.\n\n**What**\n\n`claude --remote` starts a session that runs in the cloud instead of on your computer. When it creates that session and stays attached to it, Claude Code now passes along a set of served tools. These are tools on your own machine that the cloud session can use. Before, this was always left empty when you started a session this way.\n\nThis only happens after your device has bound to the session, which means it has registered and been given a device ID. Claude Code works out which tools to serve from three things:\n\n- the device ID\n\n- the connection between your device and the session\n\n- whether you trust the repository\n\n**Why**\n\nA cloud session started with `--remote` can now reach tools on your own computer. That is a real change in what these sessions can do.\n\n- Area: Remote Tools\n- Names: `claude --remote`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}