Skip to content
Warp

Factories > Overview

Warp Factories quickstart

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

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

Create a factory and take one small work item from prompt to pull request in about 10 minutes. This quickstart is for teams that already have Warp Factories access and know which repositories they want the factory to use.

Prerequisites

Section titled “Prerequisites”
  • Warp Factories access - Request Early Access for your team.
  • A Warp team with credits - The team’s credits are consumed by factory agents.
  • Repository access - Authorize GitHub, GitLab, or Azure DevOps during setup. Restricted organizations need owner approval. Azure DevOps also requires one-time administrator approval.

Set up your factory

Section titled “Set up your factory”

About 5 minutes

  1. Sign in to the Warp Factories web app. Next to Factories, click +.

    The Factories section of the sidebar, with the + button used to start a new factory highlighted.

    The factory setup control in the sidebar.

  2. Under Connect your code hosts, connect GitHub, GitLab, or Azure DevOps. Choose the GitHub organization, GitLab group, or Azure DevOps organization and project to connect.

    To use another code forge, select No repo, finish creating the factory, then configure repository access from the default runner.

    The Connect a GitHub organization screen, with an already-connected organization shown as an option.

    Connected GitHub organizations available during setup.

  3. On Select your repos, select one or two repositories that ship together, then click Add repos. See sizing a factory before adding a repository already covered by another factory.

    The Select your repos screen, searching for repositories by name.

    The repository selector for factory setup.

  4. Name the factory. This also sets its Foreman name, the handle your team @-mentions in Slack and Linear.

    The Give your factory some personality screen, with Factory name and Foreman name fields filled in.

    Identity settings for the factory and foreman.

  5. Choose which agents the foreman can dispatch. Leave Implement enabled so this quickstart ends in a pull request. See factory agents for details.

    The Pick your factory agents screen, with the Foreman and all four default agents shown as enabled.

    Default factory agents enabled during setup.

  6. Optionally, connect Slack and an issue tracker. You can add either later from connect your factory.

Warp creates the factory and opens its dashboard.

Send your first work item

Section titled “Send your first work item”

About 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.

  1. Describe one small, verifiable change and send it:

    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.

  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. Requests for input also appear in your 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.

    A factory Slack thread with live progress.

  3. When the Implement agent finishes, review and merge the linked pull request as you would any other.

Next steps

Section titled “Next steps”