> 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 quickstart

Set up a factory, connect your repositories, and take your first work item from prompt to pull request in less than 10 minutes.

Note

Warp Factories is in **Early Access** and available to a limited set of teams. [Request access](https://www.warp.dev/factories/request-access) to use it with your team.

A factory is a fleet of agents wired to your software development lifecycle. It connects your repositories and tools to move requests through triage, specification, implementation, review, and verification, while people stay in control of key decisions. You talk to one agent, the **foreman**. It picks up the request from wherever it starts, such as Slack, an issue tracker, or a code host, then dispatches the factory’s other agents, each owning one part of the software development lifecycle.

In this quickstart, you will create a factory and take one small work item from prompt to pull request in less than 10 minutes.

## What you’ll decide

Setup connects your code host, selects repositories, names the factory and its foreman, and chooses default agents. You can also connect Slack and an issue tracker now or add them later. Every choice can be changed after setup.

## Prerequisites

-   **Warp Factories access** - [Request Early Access](https://www.warp.dev/factories/request-access) for your team.
-   **A Warp team with credits** - The team’s [credits](https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/) are consumed by factory agents.
-   **Repository access** - Authorize GitHub or GitLab during setup. If your organization restricts app installations, ask an owner to approve the connection.

## Set up your factory

*~5 minutes*

Note

An agent connected to [Factory MCP](https://docs.warp.dev/factories/factory-mcp/#set-up-with-your-coding-agent) can run this whole setup: ask it to set up a factory, and it walks you through the same choices as the wizard. If this wizard is still open when the agent finishes, refresh the page to see the new factory.

Warp walks you through a setup wizard:

1.  Sign in to the [Warp Factories web app](https://platform.warp.dev). Next to **Factories**, click **+**.
    
    ![The Factories section of the sidebar, with the + button used to start a new factory highlighted.](https://docs.warp.dev/_astro/quickstart-open-setup-wizard.BsjqM_jG_Z22uxA5.webp?dpl=dpl_GTCTkCLXXphZy1WXx34PT8T4ajgM)
    
    Click + next to Factories to open the setup wizard.
    
2.  Click **I want to use repos from GitHub** or **I want to use repos from GitLab**, then choose the organization or group to connect.
    
    ![The Connect a GitHub organization screen, with an already-connected organization shown as an option.](https://docs.warp.dev/_astro/quickstart-connect-organization.xjPpRRMC_28SywJ.webp?dpl=dpl_GTCTkCLXXphZy1WXx34PT8T4ajgM)
    
    Choose the organization or group whose repositories the factory will use. GitLab shows an equivalent screen for groups.
    
3.  On **Select your repos**, select the repositories the factory works in, then click **Add repos**. Start with one or two repositories that ship together, and add more later. See [sizing a factory](https://docs.warp.dev/factories/#sizing-a-factory) before adding a repository another factory already covers.
    
    ![The Select your repos screen, searching for repositories by name.](https://docs.warp.dev/_astro/quickstart-select-repos.vvJnPUUQ_Won52.webp?dpl=dpl_GTCTkCLXXphZy1WXx34PT8T4ajgM)
    
    Search for and select the repositories the factory works in.
    
4.  Name the factory. This also sets its [**Foreman name**](https://docs.warp.dev/factories/factory-agents/#foreman-name), the handle your team @-mentions in Slack and Linear. The factory and foreman names match by default, but the foreman is the agent that coordinates its work.
    
    ![The Give your factory some personality screen, with Factory name and Foreman name fields filled in.](https://docs.warp.dev/_astro/quickstart-name-factory.BK0E3IiM_Z1wspQF.webp?dpl=dpl_GTCTkCLXXphZy1WXx34PT8T4ajgM)
    
    Name the factory and, optionally, add a description and avatar.
    
5.  Toggle the agents the foreman can dispatch: **Triage**, **Spec**, **Implement**, and **Review**. All four start enabled. Leave **Implement** on so this quickstart can end in a pull request. See [factory agents](https://docs.warp.dev/factories/factory-agents/) for details.
    
    ![The Pick your factory agents screen, with the Foreman and all four default agents shown as enabled.](https://docs.warp.dev/_astro/quickstart-pick-agents.BUka92hr_Z1FQAAD.webp?dpl=dpl_GTCTkCLXXphZy1WXx34PT8T4ajgM)
    
    Toggle which default agents the foreman can dispatch.
    
6.  Optionally connect Slack and an issue tracker so teammates can hand work to the factory from the tools they already use. You can add either later from [connect your factory](https://docs.warp.dev/factories/connect-your-factory/).
    

Warp creates the factory and opens its [dashboard](https://docs.warp.dev/factories/factory-dashboard/).

## Send your first work item

*~5 minutes*

Send work from Slack or an issue tracker. If you skipped integrations, start a run from the **Runs** page of the factory’s [dashboard](https://docs.warp.dev/factories/factory-dashboard/).

1.  Describe one small, verifiable change and send it:
    
    ```text title="Example first request"
    Add a "Local development" section to README.md that summarizes the setup
    steps from CONTRIBUTING.md. Keep the change to that one file, run the
    repo's lint check, and open a pull request.
    ```
    
    Name the file, expected change, and verification command.
    
2.  The foreman dispatches the agents needed for the request and posts progress where it started. Follow the foreman and child runs on the factory’s [Runs page](https://docs.warp.dev/factories/factory-dashboard/#inspect-runs). Requests for input also appear in your [inbox](https://docs.warp.dev/factories/factory-inbox/).
    
    If you connected Slack, you can follow along there instead:
    
    ![A Slack thread where the Warp Factories app replies with tracking and triage progress updates, including links to open the session and view it in the factory.](https://docs.warp.dev/_astro/slack-factory-thread-reply.IqsWzCLm_1o1zNQ.webp?dpl=dpl_GTCTkCLXXphZy1WXx34PT8T4ajgM)
    
    The factory’s Slack app posting progress updates back in the thread where you sent the request.
    
3.  When the Implement agent finishes, review and merge the linked pull request as you would any other.
    

## Next steps

-   [**Connect your factory**](https://docs.warp.dev/factories/connect-your-factory/) - Configure intake sources.
-   [**Factory MCP**](https://docs.warp.dev/factories/factory-mcp/) - Send work from a coding agent or MCP client.
-   [**How Warp Factories work**](https://docs.warp.dev/factories/how-factories-work/) - Understand the work-item lifecycle.
-   [**warp-factory-examples**](https://github.com/warpdotdev/warp-factory-examples) - Complete working definitions to copy, from a single-repo quickstart to the full issue-to-PR lifecycle.
-   [**Troubleshooting Warp Factories**](https://docs.warp.dev/factories/troubleshooting/) - Fix common setup and run issues.