Warp Factories quickstart

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

Prerequisites

If you don't have a Warp account, sign up for Warp. If you're not on a team, join or create a team before starting.

• Factory creation access - On an existing Warp team, you need team or workspace admin access, or the team-level Warp Factories Editor role. See factory roles and permissions.
• Usage requirements - Check your team's access and billing requirements. For usage charges, see platform-credit billing.
• Repository access - Access to the repositories you want the factory to work on. If your organization restricts connections to Warp, involve a code-host administrator.

Set up your factory

1. Open the <a href=https://platform.warp.dev>Warp Factories web app and sign in. Choose the Warp team that will own the factory, then click + next to Factories.

   

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.

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

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

   

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.

   

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

   

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

   

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

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:

   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:

   

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