Uninstall Cua Spaces

Remove Cua Spaces, the cua CLI and everything they set up with one command. Your Spaces and their data stay unless you ask for them to go.

One command removes Cua Spaces, the cua CLI and what they set up on this computer. It lists what it found and asks before it removes anything. Run it again any time: a computer that has nothing left, or only part of Cua, is fine.

curl -fsSL https://cua.ai/uninstall.sh | sh

To see what it would do first, add --dry-run (-DryRun on Windows). It prints every step and changes nothing:

curl -fsSL https://cua.ai/uninstall.sh | sh -s -- --dry-run

What it removes#

The Cua Spaces app.
The cua CLI, and the line the installer added to your shell profile (the user PATH on Windows).
The host service, after cua host remove, so this computer no longer shows up as a machine in your account.
The Cua skills and MCP entries in your AI agents, the way cua agents remove does. Entries from other tools stay.
Launch at login.
Your sign-in and the device key: macOS Keychain items (including the old run.cua.ai one), Windows Credential Manager entries.
Cua's settings, caches and logs.

What it keeps#

Your Spaces and their data. That is the Space disks under ~/.cua, the local Cua Volume files and the Keyvault. Running Spaces are listed and stopped first, and their disks stay.

Pass --keep-data (-KeepData) to also keep ~/.cua (settings, caches, the device key) and the app's settings, for a later reinstall. Programs, services, agent entries and your sign-in are still removed.

Delete Spaces and their data too#

--delete-spaces deletes the Spaces on this computer, the local Cua Volume files and the Keyvault. It cannot be undone.

curl -fsSL https://cua.ai/uninstall.sh | sh -s -- --delete-spaces

It lists the Spaces, stops the running ones, and asks you to type delete. --yes skips that question, so use it only in scripts you trust.

Options#

macOS and Linux	Windows	Effect
`--keep-data`	`-KeepData`	Keep `~/.cua` and the app's settings.
`--delete-spaces`	`-DeleteSpaces`	Also delete Spaces and their data (not together with `--keep-data`).
`--all`	`-All`	Also run the Cua Driver uninstaller and, on macOS, the Lume one. Lume keeps your VMs unless `--delete-spaces` is given too.
`--prefix DIR`	`-Prefix DIR`	Also remove what `install.sh --prefix DIR` installed.
`--no-modify-path`	`-NoModifyPath`	Never edit your shell profile or user PATH.
`--dry-run`	`-DryRun`	Print what would be removed, change nothing.
`--yes`	`-Yes`	Accept every question. Without a terminal, nothing is removed unless you pass it.

Other Cua tools#

Cua Driver and Lume are separate products. The command above leaves them alone and says so. Add --all to remove them too, or run their own uninstallers:

/bin/bash -c "$(curl -fsSL https://cua.ai/driver/uninstall.sh)"
/bin/bash -c "$(curl -fsSL https://cua.ai/lume/uninstall.sh)"

If a step needs your attention#

The command says what to run for anything it could not remove, and exits with a non-zero status.

An app or cua owned by root (installed from the .pkg, or with sudo): run the sudo rm line it prints, or run the whole uninstaller with sudo.
The Cua Spaces login item on macOS. The app registers itself, so a script cannot unregister it. With the app gone it has nothing to start. If a row is left in System Settings, Login Items, switch it off there.
A cua from pip, npm or Homebrew is not touched. Remove it with the tool that installed it.
The .deb on Linux needs root: sudo apt-get remove cua-spaces.

To install again: curl -fsSL https://cua.ai/install.sh | sh. See Install.

What it removes#

The Cua Spaces app.

The cua CLI, and the line the installer added to your shell profile (the user PATH on Windows).

The host service, after cua host remove, so this computer no longer shows up as a machine in your account.

The Cua skills and MCP entries in your AI agents, the way cua agents remove does. Entries from other tools stay.

Launch at login.

Your sign-in and the device key: macOS Keychain items (including the old run.cua.ai one), Windows Credential Manager entries.

Cua's settings, caches and logs.

What it keeps#

Your Spaces and their data. That is the Space disks under ~/.cua, the local Cua Volume files and the Keyvault. Running Spaces are listed and stopped first, and their disks stay.

Delete Spaces and their data too#

--delete-spaces deletes the Spaces on this computer, the local Cua Volume files and the Keyvault. It cannot be undone.

curl -fsSL https://cua.ai/uninstall.sh | sh -s -- --delete-spaces

It lists the Spaces, stops the running ones, and asks you to type delete. --yes skips that question, so use it only in scripts you trust.

Options#

macOS and Linux	Windows	Effect
`--keep-data`	`-KeepData`	Keep `~/.cua` and the app's settings.
`--delete-spaces`	`-DeleteSpaces`	Also delete Spaces and their data (not together with `--keep-data`).
`--all`	`-All`	Also run the Cua Driver uninstaller and, on macOS, the Lume one. Lume keeps your VMs unless `--delete-spaces` is given too.
`--prefix DIR`	`-Prefix DIR`	Also remove what `install.sh --prefix DIR` installed.
`--no-modify-path`	`-NoModifyPath`	Never edit your shell profile or user PATH.
`--dry-run`	`-DryRun`	Print what would be removed, change nothing.
`--yes`	`-Yes`	Accept every question. Without a terminal, nothing is removed unless you pass it.

If a step needs your attention#

The command says what to run for anything it could not remove, and exits with a non-zero status.

An app or cua owned by root (installed from the .pkg, or with sudo): run the sudo rm line it prints, or run the whole uninstaller with sudo.

The Cua Spaces login item on macOS. The app registers itself, so a script cannot unregister it. With the app gone it has nothing to start. If a row is left in System Settings, Login Items, switch it off there.

A cua from pip, npm or Homebrew is not touched. Remove it with the tool that installed it.

The .deb on Linux needs root: sudo apt-get remove cua-spaces.

To install again: curl -fsSL https://cua.ai/install.sh | sh. See Install.