Warp Factories quickstart

Create your first factory and take one small work item from prompt to pull request.

Prerequisites

• A Warp account and membership in a Warp team.
• Team or workspace admin access, or the team-level Warp Factories Editor role.
• Available usage in your team’s balance for factory runs. See access and billing requirements.
• Access to the repositories you want the factory to work on.

Set up your factory

Note

For GitHub and GitLab repositories, an agent connected to Factory MCP can run this setup. For Azure DevOps, follow the steps below in the Warp Factories web app. If the setup page is still open when the agent finishes, refresh it to see the new factory.

1. Open the Warp Factories web app and sign in if prompted. To switch teams, click your avatar, hover over the team name, and select another team.

2. Click + next to Factories.

   

   The factory setup control in the sidebar.

3. On the “Connect your code hosts” screen, select GitHub, GitLab, or Azure DevOps, then choose the organization or group to connect. For Azure DevOps, also choose a project. Click Next.

   If your organization restricts connections to Warp, involve a code-host administrator.

   Azure DevOps organizations require one-time administrator approval. The setup flow lets you send the approval link to the required administrators.

   For other code forges, see Connecting other code forges to your factory.

   

   The GitHub organization dropdown in factory setup.

4. On the “Set up your factory” screen, select the repositories your factory will work on. See sizing a factory.

   

   A repository search during factory setup.

5. Enter a “Factory name”. This also sets the default foreman name, the handle your team @-mentions in Slack and Linear. Click Next.

   

   The factory name and optional details during setup.

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

   

   Default factory agents enabled during setup.

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

Send a request to your factory’s foreman from the Warp Factories web app. You can also send work from Slack or an issue tracker.

1. In the sidebar, click New Chat.

2. In the dropdown below the prompt input, choose your factory.

3. Enter one small, verifiable change, then click the send arrow:

   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.

4. The foreman dispatches the agents needed for the request and posts progress where it started. In the sidebar, click Runs to follow the foreman and child runs. Requests for input also appear in your inbox.

   If you sent the request from Slack, you can follow along in its thread:

   

   A factory Slack thread with live progress.

5. When the foreman hands back the pull request, review the changes and validation results, then merge it according to your normal process.

Next steps

• Connect your factory - Configure intake sources.
• How Warp Factories work - Understand the work-item lifecycle.
• Troubleshooting Warp Factories - Fix common setup and run issues.