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.

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. Choose one event that starts the task, then check whether an existing automation already handles it. Update that automation or add one with nonoverlapping filters. See automation matching rules.

Route work to the agent responsible for the task and make the expected output explicit. When a workflow spans several roles, use the foreman to coordinate the other agents. Add or update skills for repository-specific procedures, such as required test commands or an incident runbook. Keep a human responsible for approving specifications, accepting risk, and merging changes.

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