What
claude remote-control now understands --settings, which points it at a settings file. Before, it rejected --settings as an unknown argument.
Here the option takes only the path of a JSON settings file. Unlike elsewhere in Claude Code, a JSON string typed straight on the command line is rejected with a message saying so.
Why
Remote control can now be started with its own settings file, so its settings can be set without editing your usual settings files.
Names in the bundle--settingsclaude 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.
Confirmed since
Anthropic's documentation has since written up claude remote-control, on Continue local sessions from any device with Remote Control.
A `claude remote-control` server started with `--spawn session` has room only for its one session, so it can't run a fork.remote-control see the edit
Confirmed since
Anthropic's documentation has since written up --settings, on Speed up responses with fast mode.
* **In non-interactive mode**: pass Fable 5.2 as [`--model`](https://code.claude.com/docs/en/cli-reference#cli-flags) and fast mode in [`--settings`](https://code.claude.com/docs/en/cli-reference#cli-flags), for example `claude -p "Summari…fast-mode 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 --settings, on Speed up responses with fast mode.
Anthropic's release notes agree
Added --settings <file> to claude remote-control, which applies a settings file to every session it starts; if the file changes, no new…