{"version":"2.1.248","anchor":"claude-remote-control-refuses-flags-typed-before-the-verb","canonical_anchor":"claude-remote-control-refuses-flags-typed-before-the-verb","heading":"claude remote-control refuses flags typed before the verb","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/claude-remote-control-refuses-flags-typed-before-the-verb","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### `claude remote-control` refuses flags typed before the verb\n\nFlags typed before remote-control now error out instead of being silently dropped.\n\n**What**\n\nOptions placed before the verb, as in `claude --verbose remote-control`, used to be quietly dropped. The command now checks them against a list of options it can safely carry over and stops with an error naming the rest, so nothing you typed is silently ignored.\n\n**Details**\n\n- Carried over: `verbose`, `debug`, `model`, `pluginDir`, `dangerouslySkipPermissions`, `enableAutoMode`, `bare` and others.\n- If `--permission-mode` was among the rejected options, the message tells you to run `claude remote-control --permission-mode <mode>` instead.\n- The verb also exits with a specific error when the managed setting `disableRemoteControl` is on, and again when the org policy `allow_remote_control` denies it.\n- A blocking trusted-device preflight runs before the bridge starts; on failure, event logging and Datadog are flushed against a 500ms timeout before exit.\n\n**Usage**\n\n`claude remote-control --permission-mode plan` **Evidence** `Error: Remote Control is disabled by your organization's policy (managed setting `disableRemoteControl`).`\n\n- Area: Remote Control\n- Names: `remote-control`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}