Harnesses in Oz

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

What stays the same

Third-party harnesses inherit the same Oz 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 Oz dashboard.

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

How to switch harnesses

Warp desktop app

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

Note

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

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

Related pages

• Warp Agent with Oz — Oz’s default first-party harness.
• Claude Code with Oz — Claude Code as a cloud harness.
• Codex with Oz — Codex as a cloud harness.
• Authentication — connect credentials and launch Claude Code or Codex.
• Third-party CLI agents in the Warp terminal — run Claude Code, Codex, and other CLI agents locally.