Factories > Factory agents
About factory agents
Configure the foreman, triage, spec, implement, and review agents in Warp Factories, or add custom agents for your development workflows.
Factory agents run the work in your development workflow. The foreman coordinates the workflow and communicates with you; other agents investigate requests, plan changes, implement them, or review the result.
With a Blueprint, you assign agents to stages and define each stage’s procedure, required inputs, and outputs. The Blueprint also controls handoffs, revision routes, and human gates. Agent configuration supplies the models, harnesses, tools, and shared instructions those stages use.
The default agents
Section titled “The default agents”Every factory has a foreman. The default roles below are starting points, not required stages. Reuse them in your Blueprint or add custom agents for work that needs different resources or instructions.
The default agents’ prompts, descriptions, and models are available in 00-warp-default-agents in the warp-factory-examples repository.
| Agent | What it does | What it produces |
|---|---|---|
| Foreman | Coordinates the work and talks to the requester | Decisions, questions, status updates, and the final handoff |
| Triage | Investigates the request and establishes scope | Evidence, issue context, complexity, and open questions |
| Spec | Turns requirements into a concrete plan with validation criteria | Product and technical specs in a draft pull request |
| Implement | Makes and validates the code change | Code, tests, validation results, and visual evidence |
| Review | Independently checks the finished change | Findings and a recommendation |
These are responsibilities, not a fixed pipeline. In a Blueprint, configure routes to skip planning for well-defined work or return review findings for revision. Add a plan-review gate when implementation must wait for approval. Definitions without a Blueprint keep these decisions in the foreman’s instructions.
For the complete lifecycle, see How Warp Factories work.
Foreman
Section titled “Foreman”The foreman drives the top-level Blueprint. It gathers each stage’s inputs from the request and earlier outputs, runs stages assigned to itself in its conversation, and delegates other stages to their workers. It relays questions and answers and continues an agent’s existing conversation for revisions rather than starting a new one.
A worker can coordinate a group of stages. It handles that group’s internal handoffs and returns the group’s result to the foreman.
After implementation and review, the foreman returns the pull request and supporting evidence, then waits for your team to merge. By default, the foreman marks the work item complete on a later merge notification or your confirmation that the pull request landed.
Foreman name
Section titled “Foreman name”Use the foreman’s handle to @-mention it in Slack and Linear. Factory setup defaults the handle to the factory’s name. For example, a factory named payments gets the handle @payments.
The factory name and foreman handle can differ. To change the foreman’s handle, open your factory’s Settings in the web app and click Identity. You can also edit alias in the definition.
Triage
Section titled “Triage”Triage researches the codebase and related issues, reproducing problems when research doesn’t establish the cause. It reports scope, complexity, and open questions so the foreman can choose clarification, planning, or implementation.
Spec defines requirements through the foreman and writes specifications with validation criteria in a draft pull request. Put approval requirements in the planning stage’s gates and route implementation only from approval of the current plan.
Implement
Section titled “Implement”Implement builds on the spec’s branch and draft pull request. It adds tests, runs repository checks, and captures visual evidence of user-facing changes when computer use is available. It revises changes after review but never merges.
Review
Section titled “Review”Review independently checks requirements, code conventions, tests, security, and supporting evidence. It reruns or extends validation when needed, then recommends acceptance, revisions, or a human decision. It doesn’t approve or merge the pull request.
Built-in skills
Section titled “Built-in skills”Every default agent includes GitHub skills; the foreman also includes a Slack skill. Choosing Linear or Jira during setup adds that tracker’s skill and instructions. You can add custom procedures with factory skills.
Configuring and extending agents
Section titled “Configuring and extending agents”For settings, prompts, models, and third-party authentication, see Configuring factory agents.
For new roles, skills, and stage-worker assignments, see Creating custom agents. To start work from schedules and events, use factory automations.
Human decision points and permissions
Section titled “Human decision points and permissions”| Decision | Default behavior | What enforces it |
|---|---|---|
| Spec approval | The planning stage asks for approval before implementation when the workflow requires it | Blueprint gates and routes; foreman instructions in definitions without a Blueprint |
| Merging | The foreman hands you the finished pull request. Agents never merge on your behalf. | Your repository’s permissions decide who can approve and merge |
| Runtime access | Each agent reaches only the repositories, secrets, and MCP servers in its configuration | Platform configuration and the permissions of the connected providers |
Change workflow policy in the Blueprint, not a second stage list in an agent prompt. Gates guide the workflow; repository permissions and branch protection enforce who can approve and merge. Changing instructions does not grant tool, repository, or credential access.