> 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 about 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. 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 - **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, GitLab, or Azure DevOps during setup. Restricted organizations need owner approval. Azure DevOps also requires [one-time administrator approval](https://docs.warp.dev/factories/integrations/azure-devops/#requirements). ## Set up your factory *About 5 minutes* Note For GitHub and GitLab repositories, an agent connected to [Factory MCP](https://docs.warp.dev/factories/factory-mcp/#set-up-with-your-coding-agent) can run this whole setup. Use the web setup wizard for Azure DevOps. If the wizard is still open when the agent finishes, refresh the page to see the new factory. 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_4zwEvm2A1fAsewvcWtpQEVQfw81B) 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](https://docs.warp.dev/factories/code-forges/other-code-forges/). ![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_4zwEvm2A1fAsewvcWtpQEVQfw81B) 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](https://docs.warp.dev/factories/#sizing-a-factory) before adding a repository already covered by another factory. ![The Select your repos screen, searching for repositories by name.](https://docs.warp.dev/_astro/quickstart-select-repos.vvJnPUUQ_Won52.webp?dpl=dpl_4zwEvm2A1fAsewvcWtpQEVQfw81B) The repository selector for factory setup. 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 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_4zwEvm2A1fAsewvcWtpQEVQfw81B) 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](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_4zwEvm2A1fAsewvcWtpQEVQfw81B) Default factory agents enabled during setup. 6. Optionally, connect Slack and an issue tracker. 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 *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](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. ``` 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_4zwEvm2A1fAsewvcWtpQEVQfw81B) 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 - [**Connect your factory**](https://docs.warp.dev/factories/connect-your-factory/) - Configure intake sources. - [**How Warp Factories work**](https://docs.warp.dev/factories/how-factories-work/) - Understand the work-item lifecycle. - [**Troubleshooting Warp Factories**](https://docs.warp.dev/factories/troubleshooting/) - Fix common setup and run issues.