Signals

Copilot CLI makes local sandboxing available to every user

Edited by Michael Ruescher

1.0.93 (2026-10-07) makes local command sandboxing generally available; it remains default-off. Earlier 1.0.92 withholds ambient GITHUB_TOKEN unless configured and adds masked Git authentication. The documented proxy can inject selected credentials at permitted destinations. Stable at cutoff is 1.0.97. User settings left in config.json are ignored from 1.0.93, so upgrading alone does not enable an existing policy.

What this changes for operators

  • Individual and managed CLI users: install 1.0.97, move user settings to settings.json and try /sandbox enable or copilot --sandbox -p for a controlled job. Inspect /sandbox status and /sandbox policy, then perform one authenticated Git operation and one denied destination test.
  • Fleets requiring containment must set sandbox.enabled and sandbox.failIfUnavailable true and sandbox.allowBypass false, verifying supported hosts and managed delivery. Server-managed enabled alone can be declined on unsupported hosts; built-in file tools use best-effort software checks.
  • Scope each masked secret’s injectHosts and inspect credential files separately. Test localhost workloads on macOS; Windows host rules rely on programs honoring the proxy. Full bypass restores ordinary credentials. Recorded platform-specific denial and credential-use results would settle the deployed boundary. This replaces some repeated credential inspection with maintained host lists and deliberate exceptions, without measured savings.

Primary sources

Signal metadata

Source findings

Featured in

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-10-13-github-copilot-cli-local-sandbox-and-credential-proxy

Research evidence and publication history are open in the repository.