Factories > Overview
Transitioning from Oz to Warp Factories
# Transitioning from Oz to Warp Factories Warp Factories supports multi-stage software development workflows. If you have an existing workflow in the Oz web app, the CLI, or an SDK, review the setup it uses before moving work into a factory. ## Current status | Surface | Current use | | --- | --- | | **Oz web app** | Existing standalone cloud-agent workflows have their own [web app setup and management paths](/platform/oz-web-app/). | | **Oz CLI (`oz`)** | Existing commands remain supported during the transition. Use the [legacy CLI reference](/agents/cli/oz-cli/). | | **Warp Agent CLI (`warp`)** | Use the [Warp Agent CLI reference](/agents/cli/) for its supported commands. | | SDKs | Use the current [Python and TypeScript packages](/factories/api-and-sdk/#sdks). Repository names and package names can differ. | | **Warp Platform API** | Consult the [API reference](/api) for endpoint behavior and configuration. Use [factory endpoints](/factories/factory-api/) to send work to a factory. | | **New software factories** | Open the <a href=https://platform.warp.dev>Warp Factories web app</a> and follow the [Warp Factories quickstart](/factories/quickstart/). | ## Moving an existing workflow ### Existing web app workflows The <a href=https://oz.warp.dev>Oz web app</a> and the <a href=https://platform.warp.dev>Warp Factories web app</a> have different setup paths. Review the agents, environments, schedules, integrations, and credentials your workflow uses before moving it into a factory. Do not assume that creating a factory transfers those resources or its run history. For factory setup, see [how Warp Factories work](/factories/how-factories-work/) and the [Warp Factories quickstart](/factories/quickstart/). Contact your account team or [Warp support](/support-and-community/#contact-support) if you need help assessing an existing workflow. ### CLI functionality Continue using `oz` commands for existing workflows. Use the [Oz CLI](/agents/cli/oz-cli/) for the current command reference and the [Warp Agent CLI](/agents/cli/) for current `warp` functionality. Check the relevant reference before changing a command in a script. ### SDK packages and API The official SDK repositories keep their existing names: [Python](https://github.com/warpdotdev/oz-sdk-python) and [TypeScript](https://github.com/warpdotdev/oz-sdk-typescript). Current packages are `warp-platform-sdk` for Python and `@warp-dot-dev/warp-platform-sdk` for TypeScript; see [SDK installation and imports](/factories/api-and-sdk/#sdks). Use the [Warp Platform API reference](/api) to check the endpoints and configuration your integration needs. To send work through a factory, use [factory endpoints](/factories/factory-api/) rather than treating a standalone agent run as the same workflow. ## 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 and SDKs](/factories/developer-tools/) - Use factory endpoints, agent and run endpoints, SDKs, and API errors.Tell me about this feature: https://docs.warp.dev/platform/transitioning-from-oz/Find the current web app, CLI, SDK, and API paths for existing Oz workflows and what to consider when moving work into Warp Factories.
Warp Factories supports multi-stage software development workflows. If you have an existing workflow in the Oz web app, the CLI, or an SDK, review the setup it uses before moving work into a factory.
Current status
Section titled “Current status”| Surface | Current use |
|---|---|
| Oz web app | Existing standalone cloud-agent workflows have their own web app setup and management paths. |
Oz CLI (oz) | Existing commands remain supported during the transition. Use the legacy CLI reference. |
Warp Agent CLI (warp) | Use the Warp Agent CLI reference for its supported commands. |
| SDKs | Use the current Python and TypeScript packages. Repository names and package names can differ. |
| Warp Platform API | Consult the API reference for endpoint behavior and configuration. Use factory endpoints to send work to a factory. |
| New software factories | Open the Warp Factories web app and follow the Warp Factories quickstart. |
Moving an existing workflow
Section titled “Moving an existing workflow”Existing web app workflows
Section titled “Existing web app workflows”The Oz web app and the Warp Factories web app have different setup paths. Review the agents, environments, schedules, integrations, and credentials your workflow uses before moving it into a factory. Do not assume that creating a factory transfers those resources or its run history.
For factory setup, see how Warp Factories work and the Warp Factories quickstart. Contact your account team or Warp support if you need help assessing an existing workflow.
CLI functionality
Section titled “CLI functionality”Continue using oz commands for existing workflows. Use the Oz CLI for the current command reference and the Warp Agent CLI for current warp functionality. Check the relevant reference before changing a command in a script.
SDK packages and API
Section titled “SDK packages and API”The official SDK repositories keep their existing names: Python and TypeScript. Current packages are warp-platform-sdk for Python and @warp-dot-dev/warp-platform-sdk for TypeScript; see SDK installation and imports.
Use the Warp Platform API reference to check the endpoints and configuration your integration needs. To send work through a factory, use factory endpoints rather than treating a standalone agent run as the same workflow.
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 and SDKs - Use factory endpoints, agent and run endpoints, SDKs, and API errors.