Factories
Transitioning from the Oz web app
# Transitioning from the Oz web app Existing users do not need to take action to keep using their current workflows. Warp Factories is the path for new standing, multi-stage software development workflows. ## Current status and future direction | Surface | Current status | Future direction | | --- | --- | --- | | **Oz web app** | Existing workflows continue to work. | Existing workflows remain supported. Migration guidance will be available over time. | | **Oz CLI (`oz`)** | Existing commands continue to work. | Relevant functionality moves toward the Warp Agent CLI. Warp will publish migration guidance before support changes. | | **Warp Agent CLI (`warp`)** | Available for its current supported functionality. | The preferred direction for CLI functionality. | | **`oz-sdk-python` and `oz-sdk-typescript`** | Existing SDK packages continue to work. | Packages may be renamed or repackaged under Warp with migration guidance. | | **Warp Platform API** | Existing endpoints continue to work; no endpoint migration is required. | Documentation and naming may change while compatibility remains. | | **New software factories** | Use [Warp Factories](https://platform.warp.dev) for new multi-stage development workflows. | Warp Factories remains the primary product experience for software factories. | ## Moving an existing workflow ### Existing web app workflows Continue using the <a href=https://oz.warp.dev>Oz web app</a> for existing cloud agents, environments, schedules, integrations, and runs. Moving an existing workflow into a factory is optional and evaluated case by case with an engineering DRI. ### CLI functionality Continue using `oz` commands for existing workflows. Use the [Oz CLI](/agents/cli/oz-cli/) for current command reference and the [Warp Agent CLI](/agents/cli/) for current `warp` functionality. ### SDK packages and API The official SDK repositories retain their current package names: [Python](https://github.com/warpdotdev/oz-sdk-python) and [TypeScript](https://github.com/warpdotdev/oz-sdk-typescript). Existing API integrations remain compatible as documentation moves to the [Warp Platform API](/factories/developer-tools/). ## Related pages * [Automation Platform overview](/platform/overview/) - Configure standalone cloud-agent workflows. * [Warp Factories overview](/factories/) - Build and operate a standing software factory. * [Warp Platform API & SDKs](/factories/developer-tools/) - Use factory endpoints, Agent & run endpoints, SDKs, and API errors.Tell me about this feature: https://docs.warp.dev/platform/transitioning-from-oz/Understand how legacy web app, CLI, SDK, and API workflows remain supported while Warp Factories becomes the path for new software factories.
Existing users do not need to take action to keep using their current workflows. Warp Factories is the path for new standing, multi-stage software development workflows.
Current status and future direction
Section titled “Current status and future direction”| Surface | Current status | Future direction |
|---|---|---|
| Oz web app | Existing workflows continue to work. | Existing workflows remain supported. Migration guidance will be available over time. |
Oz CLI (oz) | Existing commands continue to work. | Relevant functionality moves toward the Warp Agent CLI. Warp will publish migration guidance before support changes. |
Warp Agent CLI (warp) | Available for its current supported functionality. | The preferred direction for CLI functionality. |
oz-sdk-python and oz-sdk-typescript | Existing SDK packages continue to work. | Packages may be renamed or repackaged under Warp with migration guidance. |
| Warp Platform API | Existing endpoints continue to work; no endpoint migration is required. | Documentation and naming may change while compatibility remains. |
| New software factories | Use Warp Factories for new multi-stage development workflows. | Warp Factories remains the primary product experience for software factories. |
Moving an existing workflow
Section titled “Moving an existing workflow”Existing web app workflows
Section titled “Existing web app workflows”Continue using the Oz web app for existing cloud agents, environments, schedules, integrations, and runs. Moving an existing workflow into a factory is optional and evaluated case by case with an engineering DRI.
CLI functionality
Section titled “CLI functionality”Continue using oz commands for existing workflows. Use the Oz CLI for current command reference and the Warp Agent CLI for current warp functionality.
SDK packages and API
Section titled “SDK packages and API”The official SDK repositories retain their current package names: Python and TypeScript. Existing API integrations remain compatible as documentation moves to the Warp Platform API.
Related pages
Section titled “Related pages”- Automation Platform overview - Configure standalone cloud-agent workflows.
- Warp Factories overview - Build and operate a standing software factory.
- Warp Platform API & SDKs - Use factory endpoints, Agent & run endpoints, SDKs, and API errors.