{"version":"2.1.284","anchor":"claude-remote-control-help-notes-updated","canonical_anchor":"claude-remote-control-help-notes-updated","heading":"claude remote-control --help now describes the trust prompt and worktree needs","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/claude-remote-control-help-notes-updated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### `claude remote-control --help` now describes the trust prompt and worktree needs\n\nThe `claude remote-control` help no longer says to run `claude` first to trust a folder, and notes what worktree mode needs\n\n**What**\n\nThe notes at the end of `claude remote-control --help` have changed:\n\n- 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.\n\n- 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.\n\n**Why**\n\nThe help text now matches the trust question that Remote Control asks on its own. The worktree requirement is stated before you run into it.\n\n- Area: Remote Control\n- Names: `claude remote-control --help`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}