GitHub Copilot CLI overlay with authentication, network policy, and native ACP support.
10K+
GitHub Copilot CLI overlay with authentication, network policy, and native ACP support.
| Name | Required | Default | Description |
|---|---|---|---|
version | Required | — | GitHub Copilot release carried by the image |
[email protected]| Type | Required | Description | |
|---|---|---|---|
com.docker.sandbox/network-policy@1 | Required | — | |
com.docker.sandbox/credential@1 | Optional | GitHub API access for git and gh | |
com.docker.sandbox/credential@1 | Optional | Copilot request access, separable from the broader github token | |
com.docker.sandbox/lifecycle@1 | Required | — | |
com.docker.sandbox/agent-context@1 | Optional | — | |
com.docker.sandbox/agent-context@2 | Optional | — | |
com.docker.sandbox/acp@1 | Optional | — | |
deb/jq, deb/util-linux, deb/libstdc++6sbx run <agent> --kit sbx/copilot-mixin:latestRun the following command to install sbx on your machine.
brew install docker/tap/sbxwinget install Docker.sbxThis v3 mixin Kit packages GitHub Copilot for Docker Sandboxes. It adds the agent, authentication configuration, and runtime integration to a compatible workload. The workload keeps its entrypoint.
This Kit is built on Docker Hardened Images.
sbx run sbx/shell:latest --kit sbx/copilot-mixin:latest /path/to/workspace
When the shell opens, run copilot. This kit supplies an overlay, so it needs a workload such as
Shell.
A manual copilot launch keeps its native approval behavior. To match the workload's automatic tool approval, run
copilot --yolo.
This kit has no create-time kit arguments.
Bind the Copilot credential on the host with sbx secret set copilot. Git and GitHub CLI access use the separate
github service, configured with sbx secret set github. Host-bound credentials remain proxy-managed.
The copilot credential needs Copilot access. For a fine-grained GitHub token, grant the Copilot Requests permission.
Working git or gh authentication alone does not establish Copilot access.
When the runtime supplies an MCP gateway, the kit registers it automatically in ~/.copilot/mcp-config.json. Existing
unrelated settings and server entries are preserved.
ACP support is included. Configure an ACP client to open a non-TTY stream to the sandbox.
sbx exec -i <sandbox> copilot --acp
The sandbox supplies the isolation for agent tool execution. Launch the kit through Docker Sandboxes and configure extra tool or MCP destinations in the runtime network policy as needed.
If a tool cannot reach a service, run sbx policy log on the host to identify blocked destinations.
sbx/copilot provides the complete agent workload.sbx/copilot-sessions provides host-backed conversation state.For the Kit format and capability contracts, see the Sandbox Kit v3 specification.
For runtime setup, see the Docker Sandboxes documentation. For provenance, SBOM, VEX, and image verification, see the Docker Hardened Images documentation.
GitHub and GitHub Copilot are trademarks of GitHub, Inc. Product names and logos do not imply sponsorship or endorsement.