Evidence record / github-copilot-cli

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the signals and issues that cite it, below.

2026-10-24-github-copilot-cli-acp-honors-saved-sandbox-settings-and-launch-flags-on-new-and-resumed-sessions

ACP honors saved sandbox settings and launch flags on new and resumed sessions. ACP sessions now honor saved sandbox settings and --sandbox / --no-sandbox, including resume. This is distinct from 1.0.88’s repair of managed MCP, permission, and plugin policy across entry points. The current ACP reference says server-launch tool filters and reasoning settings seed every created or loaded session, while a managed sandbox requirement overrides --no-sandbox.

Channel: tagged-release. Half: defect. Date: 2026-10-22.

Operator consequence: Upgrade ACP-backed editors and wrappers to a runtime containing 1.0.103, then compare new and resumed sessions under the same saved sandbox policy. Record the server binary and launch arguments, not only the editor version. A wrapper’s working approval UI was never evidence that the shell sandbox matched the terminal session. The repair reduces integration-specific configuration work; boundary tests still belong to the host operator.

Receipt

Finding metadata

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

Finding ID: 2026-10-24-github-copilot-cli-acp-honors-saved-sandbox-settings-and-launch-flags-on-new-and-resumed-sessions

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact