Skip to content
Warp

Factories > Harnesses

Running Claude Code in the cloud

Run Claude Code as a factory agent or standalone cloud harness with Anthropic or Amazon Bedrock credentials.

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

Claude Code is Anthropic’s coding agent. Use it as a factory agent’s harness to work on tasks such as code review, bug investigation, or feature implementation. Select its harness, model, and team-owned auth secret in Configuring factory agents.

Claude Code also runs as a standalone cloud agent without a factory. To run the CLI locally in Warp, follow Claude Code in Warp; local authentication is separate from the cloud setup below.

Key features

Section titled “Key features”
  • Cloud orchestration - Launch Claude Code from any Automation Platform trigger: the Warp app, the Oz web app, the Oz CLI, the REST API, schedules, Slack mentions, Linear issues, or GitHub Actions.
  • Claude model picker - Choose from the Claude Code models available in the model picker.
  • Parent and child roles - A Warp Agent parent can dispatch Claude Code children in ad hoc orchestration. A factory foreman using Claude Code can dispatch named factory agents; those agents keep their configured harnesses and resources.

Available models

Section titled “Available models”

Choose a model from the factory agent’s “Model” dropdown. For standalone runs, use the model picker in the Warp app’s Cloud Mode or the “Model” field on the Oz web app‘s new-run pane. Available model IDs and aliases can change; use the picker for the current catalog instead of assuming a pinned release is available to every account. See Agent model choice for model-selection guidance.

Credentials and billing

Section titled “Credentials and billing”

For cloud authentication with a managed secret, Claude Code accepts these credential types:

  • Anthropic API key - For direct Anthropic API access.
  • Anthropic Bedrock API key - For Bedrock-routed inference using an API key.
  • Anthropic Bedrock access key - For Bedrock-routed inference using AWS access credentials.

Direct API credentials use Anthropic; Bedrock credentials route inference through Amazon Bedrock. Your inference provider bills the corresponding account. Warp charges for hosted compute and platform usage according to your plan or contract. See harness billing for cost-reporting limitations.

Factory agents select team-scoped secrets. Standalone ad hoc runs can use personal or team-scoped secrets. For setup steps and credential scope, see Connecting Claude Code credentials.

Starting a Claude Code run

Section titled “Starting a Claude Code run”

For a factory agent, follow Configuring factory agents. For a standalone cloud run:

  • Warp app - In the Warp app’s Cloud Mode, open the “Agent harness” dropdown above the input and choose Claude Code.
  • Oz web app - On the new run or new schedule pane, in the “Harness” dropdown, choose Claude Code. In the “Claude Code auth secret” field, select a stored Anthropic secret.
  • Oz CLI - Use oz agent run-cloud --harness claude --claude-auth-secret KEY_NAME with your prompt and environment options. Replace KEY_NAME with the stored secret’s name.
  • API and SDK - Set the agent config’s harness.type to claude and select the Anthropic secret in the matching auth-secret field. See harness identifiers and the API reference for the object schema.
Section titled “Related pages”