Unclear It is not clear what switches remote tool serving and the unattended-serving feature on, or whether either is on by default.
When claude --remote creates a cloud session and stays attached, Claude Code can now show two new consent questions:
- Local MCP servers: it can ask whether to share your local MCP servers with the cloud session, or tell you which ones were held back. MCP servers are programs that give Claude extra tools.
- Unattended serving: it can ask for your consent to serve tools unattended. This only happens when the session's permission mode is
autoorbypassPermissions, which are modes where Claude acts without asking you each time.
Both questions depend on remote tool serving being switched on. The unattended-serving question has three further conditions:
- a separate feature switch is on
- managed settings do not forbid unattended serving (managed settings are rules set by an organisation's administrator)
- you have not already answered it
These questions are new when you start a session with --remote. One of them covers tools running on your machine while permission prompts are skipped. An administrator can block unattended serving through managed settings.
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.
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
| `--push` | Push the tag to `--remote` after creating it |plugins/cli-reference see the edit
It is not clear what switches remote tool serving and the unattended-serving feature on, or whether either is on by default.
Anthropic's documentation has since written up --remote, on Plugin commands reference.