{"version":"2.1.321","anchor":"remote-control-cli-adds-settings-and-debug-file-rejects","canonical_anchor":"remote-control-cli-adds-settings-and-debug-file-rejects","heading":"claude remote-control now accepts --settings with a file path","tier":"use","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-control-cli-adds-settings-and-debug-file-rejects","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### claude remote-control now accepts --settings with a file path\n\n`claude remote-control` now takes `--settings` with the path of a JSON settings file, and rejects inline JSON text\n\n**What**\n\n`claude remote-control` now understands `--settings`, which points it at a settings file. Before, it rejected `--settings` as an unknown argument.\n\nHere 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.\n\n**Why**\n\nRemote control can now be started with its own settings file, so its settings can be set without editing your usual settings files.\n\n- Area: Remote Control\n- Names: `--settings`, `claude remote-control`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}