Factory Droid CLI overlay with authentication, network policy, and native ACP support.
10K+
Factory Droid CLI overlay with authentication, network policy, and native ACP support.
| Name | Required | Default | Description |
|---|---|---|---|
version | Required | — | Factory Droid release carried by the image |
[email protected]| Type | Required | Description | |
|---|---|---|---|
com.docker.sandbox/network-policy@1 | Required | — | |
com.docker.sandbox/credential@1 | Optional | Factory API access for Droid (API key or WorkOS OAuth) | |
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 | — | |
sbx run <agent> --kit sbx/droid-mixin:latestRun the following command to install sbx on your machine.
brew install docker/tap/sbxwinget install Docker.sbxThis v3 mixin Kit packages Factory Droid 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/droid-mixin:latest /path/to/workspace
When the shell opens, run droid. This kit supplies an overlay, so it needs a workload such as
Shell.
This kit has no create-time kit arguments.
Bind a Factory API key on the host with sbx secret set droid, or use the runtime's Droid OAuth support. Host-bound
credentials remain proxy-managed.
With no bound API key, start droid and complete the first-use OAuth flow through the runtime. A bound droid API key
takes priority over OAuth.
ACP support is included. Configure an ACP client to open a non-TTY stream to the sandbox.
sbx exec -i <sandbox> droid exec --output-format 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/droid provides the complete agent workload.sbx/droid-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.
Droid is a product of Factory. Product names and logos do not imply sponsorship or endorsement.