Claude Code Adds a --settings Flag to claude remote-control
Claude CodeClaude Code 2.1.321 adds --settings <file> to the claude remote-control command, which applies one settings file to every session it starts. If the file changes, no new session starts until the user restarts claude remote-control.
Key Takeaways
claude remote-controlnow accepts--settings <file>, mirroring the flag on the main CLI.- The file applies to every session the command starts, which fixes the configuration in one place.
- A changed file does not affect a running host, since new sessions wait for a restart.
- The restart rule makes changes explicit, so sessions never start with half-applied settings.
- The flag is useful for always-on hosts, such as a machine left running for phone access.
- First-run messages are also clearer about what to do when the question goes unanswered.
One settings file for every Remote Control session
claude remote-control starts Claude Code sessions that a connected client, such as the web or mobile app, can drive. Claude Code 2.1.321 adds a --settings <file> flag to that command. The file is applied to every session the command starts, so a developer can fix the permission mode, model or other settings once instead of repeating them for each session.
What happens when the file changes
The settings file is read when claude remote-control starts. If the file changes afterward, no new session starts until the user restarts the command. This stops a running Remote Control host from quietly picking up edited settings in the middle of its run, and it gives the user a clear point at which a change takes effect.
Related Remote Control changes in the same release
The release also makes Remote Control sessions keep the folder they were started in (covered in its own entry), and it improves the messages shown for the first-run question when it goes unanswered.