> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Transitioning from Oz to Warp Factories

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

| Surface | Current use |
| --- | --- |
| **Oz web app** | Existing standalone cloud-agent workflows have their own [web app setup and management paths](https://docs.warp.dev/platform/oz-web-app/). |
| **Oz CLI (`oz`)** | Existing commands remain supported during the transition. Use the [legacy CLI reference](https://docs.warp.dev/agents/cli/oz-cli/). |
| **Warp Agent CLI (`warp`)** | Use the [Warp Agent CLI reference](https://docs.warp.dev/agents/cli/) for its supported commands. |
| SDKs | Use the current [Python and TypeScript packages](https://docs.warp.dev/factories/api-and-sdk/#sdks). Repository names and package names can differ. |
| **Warp Platform API** | Consult the [API reference](https://docs.warp.dev/api) for endpoint behavior and configuration. Use [factory endpoints](https://docs.warp.dev/factories/factory-api/) to send work to a factory. |
| **New software factories** | Open the [Warp Factories web app](https://platform.warp.dev) and follow the [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/). |

## Moving an existing workflow

### Existing web app workflows

The [Oz web app](https://oz.warp.dev) and the [Warp Factories web app](https://platform.warp.dev) have different setup paths. Review the agents, skills, environments, schedules, integrations, and credentials your workflow uses before moving it into a factory. Creating a factory is not evidence that those resources or run history have transferred.

For factory setup, see [how Warp Factories work](https://docs.warp.dev/factories/how-factories-work/) and the [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/). Contact your account team or [Warp support](https://docs.warp.dev/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](https://docs.warp.dev/agents/cli/oz-cli/) for the current command reference and the [Warp Agent CLI](https://docs.warp.dev/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](https://docs.warp.dev/factories/api-and-sdk/#sdks).

Use the [Warp Platform API reference](https://docs.warp.dev/api) to check the endpoints and configuration your integration needs. To send work through a factory, use [factory endpoints](https://docs.warp.dev/factories/factory-api/) rather than treating a standalone agent run as the same workflow.

## Related pages

-   [Automation Platform overview](https://docs.warp.dev/platform/overview/) - Understand the shared execution and configuration model.
-   [Warp Factories overview](https://docs.warp.dev/factories/) - Build and operate a standing software factory.
-   [Warp Platform API and SDKs](https://docs.warp.dev/factories/developer-tools/) - Use factory endpoints, agent and run endpoints, SDKs, and API errors.