Automation Platform > Harnesses

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.

The Automation Platform can run third-party agent harnesses as cloud agents alongside Warp Agent, including Claude Code and Codex. You choose the harness (agent runtime) that fits the task; the platform around the run stays the same.

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 launch any harness.
Environments and secrets — Reuse the same environments and agent secrets.
Skills and Rules — Saved Skills and Rules apply across harnesses.
Observability — Every run produces a transcript and shareable session in the cloud agent dashboard.

Plan requirements

Third-party harnesses require a Build plan or higher. On the Free plan, cloud agent runs use Warp Agent, and choosing another harness returns an upgrade prompt. See Warp 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 for the run’s sandbox and platform credits for the multi-agent orchestration layer.

How to switch harnesses

Warp app

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

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 below. See the API reference for the exact field names.

Harness identifiers

Surfaces that take the harness as a string all use the same identifiers: oz for the Warp Agent, claude for Claude Code, and codex for Codex. Write claude for Claude Code — not claude-code:

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 accepts the same identifiers, plus the claude-code alias.

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.

Warp Agent with the Automation Platform — the Automation Platform‘s default first-party harness.
Claude Code with the Automation Platform — Claude Code as a cloud harness.
Codex with the Automation Platform — Codex as a cloud harness.
Authentication — connect credentials and launch Claude Code or Codex.
Multi-agent orchestration — run parent and child agents across harnesses and locations.
Third-party CLI agents in the Warp terminal — run Claude Code, Codex, and other CLI agents locally.