{"version":"2.1.309","anchor":"remote-control-sandbox-testvm-option-spawn-mode-and-trust","canonical_anchor":"remote-control-sandbox-testvm-option-spawn-mode-and-trust","heading":"Remote control setup gets internal changes to sandbox and repository checks","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/remote-control-sandbox-testvm-option-spawn-mode-and-trust","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Remote control setup gets internal changes to sandbox and repository checks\n\nRemote control now handles git repository detection separately from the worktree hook check, and its tool host accepts a test VM option\n\n**What**\n\nRemote control lets you drive a Claude Code session from another device. Its setup steps changed in a few internal ways:\n\n- The tool host, the helper process that runs tools for the session, can now be started with an optional test VM setting.\n\n- Detecting whether the folder is a git repository is now a separate step from checking the worktree hook.\n\n- The message for `--allow-unattended-tool-calls` keeps its wording, apart from a renamed reference to `CLAUDE_CODE_CHILD_SESSION`, the environment variable Claude Code sets in programs it starts.\n\n**Why**\n\nThese are mostly internal changes. Using remote control should look the same as before.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}