Sign inSign up
droid-mixin logo

sbx/droid-mixin

Verified Publisher

By Docker, Inc

•Updated about 19 hours ago

Factory Droid CLI overlay with authentication, network policy, and native ACP support.

Sandbox Kit
0

10K+

sbx/droid-mixin repository overview

Digest

sha256:2b5429d31eaa…

Size

138.1 MB

Schema

v3

Pushed

about 19 hours ago

Specificationspec.yaml

MIXIN

Factory Droid CLI overlay with authentication, network policy, and native ACP support.


Arguments
NameRequiredDefaultDescription
versionRequired—

Factory Droid release carried by the image



CapabilitiesExpand a row to see its full configuration. See the full spec for the complete descriptor.
TypeRequiredDescription
com.docker.sandbox/network-policy@1Required—
com.docker.sandbox/credential@1OptionalFactory API access for Droid (API key or WorkOS OAuth)
com.docker.sandbox/lifecycle@1Required—
com.docker.sandbox/agent-context@1Optional—
com.docker.sandbox/agent-context@2Optional—
com.docker.sandbox/acp@1Optional—

Apply this mixin to a sandbox

sbx run <agent> --kit sbx/droid-mixin:latest

Make sure you have docker sbx installed

Run the following command to install sbx on your machine.

macOS
brew install docker/tap/sbx
Windows
winget install Docker.sbx
Learn more about docker sbx⁠

⁠Factory Droid mixin for Docker Sandboxes

This 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.

⁠Run

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⁠.

⁠Kit arguments

This kit has no create-time kit arguments.

⁠Authentication and configuration

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.

⁠Source and security

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.