What
Claude Code checks for remote-control or rc in the command line at the same early point it spots update, doctor, mcp serve and plugin eval, so the bridge can be steered before the main app loads.
Evidence
return o.some((n) => n === "remote-control" || n === "rc");
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleremote-controlrc
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.
Confirmed since
Anthropic's documentation has since written up remote-control, on Claude Code changelog.
* Fixed Remote Control sessions served by `claude remote-control` showing a generated name instead of their session title in `ListAgents`changelog see the edit
Added since
A small documentation edit on Continue local sessions from any device with Remote Control touched a line naming remote-control after this was published.
All traffic travels through the Anthropic API over TLS, the same transport security as any Claude Code session. The connection uses multiple short-lived credentials, each scoped to a single purpose and expiring independently. When a `claud…remote-control see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Continue local sessions from any device with Remote Control touched a line naming remote-control after this…