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

# Automation Platform overview

Find factory setup and shared runtime references, with separate entry points for existing standalone cloud-agent workflows.

[Warp Factories](https://docs.warp.dev/factories/) and [standalone cloud agents](https://docs.warp.dev/platform/) run on the Automation Platform. It provides the execution, configuration, and APIs they share.

## Start with a factory

For a team workflow with planning, implementation, and review, start with the [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/). Then configure its [agents](https://docs.warp.dev/factories/factory-agents/configuration/), [automations](https://docs.warp.dev/factories/automations/), and [tools](https://docs.warp.dev/factories/mcp/).

Already using the Oz web app, Oz CLI, or SDKs? Use [transitioning from Oz](https://docs.warp.dev/platform/transitioning-from-oz/) to assess that workflow. The [cloud agents overview](https://docs.warp.dev/platform/) retains standalone setup and management entry points.

## How a run works

A request or event supplies the task and its context. The agent executes on its configured host and produces results such as a pull request, report, or transcript. For the factory task lifecycle and review points, see [how Warp Factories work](https://docs.warp.dev/factories/how-factories-work/).

![A trigger starts an agent, which runs in a configured environment and produces artifacts such as plans, pull requests, and conversation records.](https://docs.warp.dev/_astro/cloud-agent-run-flow.C5BGK_AS_Z2nmHs6.webp?dpl=dpl_D7TtuKxUfuCUHM83kHACU6L62WQB)

A trigger starts a run that produces reviewable artifacts.

## Integrations and triggers

[Factory automations](https://docs.warp.dev/factories/automations/) route events from [connected tools](https://docs.warp.dev/factories/connect-your-factory/) to factory agents. They also start runs on a schedule. For custom intake, use [webhooks](https://docs.warp.dev/factories/webhooks/) and [factory endpoints](https://docs.warp.dev/factories/factory-api/).

Standalone workflows have separate [integrations](https://docs.warp.dev/platform/integrations/) and [scheduled runs](https://docs.warp.dev/platform/triggers/scheduled-agents/). The [CLI integration setup guide](https://docs.warp.dev/agents/cli/oz-cli/integration-setup/) covers their configuration.

## Inspecting results

Inspect factory work from the [factory dashboard](https://docs.warp.dev/factories/factory-dashboard/). For standalone management, sharing, and steering, use the [cloud-agent inspection paths](https://docs.warp.dev/platform/#monitor-inspect-and-share-cloud-agent-runs).

## Environments

Factories manage their workspace by default. [Cloud agent environments](https://docs.warp.dev/factories/environments/) cover the optional existing-environment path and standalone setup; [runners](https://docs.warp.dev/factories/runners/) cover compute configuration.

## Hosts

For factory hosting choices and requirements, compare [Warp-hosted execution](https://docs.warp.dev/factories/warp-hosting/) with [managed self-hosting](https://docs.warp.dev/factories/self-hosting/). [Unmanaged execution](https://docs.warp.dev/platform/unmanaged-execution/) covers standalone CLI workflows on infrastructure you operate.

## The CLI

Use the [Oz CLI](https://docs.warp.dev/agents/cli/oz-cli/) for existing `oz` workflows and the [Warp Agent CLI](https://docs.warp.dev/agents/cli/) for `warp` commands. Check the owning reference before changing a script.

## API and SDKs

Use [factory endpoints](https://docs.warp.dev/factories/factory-api/) to send work to a factory, and [agent and run endpoints](https://docs.warp.dev/factories/api-and-sdk/) for standalone runs and run inspection. [Developer tools](https://docs.warp.dev/factories/developer-tools/) links to the SDKs and full API reference.

## Secrets

Use [factory secrets](https://docs.warp.dev/factories/secrets/) for credentials granted to factory agents and [harness authentication](https://docs.warp.dev/factories/harnesses/authentication/) for third-party provider credentials. The [legacy secrets reference](https://docs.warp.dev/platform/secrets/) preserves standalone CLI and personal-secret workflows.

## Shared configuration

Factory-wide and per-agent settings live in the [factory definition](https://docs.warp.dev/factories/factory-as-code/). The shared [harness](https://docs.warp.dev/factories/harnesses/), [environment](https://docs.warp.dev/factories/environments/), and [MCP-server](https://docs.warp.dev/factories/mcp/) references explain factory and standalone configuration separately.

For instructions and reusable context, see [factory skills](https://docs.warp.dev/factories/factory-skills/), [Rules](https://docs.warp.dev/agents/capabilities/rules/), [saved prompts](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/prompts/), and [environment variables](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/environment-variables/). These have different scopes; follow the relevant reference.

## Measuring factory work

Use [Scorers](https://docs.warp.dev/factories/measure-and-improve/scorers/), [Benchmarks](https://docs.warp.dev/factories/benchmarks/), and [Self-improvement](https://docs.warp.dev/factories/measure-and-improve/self-improvement/) to evaluate factory work and propose changes to its configuration. See [measure and improve](https://docs.warp.dev/factories/measure-and-improve/) for metric definitions and limitations.

## Related pages

-   [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/) - Create a factory and send its first work item
-   [Cloud agents overview](https://docs.warp.dev/platform/) - Find supported standalone entry points
-   [Architecture](https://docs.warp.dev/platform/architecture/) - Review the run lifecycle and data boundaries
-   [Multi-agent orchestration](https://docs.warp.dev/platform/orchestration/) - Coordinate parent and child agents