Factories
Transitioning from the Oz web app
# Transitioning from the Oz web app Existing Automation Platform workflows remain supported. You don't need to change an existing workflow to use Warp Factories. For new multi-stage development workflows, use Warp Factories. A factory builds on the Automation Platform to route work through specialized agents, add review stages, and show the progress of work. ## Where to manage work * **Existing Automation Platform workflows** - Continue using the <a href=https://oz.warp.dev>Oz web app</a> for existing cloud agents, environments, schedules, integrations, and runs. * **New factory workflows** - Use the <a href=https://platform.warp.dev>factory dashboard</a> to build and operate multi-stage development workflows. Start with the [Warp Factories overview](/factories/) or the [factory quickstart](/factories/quickstart/). ## CLI, API, and SDK support Existing interfaces remain supported: * **Oz CLI** - Existing `oz` commands continue to work. * **Oz API & SDK** - Existing API endpoints and SDK packages continue to work. * **Cloud-agent configuration** - Existing agents, environments, schedules, integrations, API keys, and secrets remain available. ## Moving an existing workflow into a factory Moving an existing Automation Platform workflow into a factory is optional. Each workflow has different integrations, configuration, and operating requirements, so work with an engineering DRI to evaluate the move. Warp will publish guidance before any support change. ## Related pages * [Automation Platform overview](/platform/overview/) - Configure standalone cloud-agent workflows. * [Warp Factories overview](/factories/) - Build and operate a standing software factory. * [Factory dashboard](/factories/factory-dashboard/) - Inspect work items, runs, and factory settings.Tell me about this feature: https://docs.warp.dev/platform/transitioning-from-oz/Continue supported legacy cloud-agent workflows and decide whether Warp Factories fits new multi-stage development work.
Existing Automation Platform workflows remain supported. You don’t need to change an existing workflow to use Warp Factories.
For new multi-stage development workflows, use Warp Factories. A factory builds on the Automation Platform to route work through specialized agents, add review stages, and show the progress of work.
Where to manage work
Section titled “Where to manage work”- Existing Automation Platform workflows - Continue using the Oz web app for existing cloud agents, environments, schedules, integrations, and runs.
- New factory workflows - Use the factory dashboard to build and operate multi-stage development workflows. Start with the Warp Factories overview or the factory quickstart.
CLI, API, and SDK support
Section titled “CLI, API, and SDK support”Existing interfaces remain supported:
- Oz CLI - Existing
ozcommands continue to work. - Oz API & SDK - Existing API endpoints and SDK packages continue to work.
- Cloud-agent configuration - Existing agents, environments, schedules, integrations, API keys, and secrets remain available.
Moving an existing workflow into a factory
Section titled “Moving an existing workflow into a factory”Moving an existing Automation Platform workflow into a factory is optional. Each workflow has different integrations, configuration, and operating requirements, so work with an engineering DRI to evaluate the move. Warp will publish guidance before any support change.
Related pages
Section titled “Related pages”- Automation Platform overview - Configure standalone cloud-agent workflows.
- Warp Factories overview - Build and operate a standing software factory.
- Factory dashboard - Inspect work items, runs, and factory settings.