Remote Control now waits for an in-progress login token refresh before registering the device
When you run claude remote-control to connect a device (so you can continue a local session from your phone or another computer), the setup process now waits for any in-progress OAuth token refresh (the background renewal of your login credentials) to finish before it registers the device or exits, up to a new capped wait time (OAUTH_REFRESH_EXIT_WAIT_CAP_MS).
This avoids a race where Remote Control tries to register or exit while your login token is mid-refresh, which could otherwise leave the connection in a bad state.
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
* 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
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.
| `--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
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
claude remote-control on Continue local sessions from any device with Remote Control