{"version":"2.1.307","anchor":"device-bridge-gets-a-sandboxed-execution-object","canonical_anchor":"device-bridge-gets-a-sandboxed-execution-object","heading":"Device bridge prepares sandboxed running of its tools","tier":"internal","area":"Device Bridge","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/device-bridge-gets-a-sandboxed-execution-object","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Device bridge prepares sandboxed running of its tools\n\nOn start, the device bridge now sets up a place to run its tools and says whether the sandbox is currently required\n\n**Unclear.** It is not clear whether device bridge tools actually run in the sandbox yet.\n\n**What**\n\nThe device bridge is the part of Claude Code that offers tools to a connected device. When it starts, it now sets up a place to run those tools and tells the tools whether the sandbox, a restricted space for running commands, is required at that moment. That setup is cleaned away when the bridge stops or fails to start.\n\nIf the bridge is stopped while it is still listing what the machine offers, it now notices and does not finish registering.\n\n**Why**\n\nThis suggests tools offered through the device bridge can be run under the sandbox.\n\n- Area: Device Bridge\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}