Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

claude remote-control refuses flags typed before the verb

You'll notice
Useful3 Signal2
Remote Control

Flags typed before remote-control now error out instead of being silently dropped.

remote-control
What

Options 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.

Details
  • Carried over: verbose, debug, model, pluginDir, dangerouslySkipPermissions, enableAutoMode, bare and others.
  • If --permission-mode was among the rejected options, the message tells you to run claude remote-control --permission-mode <mode> instead.
  • 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.
  • A blocking trusted-device preflight runs before the bridge starts; on failure, event logging and Datadog are flushed against a 500ms timeout before exit.
Usage
claude remote-control --permission-mode plan
Evidence

Error: Remote Control is disabled by your organization's policy (managed setting disableRemoteControl).

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.248 →