Skip to content
Warp

Automation Platform > Overview

Automation Platform overview

Configure agents with Warp Factories, or run and manage cloud agents without a factory. Both use the Automation Platform.

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

Warp Factories and standalone cloud agents run on the Automation Platform. It provides the execution, configuration, and APIs they share.

Start with a factory

Section titled “Start with a factory”

For a team workflow with planning, implementation, and review, start with the Warp Factories quickstart. Then configure its agents, automations, and tools.

Already using the Oz web app, Oz CLI, or SDKs? Use transitioning from Oz to assess that workflow. The cloud agents overview retains standalone setup and management entry points.

How a run works

Section titled “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.

A trigger starts an agent, which runs in a configured environment and produces artifacts such as plans, pull requests, and conversation records.

A trigger starts a run that produces reviewable artifacts.

Integrations and triggers

Section titled “Integrations and triggers”

Factory automations route events from connected tools to factory agents. They also start runs on a schedule. For custom intake, use webhooks and factory endpoints.

Standalone workflows have separate integrations and scheduled runs. The CLI integration setup guide covers their configuration.

Inspecting results

Section titled “Inspecting results”

Inspect factory work from the factory dashboard. For standalone management, sharing, and steering, use the cloud-agent inspection paths.

Environments

Section titled “Environments”

Factories manage their workspace by default. Environments for factory agents cover the optional existing-environment path and standalone setup; runners cover compute configuration.

Hosts

Section titled “Hosts”

For factory hosting choices and requirements, compare Warp-hosted execution with managed self-hosting. Unmanaged execution covers standalone CLI workflows on infrastructure you operate.

The CLI

Section titled “The CLI”

Use the Oz CLI for existing oz workflows and the Warp Agent CLI for warp commands. Check the owning reference before changing a script.

API and SDKs

Section titled “API and SDKs”

Use factory endpoints to send work to a factory, and agent and run endpoints for standalone runs and run inspection. Developer tools links to the SDKs and full API reference.

Secrets

Section titled “Secrets”

Use factory secrets for credentials granted to factory agents and harness authentication for third-party provider credentials. The legacy secrets reference preserves standalone CLI and personal-secret workflows.

Shared configuration

Section titled “Shared configuration”

Factory-wide and per-agent settings live in the factory definition. The shared harness, environment, and MCP-server references explain factory and standalone configuration separately.

For instructions and reusable context, see factory skills, Rules, saved prompts, and environment variables. These have different scopes; follow the relevant reference.

Measuring factory work

Section titled “Measuring factory work”

Use Scorers, Benchmarks, and Self-improvement to evaluate factory work and propose changes to its configuration. See measure and improve for metric definitions and limitations.

Section titled “Related pages”