Back to blog
Workflow
Claude Code

When to use a settings file instead of per-session flags?

Thắng Đoàn
Thắng Đoàn

Remote-controlled Claude Code sessions can start with inconsistent settings, so permission prompts and config vary from session to session. A new flag lets you pin one settings file to every session claude remote-control starts.

What it is

The --settings <file> option on claude remote-control applies a settings file to every session it starts. If the file changes, no new session starts until you restart claude remote-control.

Applied case

A developer running automation through claude remote-control can point it at a checked-in settings file so every spawned session inherits the same permission policy. When the file changes on disk, the tool refuses to start new sessions on the stale config, prompting a restart. Separately, this release also fixes cases where Bash permission checks, deny rules on cp or mv, and MCP OAuth redirects behaved incorrectly.

  • Pin one settings file via --settings <file> so all remote sessions share one policy

When to use it

Use when you drive sessions through claude remote-control and need identical settings across every session. Skip when you configure each session by hand or rely on per-invocation flags.

Read more

claude-code v2.1.321 release notes

Share:

Recommended for you

Enjoyed this article?

Subscribe for new articles. No spam. Unsubscribe anytime.

By subscribing you agree to receive the newsletter. No spam, and you can unsubscribe anytime.