Droid

This guide covers authentication, configuration, and usage of Droid, an AI coding agent by Factory, in a sandboxed environment.

Official documentation: Droid

Quick start#

[!NOTE] In Docker Sandboxes v0.42, use sbx run docker.io/sbx/droid-kit:latest. The droid shorthand is unavailable in this release.

Create a sandbox and run Droid for a project directory:

$ sbx run droid ~/my-project

The workspace parameter is optional and defaults to the current directory:

$ cd ~/my-project
$ sbx run droid

Authentication#

Droid requires a Factory account. Both authentication methods authenticate you to Factory's service directly — unlike other agents where you supply a model provider key, Factory manages model access through your Factory account.

API key: Store your Factory API key using stored secrets:

$ sbx secret set droid

OAuth: If no API key is set, Droid prompts you to authenticate interactively on first run. The proxy handles the OAuth flow, so credentials aren't stored inside the sandbox.

Configuration#

Sandboxes don't pick up user-level configuration from your host. Only project-level configuration in the working directory is available inside the sandbox. See Why doesn't the sandbox use my user-level agent configuration? for workarounds.

Default startup command#

The sandbox runs droid with no implicit flags. Args after -- are passed straight through:

$ sbx run droid -- exec "fix the build"

Base image#

Template: docker/sandbox-templates:droid-docker

Preconfigured to run without approval prompts. Authentication state is persisted across sandbox restarts.

See Customize to pre-install tools or customize this environment.