Factories > Factory workers
About factory workers
Configure the workers that run Blueprint stages in Warp Factories, including their shared instructions, tools, models, and harnesses.
Factory workers are agents configured to run work in your factory. Your Blueprint assigns stages to these agents; their worker definitions select models, harnesses, tools, and shared instructions. The foreman is the worker that coordinates the top-level workflow and communicates with you.
Keep each stage’s procedure, required inputs, outputs, transitions, and human gates in the Blueprint. Put instructions that apply across stages in the worker definition.
The default workers
Section titled “The default workers”A new factory starts with these workers. Reassign stages or add custom workers when work needs different resources or instructions.
| Worker | What it does | What it produces |
|---|---|---|
| Foreman | Coordinates the top-level workflow and talks to the requester | Questions, status updates, and the final handoff |
| Lifecycle worker | Carries a change through triage, planning, implementation, and review in one conversation | The change, checks, review findings, and supporting evidence |
| Researcher | Answers a bounded question without changing code | Findings and sources |
Triage, planning, implementation, and review are stage responsibilities, not a requirement to create a separate worker for each one. A Blueprint can assign several stages to one worker or separate work that needs different tools or independent review.
Foreman
Section titled “Foreman”The foreman passes your request and prior decisions to the worker assigned by the top-level Blueprint. It gathers the stage’s inputs, runs stages assigned to itself, and delegates other stages to their workers. It reads the returned outputs and follows the matching transition, rather than repeating the worker’s investigation or implementation.
The foreman relays a worker’s questions to you and sends your answers back to that worker. Follow-ups and revisions continue the worker’s existing conversation, retaining the findings, branch, and PR.
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.
Stage responsibilities
Section titled “Stage responsibilities”Choose a worker for each stage in the Blueprint. These responsibilities describe an issue-to-PR workflow; your stage names and assignments can differ.
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 checks requirements, code conventions, tests, security, and supporting evidence. The default lifecycle worker reviews its own change; assign a separate worker when your workflow requires independent review. Review can rerun validation and recommend revisions, but it doesn’t approve or merge the pull request.
Built-in skills
Section titled “Built-in skills”The default workers include 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 workers
Section titled “Configuring and extending workers”For settings, prompts, models, and third-party authentication, see Configuring factory workers.
For new workers, skills, and stage assignments, see Creating custom workers. To start work from schedules and events, use factory automations.
Configure human decisions in the Blueprint. For access to repositories, secrets, and tools, see factory permissions and external access.