{"version":"2.1.248","anchor":"claude-remote-control-rejects-root-options-instead-of-forwar","canonical_anchor":"claude-remote-control-rejects-root-options-instead-of-forwar","heading":"claude remote-control rejects root options instead of forwarding them","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/claude-remote-control-rejects-root-options-instead-of-forwar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### `claude remote-control` rejects root options instead of forwarding them\n\nclaude remote-control now errors clearly on root-level options instead of forwarding them.\n\n**What**\n\nRunning `claude remote-control` with root-level CLI options now fails with a clear error naming the options it refuses, rather than passing your whole argv through to the bridge and behaving unpredictably. Unknown options and extra arguments are still allowed through to the bridge itself.\n\n**Details**\n\n- The subcommand disables its own help option and asks the loaded bridge module which root options it refuses.\n- If any refused option was supplied, it errors with a generated message and never starts the bridge.\n- Reachable on every build; no flag involved.\n\n**Evidence**\n\n`rootOptionsRemoteControlRefuses`\n\n- Area: Remote Control\n- Names: `claude remote-control`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}