Unclear It is not clear whether further conditions, such as a server-side switch, can still stop the tools from being served.
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.
This 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:
- the device ID
- the connection between your device and the session
- whether you trust the repository
A cloud session started with --remote can now reach tools on your own computer. That is a real change in what these sessions can do.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
* **With `/remote-control`, `claude --remote-control`, or [auto-connect](#enable-remote-control-for-all-sessions)**: the session keeps running without Remote Control, and Claude Code archives it at claude.airemote-control see the edit
To bring back a session you started with `claude --remote-control` or `/remote-control`, resume the conversation with `claude --continue` or `claude --resume`. For the permission mode that the resumed conversation starts in, see [permissio…remote-control see the edit
It is not clear whether further conditions, such as a server-side switch, can still stop the tools from being served.
A small documentation edit on Continue local sessions from any device with Remote Control touched a line naming claude --remote after this…