Signals

Copilot's enabled sandbox now permits local-network access by default

Edited by Michael Ruescher

Copilot CLI 1.0.100 defaults local/private-network access on inside an enabled sandbox. Version 1.0.101 permits direct macOS localhost TCP when local access is enabled and no host filters apply. Stable 1.0.103 also repairs saved sandbox settings and launch flags in new and resumed ACP sessions. Sandboxing itself remains default-off. Pinned docs still show the older network default, so omission is an unsafe policy choice.

What this changes for operators

  • Terminal and ACP fleet owners: install stable 1.0.103 and set sandbox.allowLocalNetwork deliberately. Test a needed development listener and an unintended private service on each host; a functioning local development loop can now replace a workaround while exposing services an operator previously assumed were unreachable.
  • Compare new and resumed ACP sessions with saved settings and launch flags, recording the actual server binary. For required containment, verify enabled=true, failIfUnavailable=true and allowBypass=false in managed policy. The 1.0.103 release and package establish delivery even though its final public notes commit is ahead of the source tag.
  • Keep host-filter and Windows cases in the test matrix. Platform-specific connection and refusal traces would settle the deployed boundary; the narrow macOS exception does not prove every localhost path works. Use those results to decide whether saved configuration removes per-session repair work.

Primary sources

Signal metadata

Source findings

Featured in

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-10-24-github-copilot-cli-sandbox-local-network-default

Research evidence and publication history are open in the repository.