Droid Factory

Droid Factory install

Install custom Factory Droid subagents and delegate work using custom slash commands with a single `npx droid-factory` (or `bunx droid-factory`) call. By default it launches a guided, step‑by‑step installer where you pick the install location (personal or project) and choose which commands and droids to install; flags are available for non‑interactive “install everything” runs.

Usage

npx droid-factory

bunx droid-factory

The guided flow highlights existing files, lets you decide on overwrites, and ends with a concise summary.

Ensure **Custom Droids** are enabled in Factory (`/settings` → Experimental → Custom Droids) or by adding `"enableCustomDroids": true` to `~/.factory/settings.json`; otherwise the installed commands cannot launch their helper agents.

Guided flow

• Step 1/6 — Choose install location (Personal ~/.factory or Project ./.factory)
• Step 2/6 — Choose source (Templates or Marketplace)

Templates (bundled):

• Step 3/6 — Install all commands and droids?
• Step 4/6 — Select commands to install
• Step 5/6 — Select droids to install
• Step 6/6 — Overwrite existing files if found?
• Summary shows what was created/overwritten/skipped and next steps

Marketplace:

• Step 3/6 — Enter marketplace (path/url/owner/repo)
• Step 4/6 — Install all plugins?
• Step 5/6 — Select plugins to install
• Step 6/6 — Overwrite existing files if found?
• Summary shows what was created/overwritten/skipped and next steps

Optional flags (non-interactive)

• --yes — run without interactive confirmations
• --dry-run — preview actions and summary without writing files
• --scope personal|project and --path — target install location
• --commands all|name1,name2 and --droids all|name1,name2 — select what to install
• --only-commands, --only-droids — limit to one type
• --force — overwrite existing files
• --list — list available templates
• --verbose — print the detailed plan
• Market