Transitioning to the Automation Platform and Warp Factories

Warp’s documentation is moving to a factory-first structure. Existing workflows, cloud agents, integrations, schedules, API keys, and the oz CLI remain available, so you don’t need to migrate immediately.

The Automation Platform remains the shared foundation for cloud agents. Warp Factories builds on those primitives for teams that need standing workflows with named agents, work intake, review stages, and measurement.

Choose the right entry point

• Use the Automation Platform - Configure standalone cloud agents, environments, schedules, integrations, and orchestration. Start with the Automation Platform overview or Cloud agents overview.
• Warp Factories - Use a repeatable workflow that routes work through named agents and tracks it in one place. Start with the Warp Factories overview or the factory quickstart.

What stays available

Current workflows and configuration continue to work during this documentation transition. Links from legacy API, SDK, and CLI reference paths point to their current documentation locations:

• API and SDK documentation - Available under Developer tools for Warp Factories.
• Legacy Oz CLI documentation - Available in the legacy CLI reference.
• Managed self-hosting documentation - Available in Managed self-hosting for Warp Factories.
• Standalone cloud-agent execution - Available in Unmanaged execution.

What comes next

This page will add verified migration actions, compatibility dates, and replacement destinations as the product transition is finalized. Until then, follow the documentation for the workflow you use today.

Related pages

• Automation Platform overview - Configure the reusable primitives behind cloud-agent workflows.
• Warp Factories overview - Build and operate a standing software factory.
• Factory dashboard - Inspect work items, runs, and factory settings.