> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Cloud agents overview

Start a team workflow with Warp Factories, or find the CLI, setup, and management references for existing standalone cloud agents.

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](https://docs.warp.dev/factories/quickstart/). A factory brings together [agents](https://docs.warp.dev/factories/factory-agents/), [automations](https://docs.warp.dev/factories/automations/), and [evaluation](https://docs.warp.dev/factories/measure-and-improve/).

See [how Warp Factories work](https://docs.warp.dev/factories/how-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](https://docs.warp.dev/platform/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](https://docs.warp.dev/platform/transitioning-from-oz/) before changing an existing workflow.

## Monitor, inspect, and share cloud agent runs

For factory work, open the factory’s [Runs page](https://docs.warp.dev/factories/factory-dashboard/#inspect-runs). For standalone workflows, use the [Agent Management Panel](https://docs.warp.dev/platform/managing-cloud-agents/) in Warp or the [Oz web app Runs page](https://docs.warp.dev/platform/oz-web-app/#runs).

See [viewing cloud agent runs](https://docs.warp.dev/platform/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](https://docs.warp.dev/factories/automations/) for event-driven work and recurring maintenance in a factory. Standalone workflows have separate [integrations](https://docs.warp.dev/platform/integrations/) and [schedules](https://docs.warp.dev/platform/triggers/scheduled-agents/). [Multi-agent orchestration](https://docs.warp.dev/platform/orchestration/) explains how parent and child agents divide work.

## How cloud agents work

The [Automation Platform overview](https://docs.warp.dev/platform/overview/) explains the shared execution model. For factory hosting choices, see [deployment patterns](https://docs.warp.dev/factories/deployment-patterns/). For standalone CLI execution in your own CI or development environment, see [unmanaged execution](https://docs.warp.dev/platform/unmanaged-execution/).

## Configure the runtime and tools

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

-   [Cloud agent harnesses](https://docs.warp.dev/factories/harnesses/) - Choose a runtime and configure its authentication
-   [Environments for factory agents](https://docs.warp.dev/factories/environments/) - Reuse an environment when the run needs one
-   [MCP servers for agents](https://docs.warp.dev/factories/mcp/) - Connect agents to external tools

### Codebase Context

For indexing requirements and availability, see [Codebase Context in cloud agent runs](https://docs.warp.dev/agents/capabilities/codebase-context/#codebase-context-in-cloud-agent-runs).

### Centralized configuration

For factory-wide and per-agent settings, use [definitions as code](https://docs.warp.dev/factories/factory-as-code/) and [factory secrets](https://docs.warp.dev/factories/secrets/). The [legacy secrets reference](https://docs.warp.dev/platform/secrets/) retains standalone CLI and personal-secret workflows.

### API access to runs

Use [factory endpoints](https://docs.warp.dev/factories/factory-api/) to send work to a factory. Use [agent and run endpoints](https://docs.warp.dev/factories/api-and-sdk/) 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](https://docs.warp.dev/agents/cli/oz-cli/), [Oz web app](https://docs.warp.dev/platform/oz-web-app/), or [API and SDKs](https://docs.warp.dev/factories/api-and-sdk/). [Session sharing](https://docs.warp.dev/agents/local-agents/session-sharing/) and the [Agent Management Panel](https://docs.warp.dev/platform/managing-cloud-agents/) provide inspection paths in Warp.

Use [Handoff](https://docs.warp.dev/platform/handoff/) to continue work between local and cloud sessions.

## Billing and plan requirements

Check [access, billing, and identity requirements](https://docs.warp.dev/platform/team-access-billing-and-identity/) before starting runs or integrations. [Platform usage](https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/) owns the charge details, and [factory infrastructure and security](https://docs.warp.dev/factories/infrastructure-and-security/#choose-inference-independently) explains inference and credential options.

## Related pages

-   [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/) - Create a factory and send its first work item
-   [Transitioning from Oz to Warp Factories](https://docs.warp.dev/platform/transitioning-from-oz/) - Assess an existing workflow before adopting a factory
-   [Cloud agents quickstart](https://docs.warp.dev/platform/quickstart/) - Start a standalone cloud run
-   [Cloud agent accounts](https://docs.warp.dev/platform/agents/) - Configure who owns and executes standalone runs
-   [Skills for agents](https://docs.warp.dev/agents/capabilities/skills/#running-agents-from-skills) - Run a standalone workflow from a reusable skill