Warp Factories quickstart

A factory is a team of cloud agents — a foreman you talk to, plus the subagents it dispatches — that turns incoming requests into pull requests for your team to review. In this quickstart, you will create a factory, connect a GitHub repository, and take one small work item from prompt to pull request in about 10 minutes.

Prerequisites

• A Warp team with credits - A factory belongs to a Warp team. Factory agents consume the team’s credits. If the team has no active plan, you will be asked to select one during setup.
• GitHub repository access - Authorize GitHub and choose repositories during setup. If your organization restricts app installations, ask a GitHub organization owner to approve the connection. See the GitHub integration for details.

Create your factory

~5 minutes

1. Open the Warp Factories web app and sign in

   Go to the Warp Factories web app at platform.warp.dev and sign in.

2. Start the setup wizard

   In the sidebar, next to Factories, click +.

   Note

   No team yet? The wizard first asks you to choose the team that will own the factory. If that team has no plan or credits, it opens Select a Warp Plan — a factory needs credits to run its agents.

3. Connect GitHub

   Click I want to use repos from GitHub and complete the GitHub authorization.

4. Select your repositories

   Choose the repositories the factory will work in and click Add repos. Start with one or two repositories — every agent in the factory shares this repo set, so a focused set keeps their context tight.

   Warp provisions a default environment for the selected repos.

5. Name your factory

   Enter a Factory name, such as Payments services. Warp derives a matching Factory alias, the handle teammates use to @-mention the factory from connected tools like Slack and Linear. Keep it short and recognizable.

6. Skip integrations for now

   The next screen offers to connect Slack. This quickstart skips integrations, so click Next. You can connect them any time from Connect your factory.

7. Choose your agents

   The foreman leads every factory — it’s the orchestration agent you interact with directly. Below it, toggle the subagents it can dispatch: Triage, Spec, Code, and Review. All four start enabled, and at least one is required. Keep Code on so this quickstart’s work item can end in a pull request.

   See Factory agents for what each role does.

8. Create the factory

   Skip the issue tracker screen the same way as Slack: click Next. Warp creates the factory.

   When the startup screen reports Factory running!, click Go to dashboard.

Submit your first work item

~5 minutes

1. Open Runs and start a new run

   In the sidebar under your factory, open Runs and click New.

2. Describe your work item

   Describe one small, verifiable change and submit 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.

   Adapt the pattern to your repository: name the file, the change you expect, and the command that verifies it. A narrow, explicit request makes the first run easy to judge.

   The foreman picks up the request as a run on Runs and dispatches your subagents as child runs.

3. Watch the run

   Follow progress from two pages in your factory’s sidebar:

   • Runs - The foreman’s run and the child runs it dispatches.
   • Activity - The work item as it moves through its stages. Open it to see its event history and pull request artifacts.

4. Review and merge the pull request

   When the Code agent finishes, the work item links a pull request in GitHub. Review and merge it through your normal process — the factory drafts the change, and your team makes the call.

Next steps

• Connect your factory - Route work in from Slack threads, Linear issues, and other intake paths.
• Factory MCP - Send work to the factory from a coding agent or MCP client.
• How Warp Factories work - The work-item lifecycle and where people stay in the loop.
• Troubleshooting - Fixes for common issues during setup and your first runs.