Share feedback
Answers are generated based on the documentation.

Droid

Availability: Experimental

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

Official documentation: Droid

Quick start

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 -g droid

Alternatively, export the FACTORY_API_KEY environment variable in your shell before running the sandbox. See Credentials for details on both methods.

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.

The sandbox runs Droid without approval prompts by default. Pass additional droid CLI options after --:

$ sbx run droid --name <sandbox-name> -- <droid-options>

Base image

Template: docker/sandbox-templates:droid-docker

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

See Custom environments to pre-install tools or customize this environment.