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

# Choosing agent harnesses

Choose the Warp Agent, Claude Code, or Codex for factory agents and standalone cloud runs, with authentication scoped to each workflow.

A harness is the agent runtime that works on a task. Choose the [Warp Agent](https://docs.warp.dev/factories/harnesses/warp-agent/), [Claude Code](https://docs.warp.dev/factories/harnesses/claude-code/), or [Codex](https://docs.warp.dev/factories/harnesses/codex/) for each factory agent. For example, use Claude Code for an implement agent and the Warp Agent for a review agent.

Set the harness, model, and team-owned authentication in [Configuring factory agents](https://docs.warp.dev/factories/factory-agents/configuration/#configuring-a-third-party-harness). For file-based configuration, set a default or per-agent override in the [factory definition](https://docs.warp.dev/factories/factory-as-code/#agentdefaultsharness).

You can also select a harness for a standalone cloud run without creating a factory. The walkthrough shows these standalone cloud-agent surfaces.

![Run any agent in the cloud with the Automation Platform - Claude Code, Codex, or Warp Agent](https://i.ytimg.com/vi/ZUYyuA5i1VU/sddefault.jpg)

## Shared cloud-run capabilities

-   **Triggers** - Select a harness for agents launched by [factory automations](https://docs.warp.dev/factories/automations/) or standalone [triggers](https://docs.warp.dev/platform/triggers/).
-   **Environments and secrets** - Configure the run’s [environment](https://docs.warp.dev/factories/environments/) and credentials. Factory agents use [factory secrets](https://docs.warp.dev/factories/secrets/); standalone runs have their own [secret configuration](https://docs.warp.dev/platform/secrets/).
-   **Instructions** - Use [skills](https://docs.warp.dev/agents/capabilities/skills/) for reusable work and [Rules](https://docs.warp.dev/agents/capabilities/rules/) for project guidance. Harnesses have their own tool and context behavior; selecting a harness does not make every local feature available in a cloud run.
-   **Observability** - Inspect factory runs in the factory dashboard, or standalone runs in the [cloud agent dashboard](https://docs.warp.dev/platform/managing-cloud-agents/).

## Plan requirements

Third-party harness access depends on your plan and workspace settings. If a harness requires an upgrade, use the Warp Agent or review [Warp pricing](https://www.warp.dev/pricing). A team admin can also disable a harness for the workspace.

## Billing

With the [provider credentials described here](https://docs.warp.dev/factories/harnesses/authentication/), your inference provider bills your account. Warp charges for [Warp-hosted compute](https://docs.warp.dev/support-and-community/plans-and-billing/credits/#compute-usage) and [platform usage](https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/) according to your plan or contract. External inference bills are not fully represented in Warp’s [cost summaries](https://docs.warp.dev/support-and-community/plans-and-billing/credits/#charges-and-estimates).

## How to switch harnesses

For a factory agent, follow [Configuring factory agents](https://docs.warp.dev/factories/factory-agents/configuration/). The following alternatives select a harness for a standalone run.

### Warp app

In the Warp app’s Cloud Mode, choose a harness from the “Agent harness” dropdown above the input.

![The Warp app Agent harness dropdown showing third-party harness options for a cloud agent.](https://docs.warp.dev/_astro/cloud-agent-harness-selector-warp-app.CxxG8vW2_ZX64aO.webp?dpl=dpl_D7TtuKxUfuCUHM83kHACU6L62WQB)

The Agent harness selector.

Note

You can enter Cloud Mode by creating a new **Cloud Agent** tab or by using the `/cloud-agent` slash command.

### Web app

In the Oz web app, open the new run or new schedule pane. In the “Harness” dropdown, choose the harness.

### API and SDK

Set the agent config’s `harness.type` to one of the [harness identifiers](#harness-identifiers). The API takes a harness object, not a bare harness string. See the [API reference](https://docs.warp.dev/factories/api-and-sdk/) for the schema and authentication fields.

## Harness identifiers

Use `oz` for the Warp Agent, `claude` for Claude Code, and `codex` for Codex in stored configuration:

-   **API and SDK** - The agent config’s `harness.type` accepts `oz`, `claude`, or `codex`.
-   **CLI** - In the Oz CLI, `oz agent run-cloud --harness` accepts these identifiers, plus `claude-code` as an alias for `claude`.
-   **Factory definition files** - Use `oz`, `claude`, or `codex` in [`harness.type`](https://docs.warp.dev/factories/factory-as-code/#agentdefaultsharness). `claude-code` is also accepted as a Claude Code alias.

Agent orchestration tools can use `claude-code` as their Claude Code label. Follow the schema for the surface you’re using rather than copying a tool-call label into an API request.

## Related pages

-   [Configuring factory agents](https://docs.warp.dev/factories/factory-agents/configuration/) - Select a harness and its team-owned auth secret
-   [Warp Agent](https://docs.warp.dev/factories/harnesses/warp-agent/)
-   [Claude Code](https://docs.warp.dev/factories/harnesses/claude-code/)
-   [Codex](https://docs.warp.dev/factories/harnesses/codex/)
-   [Configuring harness authentication](https://docs.warp.dev/factories/harnesses/authentication/)
-   [Multi-agent orchestration](https://docs.warp.dev/platform/orchestration/) - Coordinate ad hoc parent and child agents
-   [Third-party CLI agents overview](https://docs.warp.dev/agents/cli-agents/overview/) - Run CLI agents locally in Warp