Factories > Overview
Transitioning from Oz to Warp Factories
# Transitioning from Oz to Warp Factories Warp Factories is the web experience for team development workflows organized around repositories, agents, and automations. Existing standalone cloud-agent workflows still use the Oz web app, CLI, SDKs, and API references listed below. ## 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`)** | Use the [Oz CLI reference](/agents/cli/oz-cli/) for current `oz` commands. The `oz` and `warp` binaries have separate command interfaces. | | **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/). | ## Preparing an existing workflow for Warp Factories Before adopting a factory, check your workflow's web app, CLI commands, SDK packages, and API endpoints against the references in the status table. ### Existing web app workflows Review the agents, skills, environments, schedules, integrations, and credentials your existing workflow uses before setting up a factory. See [viewing runs in the Oz web app](/platform/oz-web-app/#runs) to inspect your existing 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 Use the [Oz CLI](/agents/cli/oz-cli/) for the current `oz` 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 [factory endpoints](/factories/factory-api/) to send new work to a factory. Use [agent and run endpoints](/factories/api-and-sdk/) to inspect, continue, or cancel the resulting run. ## Related pages * [Automation Platform overview](/platform/overview/) - Understand the shared execution and configuration model. * [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 current web app, CLI, SDK, and API references for existing Oz workflows. Review your setup before adopting Warp Factories.
Warp Factories is the web experience for team development workflows organized around repositories, agents, and automations. Existing standalone cloud-agent workflows still use the Oz web app, CLI, SDKs, and API references listed below.
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) | Use the Oz CLI reference for current oz commands. The oz and warp binaries have separate command interfaces. |
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. |
Preparing an existing workflow for Warp Factories
Section titled “Preparing an existing workflow for Warp Factories”Before adopting a factory, check your workflow’s web app, CLI commands, SDK packages, and API endpoints against the references in the status table.
Existing web app workflows
Section titled “Existing web app workflows”Review the agents, skills, environments, schedules, integrations, and credentials your existing workflow uses before setting up a factory. See viewing runs in the Oz web app to inspect your existing 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”Use the Oz CLI for the current oz 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 factory endpoints to send new work to a factory. Use agent and run endpoints to inspect, continue, or cancel the resulting run.
Related pages
Section titled “Related pages”- Automation Platform overview - Understand the shared execution and configuration model.
- 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.