Hidden sandbox install and status commands set up the Windows sandbox user with one UAC prompt.
What's wrong with this entry?
A hidden sandbox command group adds install, which sets up the Windows sandbox user and network filters and self-elevates through a single UAC prompt, and status, which prints availability and install state as JSON. Both are registered on every build but refuse to run outside native Windows, when the Windows sandbox is not enabled, or when policy excludes the platform.
installprints a JSON{status, message}result and exits 0 only when status is"ok".statusprints{available, installed, policyLocked, reasons};policyLockedcomes from a check for sandbox settings locked by administrator policy.
claude plugin sandbox status
claude plugin sandbox installInstall the Windows sandbox user and network filters. Self-elevates (one UAC prompt). Prints a JSON {status, message} result and exits 0 only when status is "ok"., Print Windows sandbox availability and install state as JSON {available, installed, policyLocked, reasons}.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
macOS sandbox re-applies read and delete denials inside writable folders
Both mention sandbox
-
v2.1.236
Sandbox proxy no longer writes to sockets that have gone away
Both mention sandbox
-
v2.1.236
IPv6 hosts through the proxy
Both mention sandbox