Skip to main content

Agent guide

Droid extends the fleet for teams that want Factory AI’s runtime available alongside the rest of their Conductor-managed agents without hiding the routing behind shell scripts.

Binary: droidAlias: droidBest for specialized workflows

Primary binary

droid

Known aliases

droid

Good fit

Fleet diversity, specialized workflows, and plugin-native isolation.

​
Set up Droid in Conductor

1

Install Droid

2

Complete the vendor setup flow

Finish any authentication or environment-specific setup required for the Droid CLI before launching Conductor.
3

Launch Conductor

Select Droid only for the repositories or workflows where it is the right runtime choice.
4

Set the project default

​
Model selection in Conductor

Droid model choices depend on the Factory runtime configuration available on that machine.
  • leave agentConfig.model unset when Droid already has a preferred default configured
  • add a repo-level override only when the underlying Droid setup expects an explicit model value
  • keep one clear Droid default per repository so teammates can understand why the runtime was chosen

​
Why teams pick Droid

  • broadens the available fleet without adding a shell fallback
  • useful for specialized team workflows
  • keeps isolation and config explicit
Last modified on March 29, 2026