Cloud agents overview

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.

Start with Warp Factories

For a standing team workflow, start with the Warp Factories quickstart. A factory brings together agents, automations, and evaluation.

See how Warp Factories work for the task lifecycle and human review points.

Continue a standalone workflow

To start a cloud agent directly from Warp, use the cloud agents quickstart. Existing standalone runs, schedules, and integrations have their own configuration and management paths.

Already using the Oz web app, Oz CLI, or SDKs? See transitioning from Oz to Warp Factories before changing an existing workflow.

Monitor, inspect, and share cloud agent runs

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

See viewing cloud agent runs to inspect a transcript, share a session, or continue a standalone run.

What cloud agents are designed for

Use factory automations for event-driven work and recurring maintenance in a factory. Standalone workflows have separate integrations and schedules. Multi-agent orchestration explains how parent and child agents divide work.

How cloud agents work

The Automation Platform overview explains the shared execution model. For factory hosting choices, see deployment patterns. For standalone CLI execution in your own CI or development environment, see unmanaged execution.

Configure the runtime and tools

Shared cloud-agent references now live in the Factories tab:

• Cloud agent harnesses - Choose a runtime and configure its authentication
• Cloud agent environments - Reuse an environment when the run needs one
• MCP servers for agents - Connect agents to external tools

Codebase Context

For indexing requirements and availability, see Codebase Context in cloud agent runs.

Centralized configuration

For factory-wide and per-agent settings, use definitions as code and factory secrets. The legacy secrets reference retains standalone CLI and personal-secret workflows.

API access to runs

Use factory endpoints to send work to a factory. Use agent and run endpoints to inspect run status, transcripts, and results.

Using cloud agents with or without the Warp app

For standalone runs outside the Warp app, use the Oz CLI, Oz web app, or API and SDKs. Session sharing and the Agent Management Panel provide inspection paths in Warp.

Use Handoff to continue work between local and cloud sessions.

Billing and plan requirements

Check access, billing, and identity requirements before starting runs or integrations. Platform usage owns the charge details, and factory infrastructure and security explains inference and credential options.

Related pages

• Warp Factories quickstart - Create a factory and send its first work item
• Transitioning from Oz to Warp Factories - Assess an existing workflow before adopting a factory
• Cloud agents quickstart - Start a standalone cloud run
• Cloud agent accounts - Configure who owns and executes standalone runs
• Skills as agents - Run a standalone workflow from a reusable skill