Factories > Factory workers
Configuring factory workers
Configure a factory worker's instructions, tools, model, and harness, including authentication for Claude Code, Codex, and Pi.
Configure an existing factory worker’s instructions, tools, and runtime in the Warp Factories web app or its definition files.
Prerequisites
Section titled “Prerequisites”- Editor access to this factory, or team or workspace admin access.
- An existing factory worker. See About factory workers for the default roles, or Creating custom workers to add a role.
Choose what to change
Section titled “Choose what to change”Keep workflow changes in the Blueprint and worker resources in worker configuration:
| Change | Where to edit |
|---|---|
| What a stage does and returns | The stage’s prompt, inputs, and outputs in factory.yaml |
| Which stage runs next | Blueprint start.to and stage to transitions |
| When a person must answer | The stage’s gates |
| Behavior shared across a worker’s stages | The worker’s prompt in agents/<name>/agent.md |
| A reusable procedure, such as repository checks | A skill |
| Model, harness, runner, tools, or access | The worker settings below |
The Blueprint’s stage procedures and routing take precedence over workflow instructions in worker prompts. Editing a worker prompt is not a way to replace the Blueprint’s review loop.
Edit worker settings and instructions
Section titled “Edit worker settings and instructions”If your factory definition is hosted by Warp, edit worker settings in the factory web app. If the definition is hosted by GitHub, settings are read-only in the app; edit the definition files in your repository instead.
-
In the web app sidebar, click your factory to expand it, then click Workers.
-
Click a worker to open its Settings tab.
-
Edit the worker description, harness, model, runner, host, MCP servers, or secrets.
-
To change instructions shared across stages, click Prompt and edit the worker’s prompt. For a particular stage’s procedure, edit the Blueprint in the definition instead.
-
In the top-right corner, click Save.
Choose models and harnesses per worker
Section titled “Choose models and harnesses per worker”Choose each worker’s model and harness in its settings. Supported harnesses include the Warp Agent, Claude Code, Codex, and Pi. A foreman using Claude Code or Codex can still dispatch other factory workers, whose runs are tracked as its children.
Third-party harnesses are included on the Scale and Enterprise plans for Warp Factories. Existing paid-plan access depends on your team’s plan and workspace settings. See plan requirements.
Default model IDs change over time, so choose based on what each worker has to do well:
| Work | What to optimize for |
|---|---|
| Foreman | Orchestration, instruction following, and long-running conversations |
| Triage | Research, evidence gathering, and working with connected tools |
| Spec | Synthesizing requirements, technical reasoning, and precise writing |
| Implement | Coding strength, with a harness that fits your repositories and toolchain |
| Review | A separate worker with a different model or harness when independent review needs different strengths |
The model picker also includes custom routers from factories you can access. See Agent model choice, Custom routers, and Agent harnesses for available options.
For team-managed inference in definition files, see custom endpoint and BYOK model values, including factory defaults and per-worker overrides.
Reviewing inference for provider ZDR
Section titled “Reviewing inference for provider ZDR”Use factory ZDR guidance to check coverage for your model and provider account before changing settings. For Warp-managed inference, choose models outside the provider-retention exception list.
Review factory defaults, worker and automation overrides, and separate feature models such as Computer Use and Scorers. The factory definition reference lists these settings. Team-wide model restrictions and shared credentials belong in the Admin Panel’s Models settings.
Choose the path matching where your factory definition is hosted.
Factory definition hosted by Warp
Section titled “Factory definition hosted by Warp”With editing access:
- In the Warp Factories web app, expand your factory and click Factory definition. Review model defaults and overrides in the existing definition files.
- In Workers, open each worker’s Settings, including the foreman’s, and review the “Harness” and “Model” selections.
- Save any changes, resolve validation errors, and reopen the settings to confirm the intended values before checking a new run.
Factory definition hosted by GitHub
Section titled “Factory definition hosted by GitHub”You need permission to propose and merge definition changes. The factory web app shows these files read-only.
- In the Warp Factories web app, expand your factory, open Settings, and follow the definition repository link.
- In GitHub, propose model changes in the existing definition files. Check factory defaults, workers including the foreman, and any automation or feature overrides.
- Confirm the factory-definition PR checks pass, then merge into the connected production branch. Reopen the changed settings in the factory web app to confirm the values before checking a new run.
Checking new runs
Section titled “Checking new runs”Use a test factory with non-sensitive repositories and inputs:
- In the factory web app, click New Chat and choose the test factory below the prompt input.
- Send: “Reply with a greeting. Don’t read repository files or call tools.”
- In Runs, open the new run and compare its model and harness with your selections. Check child runs and any features you changed separately.
If settings don’t match, review overrides or contact support before sending sensitive work. A greeting checks the selected model, not coverage for every AI request.
Configuring a third-party harness
Section titled “Configuring a third-party harness”Change a worker’s harness to Claude Code or Codex to run it with that provider’s own coding tool. For Pi setup, see Configuring the Pi harness.
-
In the web app sidebar, click your factory to expand it, then click Workers.
-
Click a worker to open its Settings tab.
-
In the “Harness” dropdown, choose Claude Code or Codex. The “Auth” field appears for these harnesses.
-
In the “Auth” field, choose a compatible, team-owned secret. To create one, click New auth secret for Claude Code or New OpenAI API Key for Codex.
-
In the “Model” dropdown, choose a model from that harness’s catalog.
-
In the top-right corner, click Save.
If your factory definition is hosted by Warp, edit the harness, auth, and model in the factory web app. If the definition is hosted by GitHub, edit agentDefaults.harness or a per-worker harness override in your repository. For an example, see 03-multi-harness.
Related pages
Section titled “Related pages”- About factory workers - Understand worker and stage responsibilities
- Creating custom workers
- Factory skills
- Definitions as code