You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
ImprovementsKind: in v2.1.284,
ImprovementsSection of the release
What
The notes at the end of claude remote-control --help have changed:
Trust: they no longer tell you to run claude in the directory first to accept the workspace trust dialog. They now say you will be asked whether to trust a folder you have not trusted yet. Running claude there once first is only needed when there is no terminal to ask on.
Worktrees: a new note says worktree mode needs either a git repository or WorktreeCreate/WorktreeRemove hooks. A worktree is a separate working copy of your project. Hooks are commands you configure to run at certain moments.
Why
The help text now matches the trust question that Remote Control asks on its own. The worktree requirement is stated before you run into it.
Read from
Names in the bundleclaude remote-control --help
Since it was published
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up claude remote-control --help, on Claude Code changelog.* Fixed `claude remote-control --help` saying `--[no-]chrome` defaults to the machine's `/chrome` setting; spawned sessions keep Claude in Chrome off unless `--chrome` is passedchangelogsee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up claude remote-control --help, on Claude Code changelog.
Anthropic's release notes agreeImproved claude remote-control: in a folder you haven't trusted yet, it now asks for workspace trust on the terminal instead of exiting
