{"version":"2.1.300","anchor":"remote-control-no-longer-reports-or-forwards-a-sandbox-optio","canonical_anchor":"remote-control-no-longer-reports-or-forwards-a-sandbox-optio","heading":"Remote control drops its sandbox option and tracks where sign-in tokens come from","tier":"notice","area":"Remote Control","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/remote-control-no-longer-reports-or-forwards-a-sandbox-optio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Remote control drops its sandbox option and tracks where sign-in tokens come from\n\nRemote control no longer passes or reports a sandbox option and now records where its sign-in token came from when a refresh fails\n\n**What**\n\nRemote control is the feature that lets a Claude Code session be driven from elsewhere. It changes in two ways:\n\n- A sandbox option is no longer passed to the sessions it starts, and it is no longer included in its start-up log or usage data. A sandbox is a restricted environment that limits what commands can touch.\n\n- When renewing the sign-in token fails, Claude Code now takes into account where that token came from. If it cannot tell, it logs the warning \"Could not read where the sign-in token came from\".\n\n**Why**\n\nFailed sign-in renewals in remote control are now handled with knowledge of where the token came from. If you relied on remote control forwarding a sandbox option, note that it no longer does.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}