Group of 3 You'll notice
Remote Control's background session poller now treats an expired credential (401) as a reason to re-register, with clearer error messages
What
- The bridge's background polling loop, used for Remote Control/cloud sessions, now treats a 401 (unauthorized) response as a trigger to re-register the environment, in addition to the existing 404 (not found) case, provided the same gates hold.
- The re-registration function now takes a
triggerargument distinguishing 401 from 404, logs the correct status code, and records which trigger fired in telemetry. A 401 uses its own backoff floor (reregister401BackoffFloorMs) and logs a message about a renewed Remote Control credential rather than a re-registered environment. - If repeated 401s exhaust re-registration attempts, or the server issues a replaced environment instead, the bridge now logs a distinct, user-facing fatal error telling the user to restart
claude remote-control.
Why Previously only a 404 triggered recovery, so an expired or renewed credential (401) could leave a Remote Control session stuck polling without a clear path forward. Now it's handled automatically where possible, with a clearer error message when it can't be.
Names in the bundleclaude remote-control
claude remote-control
Continue local sessions from any device with Remote Control modified, high confidence
Until you accept Remote Control's one-time confirmation, `claude remote-control` explains what it does and asks `Enable Remote Control? (y/n)` before starting the server. Answer `y` to accept and start the server. If you decline, Claude Co…see the edit
claude remote-control
Continue local sessions from any device with Remote Control modified, high confidence
* Signed out, from `claude remote-control`: `You must be logged in to use Remote Control. Remote Control is only available with claude.ai subscriptions.`see the edit
claude remote-control
Claude Code changelog modified, high confidence
* Fixed `claude remote-control` exiting and dropping every attached session when its server credential expires (about 30 days after start); the host now re-registers and keeps goingsee the edit
claude remote-control
Continue local sessions from any device with Remote Control modified, medium confidence
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…see the edit
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 claude remote-control, on CLI reference.
| `--remote-control-session-name-prefix <prefix>` | Prefix for auto-generated [Remote Control](/docs/en/remote-control) session names when no explicit name is set. Defaults to your machine's hostname, producing names like `myhost-graceful-…cli-reference see the edit
Added since
A small documentation edit on Claude Code on mobile touched a line naming claude remote-control after this was published.
Remote Control connects the Claude app to a Claude Code session running on your machine, so code execution and filesystem access stay local while you drive the session from your phone. Start the session on your computer with `claude remote…mobile see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether either of the two related gates, `tengu_bridge_env_reregister` and `tengu_bridge_fatal_error`, is active has not been read for this…
Anthropic's documentation agrees
claude remote-control on Continue local sessions from any device with Remote Control
Anthropic's release notes agree
Fixed claude remote-control exiting and dropping every attached session when its server credential expires (about 30 days after start); the…