Tool profile

Factory Droid

ByFactoryUS

Factory software engineering agent, with an interactive CLI and headless mode, multi-agent missions and IDE plugins.

Factory Droid wordmark in white on a dark gradient background
Country
US
Availability
Proprietary
Modalities
  • Text
  • Code

Factory Droid is Factory’s software engineering agent. The canonical product name is Droid; “Factory Droid” is the form used here for disambiguation. The proposition is to bring the same agent to different surfaces, from the terminal to the cloud.

What it’s for

  • Executing multi-step engineering tasks from a description
  • Running the agent interactively in the terminal or automatically in scripts and CI
  • Organizing missions with several agents and specialized subagents
  • Bringing the same flow to the editor, the app and messaging integrations

How it works

  • The CLI has an interactive mode and a headless mode with text or structured output
  • You can define subagents and autonomy levels, from the most contained to the most permissive
  • Extra capabilities come from skills, plugins and the MCP protocol
  • The agent is model-independent and accepts your own key or custom models

Where it runs

  • Command line, including headless execution
  • Desktop app and web/mobile versions
  • Editor plugins, through an agent protocol
  • CI pipelines, messaging integrations and management tools

Availability and licensing

  • Proprietary product, with a package distributed under a license that does not allow use to build a competing product
  • The public repository is for documentation and community, not the agent’s code
  • Official SDKs are available for automation integration

How it differs

  • The same runtime covers terminal, editor, cloud and CI instead of separate surfaces
  • Multi-agent missions and subagents are part of the product core
  • The entry describes the Factory agent, not the company as a whole

Things to note

  • Higher-autonomy modes widen what the agent may change without confirmation
  • Some features depend on the plan and configured integrations
  • Reviewing permissions and diffs remains part of the flow