# Harnesses in the Automation Platform

> Run third-party harnesses such as Claude Code or Codex as cloud agents. They inherit the same triggers, environments, secrets, and observability as Warp Agent.

- 网址：https://funcoding.ai/agents/warp/platform/harnesses/
- 来源：Warp 官方文档原文（英文），MIT 许可，同步于 2026-10-11
- 官方原文：https://docs.warp.dev/platform/harnesses/

---
The Automation Platform can run third-party agent harnesses as cloud agents alongside Warp Agent, including [Claude Code](https://funcoding.ai/agents/warp/platform/harnesses/claude-code/) and [Codex](https://funcoding.ai/agents/warp/platform/harnesses/codex/). You choose the harness (agent runtime) that fits the task; the platform around the run stays the same.

For a factory, set the default or per-agent harness in its [factory definition](https://funcoding.ai/agents/warp/factories/factory-as-code/#agentdefaultsharness) or configure it for a [factory agent](https://funcoding.ai/agents/warp/factories/factory-agents/).

Watch this walkthrough to see how to run Warp Agent, Claude Code, or Codex as a cloud agent.

## What stays the same

Third-party harnesses inherit the same Automation Platform features as Warp Agent:

* **Triggers** — Slack, Linear, schedules, CI, and API [triggers](https://funcoding.ai/agents/warp/platform/triggers/) launch any harness.
* **Environments and secrets** — Reuse the same [environments](https://funcoding.ai/agents/warp/platform/environments/) and [agent secrets](https://funcoding.ai/agents/warp/platform/secrets/).
* **Skills and Rules** — Saved [Skills](https://funcoding.ai/agents/warp/agents/capabilities/skills/) and [Rules](https://funcoding.ai/agents/warp/agents/capabilities/rules/) apply across harnesses.
* **Observability** — Every run produces a transcript and shareable session in the [cloud agent dashboard](https://funcoding.ai/agents/warp/platform/managing-cloud-agents/).

## Plan requirements

Third-party harnesses require a paid plan. On the Free plan, cloud agent runs use Warp Agent, and choosing another harness returns an upgrade prompt. See [Warp pricing](https://www.warp.dev/pricing) for what each plan includes.

## Billing

Claude Code and Codex each call their provider directly using credentials you supply, and the provider bills your account for inference. Warp meters [compute credits](https://funcoding.ai/agents/warp/support-and-community/plans-and-billing/credits/#compute-credits) for the run's sandbox and [platform credits](https://funcoding.ai/agents/warp/support-and-community/plans-and-billing/platform-credits/) for the [multi-agent orchestration](https://funcoding.ai/agents/warp/platform/orchestration/) layer.

## How to switch harnesses

### Warp app

In Cloud Mode, choose a harness from the **Agent harness** dropdown above the input.

<figure>
![The Warp app Agent harness dropdown showing third-party harness options for a cloud agent.](https://funcoding.ai/official-assets/warp/src/assets/agent-platform/cloud-agent-harness-selector-warp-app.webp)
<figcaption>The Agent harness selector.</figcaption>
</figure>

<div class="callout callout-note">

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

</div>

### Web app

On the new run or new schedule pane, choose the harness in the **Harness** field.

### API and SDK

Set the `harness` field on the agent config to one of the [harness identifiers](#harness-identifiers) below. See the [API reference](https://funcoding.ai/agents/warp/factories/api-and-sdk/) for the exact field names.

## Harness identifiers

Surfaces that take the harness as a string use `oz` for the Warp Agent, `claude` for Claude Code, and `codex` for Codex. Write `claude` for Claude Code — not `claude-code` — unless the surface explicitly accepts that alias:

* **API and SDK** — the agent config's `harness.type` accepts `oz`, `claude`, or `codex`.
* **CLI** — `oz agent run-cloud --harness` accepts the same identifiers, plus `claude-code` as an alias for `claude`.
* **Factory definition files** — [`harness.type`](https://funcoding.ai/agents/warp/factories/factory-as-code/#agentdefaultsharness) accepts `oz`, `claude`, or `codex`, plus `claude-code` as an alias for `claude`.

Where the alias is accepted, it selects the same Claude Code harness as `claude`. Everywhere else — including the API — only the canonical identifiers are valid, so prefer them in anything you script, sync, or store.

## Related pages

* [Warp Agent with the Automation Platform](https://funcoding.ai/agents/warp/platform/harnesses/warp-agent/) — the Automation Platform's default first-party harness.
* [Claude Code with the Automation Platform](https://funcoding.ai/agents/warp/platform/harnesses/claude-code/) — Claude Code as a cloud harness.
* [Codex with the Automation Platform](https://funcoding.ai/agents/warp/platform/harnesses/codex/) — Codex as a cloud harness.
* [Authentication](https://funcoding.ai/agents/warp/platform/harnesses/authentication/) — connect credentials and launch Claude Code or Codex.
* [Multi-agent orchestration](https://funcoding.ai/agents/warp/platform/orchestration/) — run parent and child agents across harnesses and locations.
* [Third-party CLI agents in the Warp terminal](https://funcoding.ai/agents/warp/agents/cli-agents/overview/) — run Claude Code, Codex, and other CLI agents locally.
