> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Warp Factories overview

Warp Factories turns issues, tickets, and Slack requests into reviewed pull requests with teams of cloud agents, while people approve specs and merges.

A factory is a team of cloud agents attached to a set of repositories. It takes work from Slack, GitHub, Linear, or Jira through triage, spec, implementation, and review, and returns the result, usually a pull request, where the work started.

[Open Warp Factories](https://platform.warp.dev)Sign in to create a factory or open one your team already uses.

[Create your first factory](https://docs.warp.dev/factories/quickstart/)Connect repositories and send a small, verifiable work item.

## What a factory does

A factory can work through a backlog of issues, fix defects reported in a support channel, or review incoming pull requests across several repositories.

![Introducing Warp Factories](https://i.ytimg.com/vi/0WBk4ai8y1A/sddefault.jpg)

![A circular diagram of the software factory loop: triage, spec, implement, review, verify, ship, and monitor, with human review checkpoints for the spec, code, and product.](https://docs.warp.dev/_astro/factories-concept-loop.D5J0xtAi_PLdIR.webp?dpl=dpl_2o3oiWZysLsAJSjVGUrSrTobmuWE)

The software factory loop. The default agents cover triage through review.

## The parts of a factory

### Work items

A work item is one request the factory acts on: an issue, a support thread, a pull request, or a scheduled job. It keeps its source context from intake to handoff, however many agents contribute along the way.

### Foreman and factory agents

The foreman routes work, asks for decisions, and hands back results. The default triage, spec, implement, and review agents cover the development workflow; add custom agents for other tasks. Configure each agent’s model and harness, including the Warp Agent, Claude Code, or Codex. See [factory agents](https://docs.warp.dev/factories/factory-agents/) for support and configuration.

Setup gives the foreman the same handle as the factory, so `payments` is the factory and `@payments` reaches its foreman from Slack or Linear. See [Foreman name](https://docs.warp.dev/factories/factory-agents/#foreman-name).

### Stages and checkpoints

Work moves through Triage, Planning, Building, and Reviewing. The foreman can skip unnecessary stages or send work back for revisions. Spec approval is part of its editable instructions, not a repository permission. The factory never merges; your repository’s permissions and branch protection control approval and merge access. See [how Warp Factories work](https://docs.warp.dev/factories/how-factories-work/).

### Factory definition

A factory’s repositories, agents, automations, runners, skills, and MCP servers are declared in definition files, either managed by Warp or stored in a GitHub repository your team owns. Changes to a GitHub-backed factory go through pull request review like any other code. See [definitions as code](https://docs.warp.dev/factories/factory-as-code/).

### Work sources

Connect chat, issue trackers, and code forges through [factory integrations](https://docs.warp.dev/factories/connect-your-factory/). Results return to the thread, issue, or pull request where work began. Use [custom webhooks](https://docs.warp.dev/factories/webhooks/) or [factory endpoints](https://docs.warp.dev/factories/factory-api/) for other systems, and [automations](https://docs.warp.dev/factories/automations/) for scheduled work.

The [Factory MCP](https://docs.warp.dev/factories/factory-mcp/) lets a local coding agent send work to a factory, take it over locally, and hand it back.

### Execution

Every agent run in a factory is an ordinary [cloud agent run](https://docs.warp.dev/platform/) on the Automation Platform. Runs execute on Warp-hosted compute by default; Enterprise teams can keep checkout and execution on their own infrastructure with [managed self-hosting](https://docs.warp.dev/factories/self-hosting/). See [infrastructure and security](https://docs.warp.dev/factories/infrastructure-and-security/) for runners, inference, and credential boundaries.

### Measurement

Use the [factory dashboard](https://docs.warp.dev/factories/factory-dashboard/) to inspect PR activity, autonomy, cycle time, and cost. [Scorers](https://docs.warp.dev/factories/measure-and-improve/scorers/) classify runs against your criteria; [benchmarks](https://docs.warp.dev/factories/benchmarks/) compare configurations on the same tasks; [Self-improvement](https://docs.warp.dev/factories/measure-and-improve/self-improvement/) proposes changes for review. See [measure and improve](https://docs.warp.dev/factories/measure-and-improve/) for definitions and limitations.

## Sizing a factory

Group the repositories that ship together into one factory, and keep separate products in separate factories. For example:

-   One factory for your main application
-   One factory for your marketing site
-   One factory for your data pipelines

Don’t split the same repositories across factories by team or task, such as frontend and platform. Add [agents](https://docs.warp.dev/factories/factory-agents/) and [skills](https://docs.warp.dev/factories/factory-skills/) to specialize instead.

## Related pages

-   [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/) - Create a factory and send its first work item.
-   [How Warp Factories work](https://docs.warp.dev/factories/how-factories-work/) - The work-item lifecycle, stage by stage.
-   [Factory agents](https://docs.warp.dev/factories/factory-agents/) - What each default agent does and how to configure its model and harness.
-   [Definitions as code](https://docs.warp.dev/factories/factory-as-code/) - The definition file format, with working examples in [warp-factory-examples](https://github.com/warpdotdev/warp-factory-examples).
-   [Transitioning from Oz](https://docs.warp.dev/platform/transitioning-from-oz/) - Assess an existing web app, CLI, SDK, or API workflow.
-   [Get started with the Warp team](https://www.warp.dev/get-started) - Get help choosing and setting up a workflow.