Unclear It is unclear whether --unsandboxed is a flag users can pass or only an internal entry, and what it does.
What
When a session starts, Claude Code now makes a second decision alongside the existing one about running in the cloud by default. The new decision is about a sandbox VM, an isolated virtual computer the session runs in, kept separate from your own machine. The decision ends as none, declined or applied. It applies when:
- the
sandboxVmByDefaultoption is set, - the session is eligible, and
- you did not pass unsandboxed.
Related changes:
--unsandboxedis a new command-line flag Claude Code recognises. It is added to a list of flag names that also holds--remote-control,--rcand--local. What that list is used for was not traced.- The cloud-sessions-by-default decision now also counts unsandboxed as declining it, the same as
--local. Before, only local declined it.
Why
Where these defaults are switched on, a session may start in a sandbox VM or in the cloud without you asking. Passing --unsandboxed is the way to stay out of both.
* Before v2.1.202, sessions connected with `/remote-control` or `claude --remote-control` didn't report their permission mode at all, so claude.ai and the mobile app could show a permission mode the session wasn't in. The mismatch affected…see the edit
It is unclear whether `--unsandboxed` is a flag users can pass or only an internal entry, and what it does.