Migrate from Cua Cloud and deprecated packages

Cua Cloud and Fleets ended on 18 October 2026, and cuabot, cua-computer, cua-computer-server and cua-agent are no longer maintained. What changed and what to use instead.

Cua Cloud (Fleets) has ended#

Cua Cloud, including Cua Fleets (pools, claims, warm replicas and the Terraform provider), ended on 18 October 2026. The Fleets pages have been removed.

What still works#

The same SDK calls, images and cua CLI commands run anywhere else:

WhereHowGuide
This machineSandbox.create(...) (the default), cua sb createChoose where sandboxes run
Your own AWS, Google Cloud or Modal accounton="aws", on="gcp", on="modal"; --on aws in the CLIChoose where sandboxes run
A machine you run, shared with your team and agentsCua SpacesCua Spaces

In your code#

on="cloud", local=False, --on cloud and pool: image references fail with this message:

Cua Cloud has ended; use a local sandbox or your own computer. See https://cua.ai/docs/cua-sdk/guides/cua-cloud-ended

Cua.fleet(), cua fleet, cua pools, --pool, FLEETS_TOKEN, cloud image listings and cloud suspend, resume and extend-lease are removed from the SDKs and the cua CLI.

Replace on="cloud" with a local runtime or your own cloud. Sidecars, services, secrets and images work the same way there: Sidecars, services, secrets and images.

Fleet pool names, claim TTLs and warm-replica settings have no replacement. Your own cloud gives each sandbox a time limit and cleans up after it (Time limits and cleanup).

Questions: GitHub issues or Discord.

Deprecated packages#

Deprecated

Cua no longer maintains cuabot, cua-computer, cua-computer-server or cua-agent. They will not receive updates or fixes. Existing releases stay on npm and PyPI, so current installs keep installing, but you should move off them.

Do not run cuabot

cuabot has known security issues and is no longer maintained. Do not run it. If it is installed, stop and remove it now.

PackageRegistryLast releaseUse instead
cuabotnpm1.0.14Cua Driver over MCP, or a sandbox from the cua CLI or Cua Spaces
cua-computerPyPI0.5.19The cua SDK (cua-sandbox) for sandboxes, Cua Driver for the machine you are on
cua-computer-serverPyPI0.3.46Images that ship cua-spacesd, or Cua Driver on a host
cua-agentPyPI0.9.0A coding agent with the Cua Driver MCP, or sandbox.agents()

cuabot#

cuabot ran coding agents in a Docker sandbox with a local server and a desktop you could watch. Stop it, uninstall it and remove what it created:

cuabot --stop                      # repeat with --name <session> for each named session
npm uninstall -g cuabot            # or delete any local node_modules/cuabot
docker rm -f cuabot-xpra
docker images -q trycua/cuabot | xargs docker rmi
rm -rf ~/.cuabot

Instead:

cua-computer#

cua-computer was the Python Computer class that started a VM or container and drove it through cua-computer-server. Use the cua SDK instead: it creates local sandboxes and sandboxes in your own cloud, and Sandbox exposes the screen, input, shell and files. Start with the SDK quickstart and the sandbox reference.

To operate native apps on the machine you are on, use Cua Driver.

cua-computer-server#

cua-computer-server was the HTTP and WebSocket server inside a guest that cua-computer talked to. The in-guest agent is now cua-spacesd, which Cua Spaces and the current sandbox images ship. Nothing in the cua SDK talks to cua-computer-server any more. Images built before that change still carry it; see the image catalog for which ones.

To drive a desktop directly, install Cua Driver on it.

cua-agent#

cua-agent was the Python ComputerAgent loop with LiteLLM. Bring your own agent instead: