> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# 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](https://platform.warp.dev) or its definition files.

## Prerequisites

-   [Editor access to this factory, or team or workspace admin access](https://docs.warp.dev/factories/infrastructure-and-security/#factory-roles-and-permissions).
-   An existing factory worker. See [About factory workers](https://docs.warp.dev/factories/factory-agents/) for the default roles, or [Creating custom workers](https://docs.warp.dev/factories/factory-agents/creating-custom-agents/) to add a role.

## Choose what to change

Keep workflow changes in the [Blueprint](https://docs.warp.dev/factories/blueprints/) 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](https://docs.warp.dev/factories/factory-skills/) |
| 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

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](https://docs.warp.dev/factories/factory-as-code/#where-the-definition-lives) instead.

1.  In the web app sidebar, click your factory to expand it, then click **Workers**.
    
2.  Click a worker to open its **Settings** tab.
    
3.  Edit the worker description, harness, model, runner, host, [MCP servers](https://docs.warp.dev/factories/mcp/), or [secrets](https://docs.warp.dev/factories/secrets/).
    
4.  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.
    
5.  In the top-right corner, click **Save**.
    

## 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](https://docs.warp.dev/factories/harnesses/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](https://docs.warp.dev/factories/harnesses/#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](https://docs.warp.dev/agents/inference/model-choice/), [Custom routers](https://docs.warp.dev/agents/inference/custom-routers/), and [Agent harnesses](https://docs.warp.dev/factories/harnesses/) for available options.

For team-managed inference in definition files, see [custom endpoint and BYOK model values](https://docs.warp.dev/factories/factory-as-code/#custom-inference-endpoints-and-byok), including factory defaults and per-worker overrides.

## Reviewing inference for provider ZDR

Use [factory ZDR guidance](https://docs.warp.dev/factories/zero-data-retention/) to check coverage for your model and provider account before changing settings. For Warp-managed inference, choose models outside the [provider-retention exception list](https://docs.warp.dev/agents/inference/model-choice/#models-requiring-provider-retention).

Review factory defaults, worker and automation overrides, and separate feature models such as Computer Use and Scorers. The [factory definition reference](https://docs.warp.dev/factories/factory-as-code/) lists these settings. Team-wide model restrictions and shared credentials belong in the [Admin Panel’s Models settings](https://docs.warp.dev/enterprise/team-management/admin-panel/#models-settings).

Choose the path matching [where your factory definition is hosted](https://docs.warp.dev/factories/factory-as-code/#where-the-definition-lives).

### Factory definition hosted by Warp

With [editing access](#prerequisites):

1.  In the [Warp Factories web app](https://platform.warp.dev), expand your factory and click **Factory definition**. Review model defaults and overrides in the existing definition files.
2.  In **Workers**, open each worker’s **Settings**, including the foreman’s, and review the “Harness” and “Model” selections.
3.  Save any changes, resolve validation errors, and reopen the settings to confirm the intended values before [checking a new run](#checking-new-runs).

### Factory definition hosted by GitHub

You need permission to propose and merge definition changes. The factory web app shows these files read-only.

1.  In the [Warp Factories web app](https://platform.warp.dev), expand your factory, open **Settings**, and follow the definition repository link.
2.  In GitHub, propose model changes in the existing definition files. Check factory defaults, workers including the foreman, and any automation or feature overrides.
3.  Confirm the [factory-definition PR checks](https://docs.warp.dev/factories/factory-as-code/#pull-request-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).

### Checking new runs

Use a test factory with non-sensitive repositories and inputs:

1.  In the factory web app, click **New Chat** and choose the test factory below the prompt input.
2.  Send: “Reply with a greeting. Don’t read repository files or call tools.”
3.  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](https://docs.warp.dev/support-and-community/troubleshooting-and-support/sending-us-feedback/) before sending sensitive work. A greeting checks the selected model, not [coverage for every AI request](https://docs.warp.dev/factories/zero-data-retention/#provider-zdr-coverage).

## 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](https://docs.warp.dev/factories/harnesses/pi/).

1.  In the web app sidebar, click your factory to expand it, then click **Workers**.
    
2.  Click a worker to open its **Settings** tab.
    
3.  In the “Harness” dropdown, choose **Claude Code** or **Codex**. The “Auth” field appears for these harnesses.
    
4.  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.
    
    Note
    
    -   Claude Code accepts an Anthropic API key, Anthropic Bedrock API key, or Anthropic Bedrock access key.
    -   Codex accepts an OpenAI API key.
    
    See [connecting Claude Code credentials](https://docs.warp.dev/factories/harnesses/authentication/#connecting-claude-code-credentials) and [connecting Codex credentials](https://docs.warp.dev/factories/harnesses/authentication/#connecting-codex-credentials) for how to obtain each key.
    
5.  In the “Model” dropdown, choose a model from that harness’s catalog.
    
6.  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](https://docs.warp.dev/factories/factory-as-code/#agentdefaultsharness) in your repository. For an example, see [`03-multi-harness`](https://github.com/warpdotdev/warp-factory-examples/tree/main/examples/03-multi-harness).

## Related pages

-   [About factory workers](https://docs.warp.dev/factories/factory-agents/) - Understand worker and stage responsibilities
-   [Creating custom workers](https://docs.warp.dev/factories/factory-agents/creating-custom-agents/)
-   [Factory skills](https://docs.warp.dev/factories/factory-skills/)
-   [Definitions as code](https://docs.warp.dev/factories/factory-as-code/)
