Cursor CLI overlay for a shell workload, with native ACP, credentials, and workspace setup.
10K+
Cursor CLI overlay for a shell workload, with native ACP, credentials, and workspace setup.
| Name | Required | Default | Description |
|---|---|---|---|
version | Required | — | Cursor release the image carries |
[email protected]| Type | Required | Description | |
|---|---|---|---|
com.docker.sandbox/network-policy@1 | Required | — | |
com.docker.sandbox/credential@1 | Optional | Cursor API access (API key or Cursor OAuth) | |
com.docker.sandbox/lifecycle@1 | Required | — | |
com.docker.sandbox/agent-skills@1 | Optional | — | |
com.docker.sandbox/agent-context@1 | Optional | — | |
com.docker.sandbox/agent-context@2 | Optional | — | |
com.docker.sandbox/acp@1 | Optional | — | |
sbx run <agent> --kit sbx/cursor-mixin:latestRun the following command to install sbx on your machine.
brew install docker/tap/sbxwinget install Docker.sbxThis v3 mixin Kit packages Cursor 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/cursor-mixin:latest /path/to/workspace
When the shell opens, run cursor-agent. This kit supplies an overlay, so it needs a workload such as
Shell.
A manual cursor-agent launch keeps its native tool approval behavior. To match the workload's automatic tool approval,
run cursor-agent --yolo. Pre-trusting the workspace does not grant tool approval.
This kit has no create-time kit arguments.
Bind a Cursor API key or Cursor OAuth credential through the host runtime's cursor service. For an API key, run
sbx secret set cursor on the host. The runtime supplies credential sentinels, and the kit pre-trusts the mounted
workspace.
ACP support is included. Configure an ACP client to open a non-TTY stream to the sandbox.
sbx exec -i <sandbox> cursor-acp cursor-agent --force 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/cursor provides the complete agent workload.sbx/cursor-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.
Cursor is a product of Anysphere, Inc. Product names and logos do not imply sponsorship or endorsement.