Automation Platform > Cloud Agents

Cloud agents overview

Run background agents in the cloud from events, schedules, or integrations with team-wide observability.

Cloud agents execute a request away from your laptop, on Warp-hosted compute or your own infrastructure. For example, an agent can investigate a failed build, review a pull request, or respond to an issue filed in your tracker.

For a standing team workflow with agents, automations, and measurement, start with Warp Factories in the Warp Factories web app. For one cloud-agent task in Warp, use the cloud agents quickstart.

Already using the legacy web app or CLI? See transitioning from Oz to Warp Factories. The standalone workflows below remain distinct from factory setup.

For factory work, open the factory’s Runs page. For standalone workflows, use the Agent Management Panel in Warp or the legacy Runs page.

Open a run’s transcript to inspect its prompt, commands, logs, and outputs, or share its session link with teammates. See viewing cloud agent runs for steering and continuing a session.

What cloud agents are designed for

Event-driven work - Respond to bug reports, Slack messages, or CI failures.
Parallel tasks - Use multi-agent orchestration to divide independent work among agents running in the cloud.
Recurring maintenance - Run scheduled agents for dependency checks, cleanup, or reports.

Cloud agent use cases across the development lifecycle: Plan, Prototype, Build, Validate, Review + Merge, Deploy + Monitor

Preparing a cloud-agent task

Before automating a task, identify its trigger, the context the agent needs, and how someone will validate its result.

How cloud agents work

The Automation Platform overview explains the execution model shared by factories and standalone agents, including environments and credentials.

The exact way tasks are triggered and executed depends on your deployment model. Deployment patterns covers Warp-hosted and managed self-hosted execution for factories. For standalone agents, see unmanaged execution.

For teams that need execution to stay within their network boundary, self-hosting supports two architectures: a managed worker daemon that lets the Automation Platform orchestrate agents in Docker containers on your machines, and an unmanaged mode where you run oz agent run directly in your CI, Kubernetes, or dev environment. See Self-hosting for details.

What you get by default

The following features apply to standalone cloud-agent workflows. For factory configuration, see definitions as code.

Codebase Context

Cloud agent runs automatically benefit from Codebase Context for semantic code understanding and search, as long as Codebase Context is enabled for your account. See Codebase Context in cloud agent runs for details.

Centralized configuration

Configure MCP servers and secrets for the tools your task needs. The shared configuration reference links to each configuration type and its scope.

API access to tasks

The Warp Platform API lets you query run status, metadata, and results from your own services.

Using cloud agents with or without the Warp app

Cloud agents do not require the Warp app. Teams can deploy and operate them through the Automation Platform using:

Oz CLI — run agents from scripts, CI, or the terminal
Oz web app — visual interface for managing runs, schedules, environments, and integrations (works on mobile)
Agent Session Sharing — attach to running tasks to monitor or steer
Agent Management Panel — view agent activity and run history in the Warp app
APIs and SDKs — programmatic access for custom integrations

Use Handoff to continue work between local and cloud sessions.

Billing and plan requirements

Cloud agents and integrations run on the Automation Platform control plane, and usage is billed using credits.

For cloud agents via CLI/API

Individual users can run cloud agents without being on a team. Requirements:

You need at least 20 credits available
Cloud agents run on Warp-hosted infrastructure
Self-hosted agents require a team subscription

For integrations (Slack/Linear)

Integrations require you to be part of a Warp team and additional requirements:

Plan requirements
- Supported plans: Build, Max, Business
- Your plan must support add-on credits.
Credit requirements
- Your team must have at least 20 credits available to run cloud agents and integrations.

For more details, see Access, Billing, and Identity Permissions.

Cloud agents quickstart — run your first cloud agent with an environment in ~10 minutes.
Automation Platform — CLI, Warp Platform API, orchestration, tasks, environments, hosts, integrations, and more.
Warp Factories — configure a standing development workflow with agents, automations, and measurement.
Harnesses — pick between Warp Agent, Claude Code, and Codex for any cloud agent run.
Agents — cloud agents that own and execute runs on your team.
Multi-agent orchestration — coordinate a parent agent and its child agents across local and cloud runs to build supervisor/worker, fan-out, critic, DAG, and swarm workflows.
Skills as Agents — run agents based on reusable skill definitions from the CLI, web app, API, or on a schedule.
Oz CLI — shows how to run agents in non-interactive mode from CI, scripts, or remote machines, including auth and common commands.
Environments — explains how environments provide the runtime context (repo, image, startup commands) for agent tasks.
Warp Platform API — documents the REST API for creating, querying, and monitoring agent tasks programmatically.
Agent Secrets — covers how to store, scope, and inject credentials into agent runs safely.
MCP Servers — how to configure MCP servers for agent tool access and how MCP configuration is applied across runs.
Deployment Patterns (beta) — compares common ways to deploy cloud agents and when to use each.
Access, Billing, and Identity Permissions — explains individual and team-level requirements, credit billing behavior, and the permission model for who can run, view, and steer cloud agent tasks.