Factory Droid
Operating Factory Droid on workers — FACTORY_API_KEY or login, autonomy levels and the adapter setting that changes them.
Install
npm install -g droidThe worker looks for droid on the worker user's PATH.
Sign-in
Sign in to droid once as the worker's user, or put FACTORY_API_KEY in the task's environment profile.
Without either a run ends with "Authentication failed".
How it runs
droid exec --output-format stream-json --auto medium [-m <model>] -f <prompt file>
- Without
--auto,droid execis read-only.mediumallows edits, builds, package installation and local Git, but nogit push. - Change the level per worker with the adapter setting
autonomy:low,mediumorhigh. - The task is read from the prompt file with
-f.
Add-on models
Factory Droid cannot use add-on models or providers configured on the worker. When it reaches its limit, the task moves to another compatible agent, or waits, as the fallback policy says.
Sessions
Resume is not claimed for Factory Droid: no resume command could be verified without an account. After a crash, recovery starts a fresh session from the checkpoint.
What was verified
Checked against Factory Droid 0.233.0 on 2026-10-06: its --help, and a real run without credentials through
the worker's session runtime. A task with the vendor's account has not been run.