What
If claude remote-control fails to register and it is not running in a terminal (for example when started by a script), and the error carries an HTTP status, the process now waits before exiting. The wait is based on the server's Retry-After value, a hint about how long to wait before trying again, and has an upper limit. It prints a notice such as "Exiting in about 30 seconds."
Why
A script or service that runs Remote Control will see a pause and a notice before the process exits, instead of an immediate exit.
Names in the bundleclaude remote-control
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.
Added since
A small documentation edit on Platforms and integrations touched a line naming claude remote-control after this was published.
| [Remote Control](/docs/en/remote-control) | Drive a running session from [claude.ai/code](https://claude.ai/code) or the Claude mobile app | Your machine (CLI, Desktop, or VS Code) | Run [`claude remote-control` or `/remote-control`](/do…platforms see the edit
Confirmed since
Anthropic's documentation has since written up claude remote-control, on Claude Code changelog.
* Fixed `claude remote-control --debug` failing with "Unknown argument: --debug", although Remote Control's own eligibility error says to run with `--debug`changelog see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude remote-control, on Claude Code changelog.
Anthropic's release notes agree
Fixed the Artifact tool missing from Remote Control sessions that claude remote-control starts for you to open from Claude Desktop…