{"version":"2.1.310","anchor":"bridge-tool-host-status-sandbox-dependency-errors-and-vm-on","canonical_anchor":"bridge-tool-host-status-sandbox-dependency-errors-and-vm-on","heading":"Remote control status explains sandbox failures and reports a VM-only mode","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/bridge-tool-host-status-sandbox-dependency-errors-and-vm-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Remote control status explains sandbox failures and reports a VM-only mode\n\nThe remote control status line now lists missing sandbox dependencies when the sandbox fails to start, and has a VM-only case\n\n**What**\n\nWhen you use remote control, Claude Code shows a status line about where commands run. A sandbox is a restricted environment that limits what commands can touch. The status line changes in three ways:\n\n- When the sandbox failed to start, the message now includes the dependency errors that stopped it, rather than only the reason commands are running outside the sandbox.\n\n- A new VM-only case says that commands run without anyone watching are allowed inside a virtual machine (VM).\n\n- The status is worked out again whenever the decision about the sandbox changes.\n\nIf the dependency errors cannot be read, Claude Code logs that and carries on.\n\n**Why**\n\nIf you use remote control, you get a clearer reason when sandboxing does not start, so you can see which dependency to install or fix.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}