Factory use cases

A recipe is a recommended configuration and set of instructions for completing a specific task with your factory. Recipes combine agents, automations, integrations, skills, and repository controls. Test the recipe’s results before expanding the workflow. For example, check that issue triage categorizes issues correctly before adding implementation.

Each guide links to the canonical configuration and integration references. The examples use definitions as code so you can review changes, validate them in CI, and adapt the same pattern to a Warp-managed factory.

Choose a use case

Issue triageInvestigate, categorize, and prioritize incoming issues.

Code reviewReview pull requests and return actionable findings.

Issue implementationTurn approved GitHub, Linear, or Jira issues into tested pull requests.

Production incident resolutionInvestigate production signals and propose or implement a fix.

Computer Use verificationExercise a rendered interface and attach visual evidence.

End-to-end SDLC automationConnect triage, implementation, review, and verification with human gates.

Start with the smallest recipe

Use one factory with the repositories that ship together. Add an automation for one clear intake event, route it to the agent responsible for that task, and make the expected output explicit. Keep a human responsible for approving specifications, accepting risk, and merging changes.

When a workflow spans several roles, prefer the default foreman, triage, spec, implement, and review agents before creating custom agents. Add a custom skill for repository-specific procedures, such as required test commands or an incident runbook.

Related pages

• Warp Factories quickstart - Create a factory and send its first work item.
• Factory agents - Configure the default roles and add custom agents.
• Factory automations - Route provider events to agents with filters.
• Factory definition syntax - Look up configuration keys and validate definitions.