# Droid CLI

Use the Droid CLI to run Factory from your terminal, editor, tests, and Git workflow.

Use the Droid CLI when you want Droid beside your shell, editor, tests, and Git workflow. It gives the same Factory runtime through an interactive terminal UI with project context, approvals, MCP tools, Missions, and headless execution.

## When to use the CLI

- You want Droid to work in the same terminal where you run Git, tests, and scripts.
- You prefer keyboard-first review of plans, tool calls, and diffs.
- You need quick access to shell commands, slash commands, and project-local context.
- You want a path from interactive work to `droid exec` automation.

<Note>
  **Quick tip:** Press <Kbd>!</Kbd> to toggle bash mode and run shell commands directly without AI interpretation. Press <Kbd>Esc</Kbd> to return to normal mode. See the [CLI Reference](/droid-cli/cli-reference#bash-mode) for details.
</Note>

## Key capabilities

The full Factory platform is available from the terminal. Launch multi-agent [Missions](/missions/overview) with `/missions` or `droid exec --mission`, delegate scoped tasks to [Custom Droids](/harness/subagents) via `/droids`, and package reusable procedures as [Skills](/harness/skills) with `/skills` or `/create-skill`.

To extend the harness, connect external tools and data sources over [MCP](/harness/mcp) (`droid mcp add` or `/mcp`), run shell commands around agent lifecycle events with [Hooks](/harness/hooks) (`/hooks`), and install bundles of commands, droids, skills, and hooks as [Plugins](/harness/plugins) (`droid plugin install` or `/plugins`). When a workflow stabilizes, take it headless with [Exec Mode](/droid-exec/overview): `droid exec` runs in scripts and CI/CD pipelines with structured input and output formats.

## What `droid` brings to your workflow

Droid plans, implements, tests, and reviews changes end to end while approval workflows keep you in control. It works from deep codebase understanding: project files, repository instructions, and connected knowledge inform every answer and scoped change. Connect Jira, Notion, Slack, Linear, PagerDuty, and MCP tools to keep development synchronized with team systems, and move repeatable local workflows into Droid Exec for scripts and CI/CD pipelines.

<RelatedLinks>
  <RelatedLink href='/harness/agents-md' title='AGENTS.md Guide'>
    Configure project-specific guidance and conventions.
  </RelatedLink>
  <RelatedLink href='/harness/skills' title='Skills'>
    Package reusable procedures as self-contained workflows.
  </RelatedLink>
</RelatedLinks>