What
claude remote-control used to reject --debug, -d and --debug=… as unknown arguments, stop, and point you to claude remote-control --help. It now accepts them. This command's own argument handling does nothing further with the flag.
Why
Running claude remote-control --debug used to fail at startup and now runs.
Names in the bundleclaude remote-control--debug
claude remote-control
Claude Code changelog modified, high confidence
* Fixed the Artifact tool missing from Remote Control sessions that `claude remote-control` starts for you to open from Claude Desktop, claude.ai or the mobile appsee 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 --debug, on Model configuration.
`enforceAvailableModels` remaps the Default option only when `availableModels` is non-empty. When `availableModels` is non-empty but no entry resolves to an allowed and available model, enforcement is skipped with a warning visible only un…model-config see the edit
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 Continue local sessions from any device with Remote Control.
* From `/remote-control`, `claude remote-control`, or `claude --remote-control`: `Couldn't verify your organization's policy for remote control. Check your network connection and try again.`remote-control see the edit
Added since
A small documentation edit on Continue local sessions from any device with Remote Control touched a line naming --debug after this was published.
| `-d`, `--debug[=<filter>]` | Turn on debug logging for the server, optionally filtered by category. Pass a filter only in the `=` form, such as `--debug=api,hooks`. Requires Claude Code v2.1.282 or later; earlier versions reject the flag…remote-control 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 the flag actually turns on debug output for remote control or is only tolerated is not known.
Anthropic's documentation agrees
claude remote-control on Claude Code changelog
Anthropic's release notes agree
Fixed claude remote-control --debug failing with "Unknown argument: --debug", although Remote Control's own eligibility error says to run…