> 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 The Automation Platform provides shared execution, configuration, and APIs for Warp Factories and standalone cloud agents. [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. For a team workflow with planning, implementation, and review, start with the [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/). To run cloud agents directly from Warp, use the [cloud agents quickstart](https://docs.warp.dev/platform/quickstart/). See [transitioning from Oz](https://docs.warp.dev/platform/transitioning-from-oz/) if you already use the Oz web app, Oz CLI, or SDKs. ## How a run works A run starts with a request or event and ends with a result you can inspect: 1. A **trigger** fires. This could be a schedule, an integration event like a Slack mention or a CI failure, an API call, or a manual start. 2. The agent receives the request and its context, such as a Slack thread, PR metadata, or CI logs. 3. The agent executes on a **host**. If an [environment](https://docs.warp.dev/platform/environments/) is configured, it defines the image, repositories, and setup commands. 4. The run produces **outputs**, like a pull request, Slack reply, report, or transcript and summary. ![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_774R4EjZERfRTeAPSbk2mPGPP3HR) 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 cloud-agent workflows also have [integrations](https://docs.warp.dev/platform/integrations/) and [scheduled runs](https://docs.warp.dev/platform/triggers/scheduled-agents/). For CLI setup, use `oz integration create` on the Oz CLI. See the [integration setup guide](https://docs.warp.dev/agents/cli/oz-cli/integration-setup/). ## Inspecting results Runs retain their status, transcript, and outputs for later review. For inspection, sharing, and steering, see [viewing cloud agent runs](https://docs.warp.dev/platform/viewing-cloud-agent-runs/). Factory work and standalone work have different inspection paths; the [cloud agents overview](https://docs.warp.dev/platform/#monitor-inspect-and-share-cloud-agent-runs) links to each. ## Environments An [environment](https://docs.warp.dev/platform/environments/) defines a Docker image with your toolchain, repositories, and setup commands. Use the [environment setup reference](https://docs.warp.dev/platform/environments/configuring-environments/) for standalone runs and [factory runners](https://docs.warp.dev/factories/runners/) for factory execution. ## Hosts A host is where the agent executes. By default, runs execute on [Warp-hosted infrastructure](https://docs.warp.dev/factories/warp-hosting/), with nothing to set up. On Enterprise plans, [self-hosted runners](https://docs.warp.dev/factories/self-hosting/) keep code and execution inside your own network while Warp still tracks the runs. ## The CLI Use the [Oz CLI](https://docs.warp.dev/agents/cli/oz-cli/) for `oz` workflows in CI, scripts, and remote servers. The [Warp Agent CLI](https://docs.warp.dev/agents/cli/) runs the Warp Agent with `warp`. ## API and SDKs Use the [Warp Platform API and SDKs](https://docs.warp.dev/factories/developer-tools/) to send work from your own services. [Factory endpoints](https://docs.warp.dev/factories/factory-api/) dispatch by factory UID; [agent and run endpoints](https://docs.warp.dev/factories/api-and-sdk/) start standalone runs and inspect, continue, or cancel runs. The official [`warp-platform-sdk` Python package](https://pypi.org/project/warp-platform-sdk/) and [`@warp-dot-dev/warp-platform-sdk` TypeScript package](https://www.npmjs.com/package/@warp-dot-dev/warp-platform-sdk) provide typed requests, retries, and error handling. ## Secrets Agents often need credentials for APIs, cloud providers, databases, and MCP servers. Store them as [secrets](https://docs.warp.dev/platform/secrets/), and Warp injects them at runtime without exposing the values in logs or the UI. Secrets can be scoped to the whole team or to one person. ## Shared configuration For factories, declare shared [skills](https://docs.warp.dev/factories/factory-skills/), MCP servers, and execution defaults in the [factory definition](https://docs.warp.dev/factories/factory-as-code/). Standalone workflows also use [MCP servers](https://docs.warp.dev/platform/mcp/), [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/); follow each reference for its scope and setup. ## 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. - [Architecture](https://docs.warp.dev/platform/architecture/) - reference diagrams of the stack, the run lifecycle, and data boundaries. - [Cloud agents](https://docs.warp.dev/platform/) - what cloud agents are, how they get triggered, and how to run them with or without the Warp app. - [Cloud agents quickstart](https://docs.warp.dev/platform/quickstart/) - run a cloud agent from Warp. - [Environments](https://docs.warp.dev/platform/environments/) - define the toolchain and repos a run executes against. - [Multi-agent orchestration](https://docs.warp.dev/platform/orchestration/) - divide work among parent and child agents. - [Warp Platform API](https://docs.warp.dev/factories/api-and-sdk/) - drive the platform programmatically.