Skip to content

Factories > Factory workers

About factory workers

Configure the workers that run Blueprint stages in Warp Factories, including their shared instructions, tools, models, and harnesses.

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

Factory workers run the stages in your Blueprint. The foreman coordinates the workflow and communicates with you. Other workers run assigned stages using their configured models, harnesses, tools, and shared instructions.

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.

A new factory starts with these workers. Reassign stages or add custom workers when work needs different resources or instructions.

WorkerWhat it doesWhat it produces
ForemanCoordinates the top-level workflow and talks to the requesterQuestions, status updates, and the final handoff
Lifecycle workerCoordinates the development stages within its assigned groupThe group’s result and supporting evidence
ResearcherInvestigates a scoped questionFindings 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.

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 a worker’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.

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.

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 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 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 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.

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.

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.