Skip to content

armgit / cua

Public Imported from GitHub
0

Scale computer-use 2.0 with open-source drivers, cross-OS sandboxes, and benchmarks for training, evaluation, and data generation.

docs(spaces): say computers instead of machines (CUA-3066) (#6313)

Francesco Bonacci4074d0dfadee
diff --git a/README.md b/README.md
index 64e861b721..6ee36dc1ba 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,7 @@
</picture>
</a>
- <p align="center"><strong>Give AI agents computers they can use.</strong><br>Cua Spaces gives your agents full desktops on your Mac and on machines you own. This repository also holds Cua Driver for desktop automation, Lume for local VMs, CUA-S1 decision models and Cua Bench for evaluating computer-use agents.</p>
+ <p align="center"><strong>Give AI agents computers they can use.</strong><br>Cua Spaces gives your agents full desktops on your Mac and on computers you own. This repository also holds Cua Driver for desktop automation, Lume for local VMs, CUA-S1 decision models and Cua Bench for evaluating computer-use agents.</p>
<p align="center"><strong><a href="https://spaces.cua.ai">Get Cua Spaces</a></strong></p>
@@ -29,7 +29,7 @@
<tr>
<td colspan="3" align="center" valign="top">
<a href="#cua-spaces">
- <img src="img/card-cua-spaces-wide.webp" alt="Cua Spaces: full desktops for your agents. macOS and Linux Spaces on machines you own." width="100%">
+ <img src="img/card-cua-spaces-wide.webp" alt="Cua Spaces: full desktops for your agents. macOS and Linux Spaces on computers you own." width="100%">
</a>
</td>
</tr>
@@ -66,7 +66,7 @@ Bring your own agent and model, or explore CUA-S1 for specialized decisions. Cua
## Cua Spaces
-Cua Spaces is a desktop app that gives your agents full desktops. Each desktop is a Space: a macOS VM built locally on your Mac, or a Linux or Omarchy image. Spaces run on your Mac, on other machines you own, and in [your own cloud account](https://cua.ai/docs/cua-sdk/guides/local-runtimes#your-own-cloud) (AWS, Google Cloud or Modal), and the app keeps them in your menu bar and notch.
+Cua Spaces is a desktop app that gives your agents full desktops. Each desktop is a Space: a macOS VM built locally on your Mac, or a Linux or Omarchy image. Spaces run on your Mac, on other computers you own, and in [your own cloud account](https://cua.ai/docs/cua-sdk/guides/local-runtimes#your-own-cloud) (AWS, Google Cloud or Modal), and the app keeps them in your menu bar and notch.
- **Teleport.** Move a signed-in app, such as Chrome or Slack, into a Space and it opens there still signed in. Your sessions stay in the Cua Keyvault, encrypted on your Mac, and reach a Space only after you approve.
- **Multiplayer.** You and your agents work on the same desktop, each with your own cursor. Step in to make a choice, then hand the desktop back.
@@ -134,7 +134,7 @@ Create and manage local macOS and Linux VMs on Apple Silicon using Apple's Virtu
## Cua SDK and CLI
-One SDK and one `cua` command for local VMs and containers, and for any machine that runs [cua-spacesd](libs/cua-spacesd/README.md).
+One SDK and one `cua` command for local VMs and containers, and for any computer that runs [cua-spacesd](libs/cua-spacesd/README.md).
**macOS / Linux**
@@ -168,7 +168,7 @@ async with Sandbox.ephemeral(Image.linux(), local=True) as sb:
- **SDK:** the same API in Python (`pip install cua`), TypeScript (`@trycua/cua`) and Rust (`cua-sdk`), running embedded in your process or through a shared `cua daemon`. Swift and Kotlin bindings are not yet released.
- **Sandboxes need no agent inside.** Readiness comes from the runtime and optional port probes. Images that ship cua-spacesd (port 3211) add processes, files, screenshots, input through cua-driver, and low-latency video and audio streaming. There is no agent layer in the SDK either: drive sandboxes from your own harness ([guide](https://cua.ai/docs/cua-sdk/guides/own-harness)).
-- **Your own machines.** `cua host setup` makes this machine reachable through the cua.ai relay with no port forwarding.
+- **Your own computers.** `cua host setup` makes this computer reachable through the cua.ai relay with no port forwarding.
**[SDK README](libs/cua/README.md)** | **[Quickstart](https://cua.ai/docs/cua-sdk/quickstart)** | **[CLI reference](https://cua.ai/docs/cua-cli/reference/cli)** | **[Sandbox SDK reference](https://cua.ai/docs/cua-sdk/reference/sandbox)**
@@ -229,7 +229,7 @@ Cua no longer maintains these. They will not receive updates or fixes, and exist
| Package | Registry | Use instead |
| -------------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| [cuabot](libs/cuabot/README.md) | npm | **Do not run it:** it has known security issues. Stop it and uninstall it ([how](libs/cuabot/README.md)), then use Cua Driver or the `cua` CLI. |
-| `cua-computer` | PyPI | The [`cua` SDK](#cua-sdk-and-cli) for sandboxes, [Cua Driver](#cua-driver) for the machine you are on |
+| `cua-computer` | PyPI | The [`cua` SDK](#cua-sdk-and-cli) for sandboxes, [Cua Driver](#cua-driver) for the computer you are on |
| `cua-computer-server` | PyPI | Images that ship [cua-spacesd](libs/cua-spacesd/README.md), or [Cua Driver](#cua-driver) |
| [cua-agent](libs/python/agent/README.md) | PyPI | A coding agent with the [Cua Driver MCP](https://cua.ai/docs/cua-driver/guides/connect-your-agent), or `sandbox.agents()` in the `cua` SDK |
| [cua-som](libs/python/som/README.md) | PyPI | [Cua Driver](#cua-driver) |
diff --git a/apps/cua-spaces/README.md b/apps/cua-spaces/README.md
index 59788c3738..07e20ed01b 100644
--- a/apps/cua-spaces/README.md
+++ b/apps/cua-spaces/README.md
@@ -67,8 +67,8 @@ is a step-by-step sheet:
1. **System**: Linux, macOS or Windows, the image (a dropdown of the published
entries of `libs/images/sandbox-images.json`, the same list the docs show),
and where it runs: This Mac, one of your own computers, or your own cloud
- account. Cua no longer rents cloud machines. **Advanced** picks the kind (container or virtual
- machine, when the image comes in both) and the runtime, offering only what
+ account. Cua no longer rents cloud computers. **Advanced** picks the kind (container or virtual
+ computer, when the image comes in both) and the runtime, offering only what
the image runs there: containers `auto`, `gvisor`, `runc`; VMs `auto` and
the image's `qemu` or `lume`.
2. **Resources**: CPU cores and memory.
@@ -78,28 +78,28 @@ is a step-by-step sheet:
Every create is one `create_space {image, on, kind, runtime, ...}` call.
Spaces on this Mac run through
`cua-vmm`. The notch "+" drop creates in the default location. **Connect by
-address** adds a machine that already runs cua-spacesd (`host:port` plus its
+address** adds a computer that already runs cua-spacesd (`host:port` plus its
token). Delete deletes a created Space's sandbox; a Space
added by address is only removed from the list.
-### First run and "This machine"
+### First run and "This computer"
The first launch shows the welcome flow in the main window, one step per page
with page dots: Welcome, Command line (put the bundled `cua` on PATH), Sign in,
-AI agents (cua skills and the cua MCP server), This machine, Done. Every write
+AI agents (cua skills and the cua MCP server), This computer, Done. Every write
asks first and shows its path.
-"This machine" asks what the machine is for:
+"This computer" asks what the computer is for:
-- **Access other machines**: nothing is installed. The signed-in account's
- own machines (`relay:<id>`) appear automatically.
-- **Set up this machine for unattended access**: `cua-host` (the library
+- **Access other computers**: nothing is installed. The signed-in account's
+ own computers (`relay:<id>`) appear automatically.
+- **Set up this computer for unattended access**: `cua-host` (the library
behind `cua host setup`) installs cua-spacesd as a service that joins the Cua
relay (`https://relay.cua.ai`, or `CUA_RELAY_URL`). Direct `ip:port` is
under **Advanced**. On macOS the Screen Recording and Accessibility panes are
listed for the user to open; nothing is granted programmatically.
-The sidebar always has a **This machine** entry with its sharing state and
+The sidebar always has a **This computer** entry with its sharing state and
**Stop sharing** / Resume / Remove.
### Installers
diff --git a/docs/content/docs/agents/add-a-machine.mdx b/docs/content/docs/agents/add-a-machine.mdx
index 7af562cc46..2557e8c0e6 100644
--- a/docs/content/docs/agents/add-a-machine.mdx
+++ b/docs/content/docs/agents/add-a-machine.mdx
@@ -1,20 +1,20 @@
---
-title: Add a machine
-description: 'For an AI agent: run a Cua Spaces image by hand on a cloud or machine your user owns, then add it to Cua Spaces with cua spaces add.'
+title: Add a computer
+description: 'For an AI agent: run a Cua Spaces image by hand on a cloud or computer your user owns, then add it to Cua Spaces with cua spaces add.'
---
Cua Spaces can't start this image on that cloud itself, so your user wants it run
by hand and added as a Space. Ask your user which image, which cloud and region,
-and the most they will spend, then wait for a yes. Machines you start in their
+and the most they will spend, then wait for a yes. Computers you start in their
cloud are billed to them. Tell them what you started and how to stop it.
## You run on your user's computer
-1. Start a machine in the cloud your user named, with the cloud's own CLI, big
+1. Start a computer in the cloud your user named, with the cloud's own CLI, big
enough for the image (a Linux desktop wants 2 CPUs and 4 GB of memory). Use a
firewall that lets in only your user's address or their tailnet on port 3211,
never the whole internet. Tag it so you can find it later.
-2. On the machine, run the image with a new token. This is the Linux desktop; use
+2. On the computer, run the image with a new token. This is the Linux desktop; use
the image your user named if it is another Cua Spaces image.
```bash skip="no-runner"
@@ -22,7 +22,7 @@ cloud are billed to them. Tell them what you started and how to stop it.
docker run -d --name cua-space -e CUA_ENV_TOKEN=$TOKEN -p 3211:3211 ghcr.io/trycua/linux:24.04
```
-3. From your user's machine, add it with its address and the token. Keep the
+3. From your user's computer, add it with its address and the token. Keep the
token in an environment variable, not in the chat or a file.
```bash test="cli-shape" id="agent-machine-add"
@@ -31,9 +31,9 @@ cloud are billed to them. Tell them what you started and how to stop it.
## You run in the cloud (hosted assistants)
-You can't reach your user's cloud account or machine from here. Tell your user the
+You can't reach your user's cloud account or computer from here. Tell your user the
image, cloud and steps above, and ask them to run them or to paste this link into an
-agent on their machine.
+agent on their computer.
## Check it worked
@@ -49,17 +49,17 @@ firewall and the token, and try again. Don't open the port wider to make it pass
## Don't
- Print the token or put it in a file, the chat or a shell history you can avoid.
-- Open port 3211 to everyone, or run the machine without a token.
-- Leave machines running that you started: tell your user, or stop them when done.
-- Touch machines, networks or users in the account that you did not create.
+- Open port 3211 to everyone, or run the computer without a token.
+- Leave computers running that you started: tell your user, or stop them when done.
+- Touch computers, networks or users in the account that you did not create.
## What you get
-- Nothing new for yourself. The machine is one more Space in your user's Cua
+- Nothing new for yourself. The computer is one more Space in your user's Cua
Spaces, and they or their agents can create work in it.
- The token is kept apart from the Space list, readable only by your user.
- Your user can forget it with `cua spaces rm <name>`. That does not stop the
- machine: stop it with the cloud's own CLI.
+ computer: stop it with the cloud's own CLI.
- It is a Space reached by its address (`direct:<address>:3211`), not one of
- your user's machines. How they differ:
- [Machines and Spaces](/spaces/concepts/machines-and-spaces).
+ your user's computers. How they differ:
+ [Computers and Spaces](/spaces/concepts/machines-and-spaces).
diff --git a/docs/content/docs/cua-cli/index.mdx b/docs/content/docs/cua-cli/index.mdx
index 5411f7a8a7..08402719f4 100644
--- a/docs/content/docs/cua-cli/index.mdx
+++ b/docs/content/docs/cua-cli/index.mdx
@@ -36,7 +36,7 @@ flags: [Install Cua Spaces](/spaces/guides/install).
| `cua daemon` | | Shared background runtime; `cua daemon mcp`. |
| `cua spaces` | | Registered Spaces and your relay machines ([Cua Spaces](/spaces)). |
| `cua cloud` | | Your own AWS, Google Cloud, Hetzner or Modal account as a location ([Choose where sandboxes run](/cua-sdk/guides/your-cloud)). |
-| `cua host` | | [Unattended access](/spaces/guides/add-a-computer#add-a-machine-from-a-terminal) to this machine. |
+| `cua host` | | [Unattended access](/spaces/guides/add-a-computer#add-a-computer-from-a-terminal) to this machine. |
| `cua teleport` | | [Move an app session](/spaces/guides/teleport-an-app) into a sandbox. |
| `cua image` | `img` | Local OCI images. |
| `cua spacesd` | | Talk to any cua-spacesd by URL. |
diff --git a/docs/content/docs/cua-sdk/guides/spacesd.mdx b/docs/content/docs/cua-sdk/guides/spacesd.mdx
index 1d709502c1..d353daba6b 100644
--- a/docs/content/docs/cua-sdk/guides/spacesd.mdx
+++ b/docs/content/docs/cua-sdk/guides/spacesd.mdx
@@ -46,7 +46,7 @@ on a machine, see [Run spacesd yourself](#run-spacesd-yourself); its RPCs are in
## Run spacesd yourself
On a machine you own, `cua host setup` installs spacesd as a service
-([Unattended access](/spaces/guides/add-a-computer#add-a-machine-from-a-terminal)). To run the binary by
+([Unattended access](/spaces/guides/add-a-computer#add-a-computer-from-a-terminal)). To run the binary by
hand:
```bash skip="no-runner"
diff --git a/docs/content/docs/spaces/concepts/how-spaces-works.mdx b/docs/content/docs/spaces/concepts/how-spaces-works.mdx
index cb9978665d..fe68e3a710 100644
--- a/docs/content/docs/spaces/concepts/how-spaces-works.mdx
+++ b/docs/content/docs/spaces/concepts/how-spaces-works.mdx
@@ -1,31 +1,31 @@
---
title: How Spaces works
-description: 'Machines and Spaces, bring-your-own compute, where a Space can run, and how you and your agents reach it directly or through the relay.'
+description: 'Computers and Spaces, bring-your-own compute, where a Space can run, and how you and your agents reach it directly or through the relay.'
---
-Cua Spaces connects three things: the machines you own, the Spaces on them, and
+Cua Spaces connects three things: the computers you own, the Spaces on them, and
the people and agents who use those Spaces.
-## Machines and Spaces
+## Computers and Spaces
-A **machine** is a Mac, Windows or Linux computer you own or rent. Sign in and
-all your machines appear in one list, **Machines**, each with its state on the
-row. A machine provides **Spaces**. A **Space** is the isolated sandbox: an
+A **computer** is a Mac, Windows or Linux PC you own or rent. Sign in and
+all your computers appear in one list, **Computers**, each with its state on the
+row. A computer provides **Spaces**. A **Space** is the isolated sandbox: an
image plus a kind (`vm`, `gvisor`, `microvm` or `container`), set up for a
-task. A machine can also share its own desktop as a Space. See
-[Machines and Spaces](/spaces/concepts/machines-and-spaces) for how they relate
+task. A computer can also share its own desktop as a Space. See
+[Computers and Spaces](/spaces/concepts/machines-and-spaces) for how they relate
and [Space kinds](/spaces/concepts/space-kinds) for the kinds.
-Cua doesn't rent machines. You bring them, and your cloud provider bills you for
+Cua doesn't rent computers. You bring them, and your cloud provider bills you for
any VM you run in your own account. Cua provides the app, sharing and the relay
-that lets your machines reach each other.
+that lets your computers reach each other.
## Where a Space runs
| Location | What it is |
|---|---|
-| This machine | A container or VM on the Mac, Windows or Linux PC you are using. |
-| Another of your machines | A machine you [added](/spaces/guides/add-a-computer) that provides Spaces, such as a [spare Mac mini](/spaces/guides/add-a-computer#use-a-spare-mac-to-host-spaces). |
+| This computer | A container or VM on the Mac, Windows or Linux PC you are using. |
+| Another of your computers | A computer you [added](/spaces/guides/add-a-computer) that provides Spaces, such as a [spare Mac mini](/spaces/guides/add-a-computer#use-a-spare-mac-to-host-spaces). |
| Your own cloud | A VM in your own AWS, Google Cloud or Modal account. See [Choose where sandboxes run](/cua-sdk/guides/your-cloud). |
Cua Cloud, the hosted option, has ended. See
@@ -36,12 +36,12 @@ Every Space runs `cua-spacesd`. It streams the screen, takes input through
## How you reach a Space
-- **Directly.** On the same network, or over Tailscale, your machine connects to
+- **Directly.** On the same network, or over Tailscale, your computer connects to
the Space with its address and a token. No account is needed, and the traffic
doesn't use the relay.
-- **Through the relay.** A machine set up with `cua host setup` joins the cua.ai
+- **Through the relay.** A computer set up with `cua host setup` joins the cua.ai
relay with an outbound connection, so you don't open ports. Your other
- machines, and people you share a Space with, reach it through the relay. Relay
+ computers, and people you share a Space with, reach it through the relay. Relay
use counts toward your [plan's](/spaces/guides/teams#plans) live sessions and
remote hours.
@@ -52,18 +52,18 @@ For what the relay can and can't see, see
| Kind | Id | Comes from |
|------|----|------------|
-| Local | `local:<name>` | `spaces.create(options)`: a new Space, on this machine by default |
-| Direct | `direct:<host:port>` | `spaces.add(url, token)`: an existing machine |
-| Relay | `relay:<machine-id>` | Your machines set up with `cua host setup`, listed automatically |
+| Local | `local:<name>` | `spaces.create(options)`: a new Space, on this computer by default |
+| Direct | `direct:<host:port>` | `spaces.add(url, token)`: an existing computer |
+| Relay | `relay:<machine-id>` | Your computers set up with `cua host setup`, listed automatically |
The app, the `cua` CLI, the SDKs and `cua daemon` share one registry
-(`~/.cua/spaces.json`). Relay machines come from your account's directory and
+(`~/.cua/spaces.json`). Relay computers come from your account's directory and
are never written to `spaces.json`.
## Who can do what
-You own your machines and the Spaces on them. You can
+You own your computers and the Spaces on them. You can
[share a Space](/spaces/guides/share-a-space) with another account as a viewer or
-an editor, and with [Teams](/spaces/guides/teams) a machine can belong to the
+an editor, and with [Teams](/spaces/guides/teams) a computer can belong to the
team instead of one person. Your agents act through the `cua` MCP server, and you
choose what each one may do. See [Connect your agent](/spaces/guides/connect-your-agent).
diff --git a/docs/content/docs/spaces/concepts/machines-and-spaces.mdx b/docs/content/docs/spaces/concepts/machines-and-spaces.mdx
index 16676feb0e..15a00120e4 100644
--- a/docs/content/docs/spaces/concepts/machines-and-spaces.mdx
+++ b/docs/content/docs/spaces/concepts/machines-and-spaces.mdx
@@ -1,22 +1,22 @@
---
-title: Machines and Spaces
-description: 'How machines, their shared desktops and Spaces relate: one list of machines, the state on each row, and the sandbox Space you actually work in.'
+title: Computers and Spaces
+description: 'How computers, their shared desktops and Spaces relate: one list of computers, the state on each row, and the sandbox Space you actually work in.'
---
-Cua Spaces has two things to know: **machines** and **Spaces**. A machine
+Cua Spaces has two things to know: **computers** and **Spaces**. A computer
provides Spaces. A Space is the isolated sandbox where work happens.
| Name | What it is | Where you see or use it |
| --- | --- | --- |
-| Machine | A Mac, Windows or Linux computer you added to your account, by signing in on it or with **Add a machine**. It can provide Spaces, share its own desktop, or both. | The **Machines** tab. `--on host:<machine-id>` creates new Spaces on it. |
-| Space | An isolated sandbox: an image plus a kind (`container`, `vm` or `microvm`; containers use gVisor where installed). See [Space kinds](/spaces/concepts/space-kinds). | The **Spaces** tab. `local:<name>` on this machine, or its own `relay:` id when it runs on another machine, with `host` naming the machine that runs it. A machine you added by address (set up with `--direct`, no relay) has a `direct:<host:port>` id. |
-| A machine's shared desktop | The machine's own screen, input, shell and files, shown as a Space while **Let other machines control this desktop** is on. It is not a sandbox. | `relay:<machine-id>` for a machine set up on the relay. A direct host is its own `direct:<host:port>` Space, added with `cua spaces add <host:port> --host`. |
+| Computer | A Mac, Windows or Linux computer you added to your account, by signing in on it or with **Add a computer**. It can provide Spaces, share its own desktop, or both. | The **Computers** tab. `--on host:<machine-id>` creates new Spaces on it. |
+| Space | An isolated sandbox: an image plus a kind (`container`, `vm` or `microvm`; containers use gVisor where installed). See [Space kinds](/spaces/concepts/space-kinds). | The **Spaces** tab. `local:<name>` on this computer, or its own `relay:` id when it runs on another computer, with `host` naming the computer that runs it. A computer you added by address (set up with `--direct`, no relay) has a `direct:<host:port>` id. |
+| A computer's shared desktop | The computer's own screen, input, shell and files, shown as a Space while **Let other computers control this desktop** is on. It is not a sandbox. | `relay:<machine-id>` for a computer set up on the relay. A direct host is its own `direct:<host:port>` Space, added with `cua spaces add <host:port> --host`. |
-## One list of machines
+## One list of computers
-Sign in on a machine and it joins your account. Every machine you own appears
-in the **Machines** tab on all the others. There is no second list to keep in
-step: a machine's state is a line on its row, and what you can do to it is on its page.
+Sign in on a computer and it joins your account. Every computer you own appears
+in the **Computers** tab on all the others. There is no second list to keep in
+step: a computer's state is a line on its row, and what you can do to it is on its page.
The state on a row is one of these:
@@ -25,43 +25,43 @@ The state on a row is one of these:
The shared desktop is not counted among the Spaces.
- **Signed in, not sharing**: you signed in on it, but it neither shares its
desktop nor provides Spaces. **New Space** never offers it as a place to run.
-- **Waiting for you**: a machine asking to join your account. Its page asks
- **Add this machine?** with **Add machine** and **Not me**.
+- **Waiting for you**: a computer asking to join your account. Its page asks
+ **Add this computer?** with **Add computer** and **Not me**.
-Machines you have not seen for 30 days collapse into **Offline for 30+ days**,
-and machines your team shares appear under **Team machines**.
+Computers you have not seen for 30 days collapse into **Offline for 30+ days**,
+and computers your team shares appear under **Team computers**.
-Open a machine to rename it, to turn its two switches on or off, to see the
+Open a computer to rename it, to turn its two switches on or off, to see the
Spaces on it, to press **New Space here**, to read its **Details**, or to remove
-it with **Remove from account**. Another machine's switches are read only: change
-them on that machine.
+it with **Remove from account**. Another computer's switches are read only: change
+them on that computer.
-## What a machine provides
+## What a computer provides
-Two switches decide what a machine does, and each works on its own:
+Two switches decide what a computer does, and each works on its own:
-- **Let other machines control this desktop** shows the machine's own screen as
- a Space for your other machines.
-- **Let other machines create Spaces here** lets your other machines, and
+- **Let other computers control this desktop** shows the computer's own screen as
+ a Space for your other computers.
+- **Let other computers create Spaces here** lets your other computers, and
teammates you share it with as editors, create sandbox Spaces on it.
-A machine that only provides Spaces keeps its own desktop private. A machine
+A computer that only provides Spaces keeps its own desktop private. A computer
that shares nothing is simply signed in.
-## One machine, two records
+## One computer, two records
-Behind the list, a machine can have two records: the relay's record of a machine
-that shares its desktop or provides Spaces (set up with **Add a machine** or
+Behind the list, a computer can have two records: the relay's record of a computer
+that shares its desktop or provides Spaces (set up with **Add a computer** or
`cua host setup`), and the record of a sign-in on it (made by `cua auth login`
-or the app). They describe one machine, and the **Machines** tab joins them into
+or the app). They describe one computer, and the **Computers** tab joins them into
one row when it can match them safely, for example by the same id or matching
names. If the match is unclear, such as two Macs with the same name, they stay as
separate rows. The `cua devices` commands manage the sign-in record, and
-`cua machines rm` removes a machine that is gone.
+`cua machines rm` removes a computer that is gone.
-A machine that only hosts, set up with `--direct` or with its own token, can't
-reach your other machines: signing in is what lets a machine see them.
+A computer that only hosts, set up with `--direct` or with its own token, can't
+reach your other computers: signing in is what lets a computer see them.
-See [Add a machine](/spaces/guides/add-a-computer) for the two switches and how
+See [Add a computer](/spaces/guides/add-a-computer) for the two switches and how
to add one, and [How Spaces works](/spaces/concepts/how-spaces-works#space-ids)
for Space ids.
diff --git a/docs/content/docs/spaces/concepts/space-kinds.mdx b/docs/content/docs/spaces/concepts/space-kinds.mdx
index 6e4ebd5dfe..43f3f98a2d 100644
--- a/docs/content/docs/spaces/concepts/space-kinds.mdx
+++ b/docs/content/docs/spaces/concepts/space-kinds.mdx
@@ -1,12 +1,12 @@
---
title: 'Space kinds: container, VM, microVM'
-description: 'What a container, a VM and a microVM Space are, which machines run each, how Cua picks one, and how to ask for a kind in the CLI, the SDKs and the app.'
+description: 'What a container, a VM and a microVM Space are, which computers run each, how Cua picks one, and how to ask for a kind in the CLI, the SDKs and the app.'
---
import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
Every Space is one of three kinds. The kind decides how the Space is kept apart
-from the machine it runs on, how fast it starts, and which images it runs.
+from the computer it runs on, how fast it starts, and which images it runs.
## The three kinds
@@ -31,12 +31,12 @@ exec, files and ports work. A VM needs a Cua disk image. See
| Checkpoints and forks | Yes | Yes | Yes, except on Apple's Containerization |
Use a container for most Linux work: it starts fastest and runs on the most
-machines. Use a VM for Windows or macOS, or a full Linux desktop OS. Use a
+computers. Use a VM for Windows or macOS, or a full Linux desktop OS. Use a
microVM to run any Linux image, such as untrusted code, behind its own kernel.
-## Which machines run which kind
+## Which computers run which kind
-| Machine | `container` | `vm` | `microvm` |
+| Computer | `container` | `vm` | `microvm` |
| --- | --- | --- | --- |
| Mac, Apple silicon | Yes | QEMU; Lume for macOS guests | `vz` on macOS 14 or later; `containerization` on macOS 26 or later |
| Mac, Intel | Yes | QEMU | No |
@@ -64,20 +64,20 @@ The microVM runtimes:
An [egress policy](/cua-sdk/guides/egress) is enforced on Firecracker
microVMs. On `vz` and Containerization microVMs it is refused.
-### Your own cloud and your other machines
+### Your own cloud and your other computers
-- **Another of your machines** runs the kinds it reports to your account.
-- **AWS**: a pool machine needs KVM for VM and microVM Spaces. Of the machine
- types Cua offers, only bare metal (`c6g.metal`) has it. A metal machine costs
+- **Another of your computers** runs the kinds it reports to your account.
+- **AWS**: a pool computer needs KVM for VM and microVM Spaces. Of the computer
+ types Cua offers, only bare metal (`c6g.metal`) has it. A metal computer costs
dollars an hour, so a single small request is refused unless you allow it
with `cua cloud budget --allow-metal on`.
-- **Hetzner and Google Cloud**: the machine types Cua offers have no KVM, so
+- **Hetzner and Google Cloud**: the computer types Cua offers have no KVM, so
they run containers only.
- **Modal**: `--on modal --kind microvm` (or `--runtime microvm`) runs the
sandbox on Modal's VM runtime. Linux images only.
`cua cloud plan --kind microvm` shows where microVM Spaces would go and which
-machines the pool would add for them. See
+computers the pool would add for them. See
[Use your own cloud](/cua-sdk/guides/your-cloud).
## How the default is chosen
@@ -100,7 +100,7 @@ or CI job). A default that does not fit an explicit request is skipped. See
[Change the default](/cua-sdk/guides/local-runtimes#change-the-default).
Some tools have their own default: `cua build` builds a VM, and
-`cua compat serve` makes VMs where this machine can accelerate them, else
+`cua compat serve` makes VMs where this computer can accelerate them, else
containers.
## Pick a kind
@@ -158,10 +158,10 @@ const sb = await embedded().sandboxes().create(
In Cua Spaces, press **New Space**, then open **Advanced** in **Choose a
system**. **Kind** offers **Container**, **Virtual machine** and **MicroVM**,
with one line under it that says what the chosen kind is. **Runtime** picks
-the engine: for a microVM, the microVM runtimes ready on this machine.
+the engine: for a microVM, the microVM runtimes ready on this computer.
-**MicroVM** is offered only when the machine in **Run on** runs microVMs: this
-machine when its runtime check has one ready, another of your machines when
+**MicroVM** is offered only when the computer in **Run on** runs microVMs: this
+computer when its runtime check has one ready, another of your computers when
it reports the kind. Otherwise it is greyed out, and the line under **Kind**
says why (for example `MicroVM needs macOS 26.` or `MicroVM needs KVM.`). The
app sends the same `kind="microvm"` as the CLI.
@@ -172,7 +172,7 @@ app sends the same `kind="microvm"` as the CLI.
A kind or runtime the location does not offer fails with `InvalidPlacement`,
and the message lists the valid values.
-The [E2B, Daytona and Modal SDKs](/spaces/guides/sandbox-sdks#what-you-get-on-your-own-machines)
+The [E2B, Daytona and Modal SDKs](/spaces/guides/sandbox-sdks#what-you-get-on-your-own-computers)
take the kind as `cua.kind` in E2B metadata, Daytona labels and Modal
`experimental_options`, and
[cua-e2b](/spaces/guides/sandbox-sdks#use-cua-e2b-in-place-of-e2b) takes
diff --git a/docs/content/docs/spaces/examples/infinite-canvas.mdx b/docs/content/docs/spaces/examples/infinite-canvas.mdx
index fa2a1627f2..75193d9e23 100644
--- a/docs/content/docs/spaces/examples/infinite-canvas.mdx
+++ b/docs/content/docs/spaces/examples/infinite-canvas.mdx
@@ -37,7 +37,7 @@ swift build -c release
.build/release/infinite-canvas --spaces spaces.json --show
```
-`spaces.json` lists the Spaces to show (any machine running cua-spacesd):
+`spaces.json` lists the Spaces to show (any computer running cua-spacesd):
```json skip="no-runner"
{
diff --git a/docs/content/docs/spaces/guides/add-a-computer.mdx b/docs/content/docs/spaces/guides/add-a-computer.mdx
index a55a4b65a9..04fd87a600 100644
--- a/docs/content/docs/spaces/guides/add-a-computer.mdx
+++ b/docs/content/docs/spaces/guides/add-a-computer.mdx
@@ -1,80 +1,80 @@
---
-title: Add a machine
-description: 'Connect another Mac, Windows or Linux machine you own to Cua Spaces, so your agents and your other machines can use it. Also how to turn a spare Mac into a place that runs Spaces.'
+title: Add a computer
+description: 'Connect another Mac, Windows or Linux computer you own to Cua Spaces, so your agents and your other computers can use it. Also how to turn a spare Mac into a place that runs Spaces.'
---
import { Callout } from 'fumadocs-ui/components/callout';
-A machine you add runs Spaces for you. Once it is added, it shows up in
-**Machines** on all your machines, your agents can create Spaces on it, and you
+A computer you add runs Spaces for you. Once it is added, it shows up in
+**Computers** on all your computers, your agents can create Spaces on it, and you
can open its desktop from anywhere, even when nobody is sitting at it. Cua
-doesn't rent machines: add a Mac on your desk, a spare box in the office, or a
+doesn't rent computers: add a Mac on your desk, a spare box in the office, or a
VM in your own cloud account. For a walkthrough of each, see
[Bring your own compute](/spaces/guides/bring-your-own-compute).
-![Add a machine: one row per way to add it, and a prompt for an agent on the other machine](/img/spaces/add-a-computer.png)
+![Add a computer: one row per way to add it, and a prompt for an agent on the other computer](/img/spaces/add-a-computer.png)
-## Add a machine from the app
+## Add a computer from the app
-In Cua Spaces, open **Machines** and press **Add a machine**. You can also
+In Cua Spaces, open **Computers** and press **Add a computer**. You can also
find it in the command palette. The sheet
-lists the ways to add one; pick the one that suits the other machine.
+lists the ways to add one; pick the one that suits the other computer.
-| Way | What to do on the other machine |
+| Way | What to do on the other computer |
|---|---|
-| **Sign in there** | Open `https://cua.ai/install`, install Cua Spaces and sign in with the same account. Signing in adds the machine. No code needed. |
-| **Open a link** | Open the one-time link the sheet shows. The page gives the install command for that machine, which installs Cua Spaces and adds it. |
-| **Scan a QR code** | Scan the code with that machine's camera. It opens the same link. |
+| **Sign in there** | Open `https://cua.ai/install`, install Cua Spaces and sign in with the same account. Signing in adds the computer. No code needed. |
+| **Open a link** | Open the one-time link the sheet shows. The page gives the install command for that computer, which installs Cua Spaces and adds it. |
+| **Scan a QR code** | Scan the code with that computer's camera. It opens the same link. |
| **Run a command** | Run the command in a terminal. **macOS / Linux** and **Windows (preview)** each have their own. |
-| **Enter a code** | For a machine that already has Cua Spaces. There, open **Add a machine**, choose **Have a code? Enter it** and type the code. |
+| **Enter a code** | For a computer that already has Cua Spaces. There, open **Add a computer**, choose **Have a code? Enter it** and type the code. |
You can also paste the prompt under **Or paste this into an agent on that
-machine** into an AI agent running there. It carries the same one-time code.
+computer** into an AI agent running there. It carries the same one-time code.
-The sheet waits for the machine and then says **Added** with its name,
+The sheet waits for the computer and then says **Added** with its name,
whichever way you used. The link, code, command and prompt work once and
expire after 30 minutes. While the sheet is open they renew by themselves. The
**⋯** menu shows how long the code has left, makes a new one, or revokes it.
If you are an owner or admin of a team on the Teams plan, choose the team next
to **For** at the bottom of the sheet. See
-[Team machines](/spaces/guides/teams#team-machines).
+[Team computers](/spaces/guides/teams#team-computers).
A `cua://add/<code>` link opens **Enter a code** with the code filled in. The
-app asks before this machine joins.
+app asks before this computer joins.
<Callout type="warn">
- Only use a code you made yourself. Joining adds the machine to the account
+ Only use a code you made yourself. Joining adds the computer to the account
that made the code, and that account can then reach it.
</Callout>
-A machine added from this sheet, or by signing in, provides Spaces and keeps
-its screen private. Turn off **Let other machines create Spaces here** in
+A computer added from this sheet, or by signing in, provides Spaces and keeps
+its screen private. Turn off **Let other computers create Spaces here** in
**Settings** to stop it running Spaces for you, and turn on **Let other
-machines control this desktop** on its page under **Machines** to see and
-control its screen from your other machines. With both off, the machine simply
+computers control this desktop** on its page under **Computers** to see and
+control its screen from your other computers. With both off, the computer simply
isn't shared.
-## Add a machine from the web
+## Add a computer from the web
You can also start from your account page, with no app open. Sign in at
[app.cua.ai](https://app.cua.ai), open **Computers** (this guide calls them
-machines) and press **Add with a pairing code**. The page shows a one-time
+computers) and press **Add with a pairing code**. The page shows a one-time
code, a link, a QR code and an install command for macOS, Linux and Windows
-(preview). Run the command in a terminal on the other machine, or open the
-link there. The new machine appears on the page when it is added. The code
+(preview). Run the command in a terminal on the other computer, or open the
+link there. The new computer appears on the page when it is added. The code
works once and expires in about 30 minutes.
-## Add a machine from a terminal
+## Add a computer from a terminal
-If you can't use the link, set the machine up yourself:
+If you can't use the link, set the computer up yourself:
1. Install Cua Spaces on it. See [Install](/spaces/guides/install).
-2. Sign in with the same account you use here. Signing in adds the machine to
+2. Sign in with the same account you use here. Signing in adds the computer to
that account. The installer does the same after it signs you in; add
- `--no-host` to sign in without adding the machine.
+ `--no-host` to sign in without adding the computer.
-Or run this in a terminal on that machine:
+Or run this in a terminal on that computer:
```bash test="cli-shape" id="cua-host-setup-add"
cua host setup # signs in to cua.ai for this command if needed
@@ -82,30 +82,30 @@ cua host setup # signs in to cua.ai for this command if needed
`cua host setup` installs cua-spacesd as a background service. By default it
joins the cua.ai relay with an outbound connection, as your account: no port
-forwarding and no token to copy. Your other machines, once
-[you have added them to your account](#reach-it-from-your-other-machines), then see the machine as
+forwarding and no token to copy. Your other computers, once
+[you have added them to your account](#reach-it-from-your-other-computers), then see the computer as
`relay:<machine-id>` in `cua spaces ls` and in the app.
-The machine keeps only its own token. If it is not signed in, setup
+The computer keeps only its own token. If it is not signed in, setup
signs you in for that one command and stores no session, so a dedicated host
-holds no account credentials. The token lets the machine serve itself and stop
-sharing. It can't list or reach your other machines, change who the machine is
-shared with, or add machines to your account. Running `setup` again updates the configuration
+holds no account credentials. The token lets the computer serve itself and stop
+sharing. It can't list or reach your other computers, change who the computer is
+shared with, or add computers to your account. Running `setup` again updates the configuration
and rotates the token.
| Option | Effect |
|--------|--------|
-| `--remote` | When sign-in is needed, print a sign-in code to approve in a browser on another machine (for example over SSH). The account session is not saved. Cannot be combined with `--direct`. |
+| `--remote` | When sign-in is needed, print a sign-in code to approve in a browser on another computer (for example over SSH). The account session is not saved. Cannot be combined with `--direct`. |
| `--direct ip:port` | Serve on your LAN (or a forwarded port) with a local env token instead of the relay. No account needed. |
| `--relay URL` | Use a different relay (`CUA_RELAY_URL`). The default is `https://relay.cua.ai`. |
| `--name NAME` | Display name (default: host name). |
| `--allow ACCOUNT` | Also allow this account (id or email). Repeatable. |
| `--runner KIND` | `auto`, `systemd`, `launchd`, `windows-task` or `process`. On Linux, `auto` uses systemd when it is running, otherwise `process`. |
-| `--share desktop\|spaces\|both\|none` | What this machine shares: `desktop` (this desktop only), `spaces` (create Spaces for your machines and keep its own desktop private; see [Use a spare Mac to host Spaces](#use-a-spare-mac-to-host-spaces)), `both`, or `none` (refused: there is nothing to share). Without it the desktop is shared, and a machine set up for the first time also provides Spaces; a machine set up before keeps its setting. `cua host config` changes it later. |
+| `--share desktop\|spaces\|both\|none` | What this computer shares: `desktop` (this desktop only), `spaces` (create Spaces for your computers and keep its own desktop private; see [Use a spare Mac to host Spaces](#use-a-spare-mac-to-host-spaces)), `both`, or `none` (refused: there is nothing to share). Without it the desktop is shared, and a computer set up for the first time also provides Spaces; a computer set up before keeps its setting. `cua host config` changes it later. |
## What each system needs
-| System | Service setup installs | Before the machine is reachable |
+| System | Service setup installs | Before the computer is reachable |
|---|---|---|
| macOS | LaunchAgent `com.trycua.spacesd.host` in your GUI session | Grant cua-spacesd **Screen Recording** and **Accessibility** in System Settings, and [Cua Driver](/cua-driver/quickstart) its own permissions. Setup can't do it for you. |
| Windows | Scheduled task `Cua\SpacesdHost` at logon, in your interactive session | Stay signed in and unlocked. After a restart, sign in once. |
@@ -113,7 +113,7 @@ and rotates the token.
`cua host status` shows the runner in use.
-On Windows the host runs in your signed-in session, so your machines reach the
+On Windows the host runs in your signed-in session, so your computers reach the
desktop only while it is signed in, unlocked and on screen:
- **After a restart**, sign in once (or turn on automatic sign-in). The host
@@ -128,34 +128,34 @@ desktop only while it is signed in, unlocked and on screen:
A viewer or agent that connects in one of these states sees which one it is.
-## Reach it from your other machines
+## Reach it from your other computers
-One account, one list of machines. Your other machines see this one in
-**Machines** once you have added them to your account and they are trusted. A
-machine reaches the rest through the cua.ai relay only after you have added it
+One account, one list of computers. Your other computers see this one in
+**Computers** once you have added them to your account and they are trusted. A
+computer reaches the rest through the cua.ai relay only after you have added it
once with a second factor, so a stolen account session alone is not enough. A
-machine that only hosts never gets this access: it joins with its own token and
-can't reach your other machines.
+computer that only hosts never gets this access: it joins with its own token and
+can't reach your other computers.
-- **Sign in.** Signing in on your own machine adds it. If the app has not done
- it for you, run `cua devices enroll` right after `cua auth login`. A machine
+- **Sign in.** Signing in on your own computer adds it. If the app has not done
+ it for you, run `cua devices enroll` right after `cua auth login`. A computer
you added before checks itself again when you sign in again.
-- **Approve.** A new machine on an account that already has an added machine
+- **Approve.** A new computer on an account that already has an added computer
waits for one of them to say yes (or for a sign-in whose token itself proves a
second factor with your identity provider). It shows under **Waiting for you**
- in **Machines**, and `cua devices enroll` prints a one-time code. Approve it
- from an added machine with `cua devices approve <code>`, or in the app, which
+ in **Computers**, and `cua devices enroll` prints a one-time code. Approve it
+ from an added computer with `cua devices approve <code>`, or in the app, which
asks for Touch ID.
-Every added machine is notified when a new one asks to join, in the app's
-notification feed and in `cua devices audit`, so a machine you don't recognize
+Every added computer is notified when a new one asks to join, in the app's
+notification feed and in `cua devices audit`, so a computer you don't recognize
doesn't slip in unnoticed. An addition lasts 30 days. After that, a fresh
-sign-in or one approval checks the machine again (its row says **Needs a quick
-check** until then). In the meantime, unattended agents on an added machine
+sign-in or one approval checks the computer again (its row says **Needs a quick
+check** until then). In the meantime, unattended agents on an added computer
keep working without prompts.
The `cua devices` commands are named after the sign-ins they manage, and they
-act on machines: one machine, one sign-in, one row in **Machines**.
+act on computers: one computer, one sign-in, one row in **Computers**.
```bash test="cli-shape" id="cua-devices"
cua devices enroll
@@ -166,28 +166,28 @@ cua devices audit # who opened which machine, from which machine, and when
cua devices revoke dev_0123456789abcdef01234567
```
-A machine that is gone: `cua machines rm <name>` removes it from your relay directory and revokes its sign-in.
+A computer that is gone: `cua machines rm <name>` removes it from your relay directory and revokes its sign-in.
-In the app, the **Machines** tab holds all of it. A machine that asks to join waits under
-**Waiting for you** with **Add machine** and **Not me** (Add machine asks for Touch ID or your login
+In the app, the **Computers** tab holds all of it. A computer that asks to join waits under
+**Waiting for you** with **Add computer** and **Not me** (Add computer asks for Touch ID or your login
password first, and Not me refuses it), and the sidebar shows how many wait. The state of every
-other machine is on its row: online, offline, **Desktop shared**, **Desktop and 2 Spaces** or
-**Signed in, not sharing**. What you can do to a machine is on its page: Rename, Revoke, the
-switches and its recent access (who opened it, and when). This machine's page says how far it is trusted.
+other computer is on its row: online, offline, **Desktop shared**, **Desktop and 2 Spaces** or
+**Signed in, not sharing**. What you can do to a computer is on its page: Rename, Revoke, the
+switches and its recent access (who opened it, and when). This computer's page says how far it is trusted.
## Keep a desktop in the notch
On a Mac, the notch lists the Spaces you can open and the shared desktop of each
-of your other machines. A desktop tile reads **Desktop** and opens the same
-desktop its page under **Machines** does, without creating anything. A machine
+of your other computers. A desktop tile reads **Desktop** and opens the same
+desktop its page under **Computers** does, without creating anything. A computer
that only provides Spaces has no desktop to show, so it is not listed. The
count on the closed notch is the Spaces and desktops that are running; with
none running it disappears.
To keep a desktop or a Space in front, choose **Pin to notch** from its **⋯**
-menu, on **Spaces** or on the machine's page under **Machines**, and **Unpin
+menu, on **Spaces** or on the computer's page under **Computers**, and **Unpin
from notch** to let it go. Pinned tiles come first, in the order you pinned
-them, then the rest as usual. A pinned desktop whose machine is off, or no
+them, then the rest as usual. A pinned desktop whose computer is off, or no
longer shares its desktop, stays on the notch dimmed and says **Offline** or
**Not shared**, and it is not counted. Pinning only changes what the notch
shows: it doesn't turn sharing on or give anyone access. Pins are saved in the
@@ -195,7 +195,7 @@ app's settings on that Mac.
## Share it with your team
-`--allow` at setup, or later from an added machine, shares the machine with
+`--allow` at setup, or later from an added computer, shares the computer with
someone in your team (id or verified email). Sharing is for teams: you need a
team, and they must be in it. See [Share a Space](/spaces/guides/share-a-space).
Sharing asks for confirmation. Unsharing cuts that account's open connections.
@@ -213,7 +213,7 @@ cua host unshare [email protected]
## Check, pause or remove
-On the machine, run:
+On the computer, run:
```bash test="cli-shape" id="cua-host-status"
cua host status # setup, service, who is connected; missing permissions
@@ -224,16 +224,16 @@ cua host remove # unregister, uninstall the service, delete ~/.cua/host
`cua host stop` turns sharing off locally first, so it holds even when the relay
is unreachable. In direct mode, `cua host status` prints the URL and the path of
-the env token. Add the machine elsewhere with
-[`spaces.add(url, token)`](/spaces/guides/add-a-space#add-an-existing-machine-by-address).
+the env token. Add the computer elsewhere with
+[`spaces.add(url, token)`](/spaces/guides/add-a-space#add-an-existing-computer-by-address).
Uninstalling the app turns sharing off too. On Linux, `sudo apt remove cua-spaces`
-(and `purge`) removes the machine, and the Spaces it provides, from the relay,
+(and `purge`) removes the computer, and the Spaces it provides, from the relay,
deletes the `cua-spacesd-host.service` user unit and stops the daemon. Your
-Spaces and data under `~/.cua` stay on the machine (the Spaces are turned off).
+Spaces and data under `~/.cua` stay on the computer (the Spaces are turned off).
-An owner or admin can remove a team machine at
-[app.cua.ai/machines](https://app.cua.ai/machines). Removing a machine doesn't
+An owner or admin can remove a team computer at
+[app.cua.ai/machines](https://app.cua.ai/machines). Removing a computer doesn't
delete anything on it.
## Use a spare Mac to host Spaces
@@ -242,7 +242,7 @@ A spare Mac mini in a closet can run Spaces for your laptop and your agents.
Your laptop, or a coding agent on it, asks for Spaces through the cua.ai relay or
[directly over Tailscale](#over-tailscale-without-the-relay). The mini runs them
with its own runtimes, Lume for macOS VMs and Docker for Linux. Its own desktop,
-shell and files stay private. To share a machine's own desktop instead, use the
+shell and files stay private. To share a computer's own desktop instead, use the
steps above.
### Set up the spare Mac
@@ -255,7 +255,7 @@ cua host setup --share spaces --name "Mac mini (spare)"
`--share spaces` shares no desktop and provides Spaces. Setup joins
the relay the way the steps above do. It signs you in for that one command and
-keeps no account session, only the machine's own token.
+keeps no account session, only the computer's own token.
Your laptop then reaches the Mac over Cua's
[end-to-end encrypted mesh](/spaces/guides/relay-security#end-to-end-encrypted-connections):
@@ -263,24 +263,24 @@ directly when the two networks allow it (on the same LAN that is the LAN),
through the relay as ciphertext otherwise. The relay introduces the two and
never holds the keys.
-For how a machine, its shared desktop and its Spaces fit together, see
-[Machines and Spaces](/spaces/concepts/machines-and-spaces).
+For how a computer, its shared desktop and its Spaces fit together, see
+[Computers and Spaces](/spaces/concepts/machines-and-spaces).
-The machine has two settings, and each works on its own:
+The computer has two settings, and each works on its own:
| Setting | What it does | Default | `--share spaces` |
|---|---|---|---|
-| Let other machines control this desktop (`--desktop`) | The machine itself is a Space: its screen, input, shell and files. | on | off |
-| Let other machines create Spaces here (`--provide-spaces`) | Your other machines can create, list and delete Spaces on it. | on for a new setup | on |
+| Let other computers control this desktop (`--desktop`) | The computer itself is a Space: its screen, input, shell and files. | on | off |
+| Let other computers create Spaces here (`--provide-spaces`) | Your other computers can create, list and delete Spaces on it. | on for a new setup | on |
-A machine set up before this default keeps what it had: setting it up again
-never turns **Let other machines create Spaces here** on unless you pass `--share spaces` or `--share both`. With
-that switch on, your machines (and teammates you share the machine with
+A computer set up before this default keeps what it had: setting it up again
+never turns **Let other computers create Spaces here** on unless you pass `--share spaces` or `--share both`. With
+that switch on, your computers (and teammates you share the computer with
as editors) can run Spaces and `cua run` jobs on it, at most 4 at once and two
-macOS VMs on a Mac. Nothing runs until a Space is created. When **Let other machines create Spaces here**
+macOS VMs on a Mac. Nothing runs until a Space is created. When **Let other computers create Spaces here**
turns on in the Cua Spaces app, the app asks for macOS Local Network access on
that Mac (click **Allow** when macOS asks), which macOS Spaces your other
-machines create there need. With **Let other machines control this desktop**
+computers create there need. With **Let other computers control this desktop**
off, a relayed caller reaches only the Spaces service. Change either
setting at any time:
@@ -292,8 +292,8 @@ cua host config --max-memory 32 --max-disk 200 # at most 32 GB of memory and
cua host config --max-run-time 480 # a Space made here stops after 8 hours
```
-The app's **This machine** page has the same two switches, the Spaces the
-machine provides, and every remote create and delete.
+The app's **This computer** page has the same two switches, the Spaces the
+computer provides, and every remote create and delete.
### Over ssh or Tailscale
@@ -321,7 +321,7 @@ cua host setup --remote --share spaces --name "Mac mini (spare)"
```
If the mini has no saved account session, this prints a URL and a short code
-that you approve in a browser on another machine. The sign-in is held only for
+that you approve in a browser on another computer. The sign-in is held only for
setup. An existing account session is reused.
<Callout type="warn">
@@ -340,7 +340,7 @@ setup. An existing account session is reused.
seconds and says so. Allow it once from the SSH session instead (Apple
documents this in [TN3179](https://developer.apple.com/documentation/technotes/tn3179-understanding-local-network-privacy),
macOS 15.5 and later). It lets every app on that Mac reach its virtual
- machines, and it needs a restart:
+ computers, and it needs a restart:
```sh skip="no-runner"
sudo defaults write com.apple.network.local-network AllowedEthernetLocalNetworkAddresses -array 192.168.64.0/24
@@ -351,7 +351,7 @@ setup. An existing account session is reused.
### Create Spaces on it from your laptop
-Your laptop must be [added to your account](#reach-it-from-your-other-machines). Then ask your coding agent, through the cua MCP server:
+Your laptop must be [added to your account](#reach-it-from-your-other-computers). Then ask your coding agent, through the cua MCP server:
> spin up 2 macos spaces on my spare mac mini
@@ -365,12 +365,12 @@ cua spaces create linux --on host:0123abcd4567ef89
The SDK takes the same `on`: `spaces.create(on="host:spare mac mini", image="macos")`.
-The machine is matched by its ID, its exact name, or the words of its name, so
+The computer is matched by its ID, its exact name, or the words of its name, so
"spare mac mini" finds `Mac mini (spare)` or `office-mac-mini`. When two
-machines fit equally well, the call fails with `ambiguous_host` and lists them
+computers fit equally well, the call fails with `ambiguous_host` and lists them
with their IDs, so the agent can ask you which one you meant.
-Each new Space joins the relay as a machine of its own and comes back as
+Each new Space joins the relay as a computer of its own and comes back as
`relay:<machine>`. Open it, stream it and run commands in it like any other
Space.
@@ -381,9 +381,9 @@ cua spaces ls
cua spaces delete relay:space-0123456789abcdef
```
-`cua spaces ls` (and the app's sidebar) groups the Spaces a machine provides
-under that machine. In `list_spaces` each one carries `host` (the machine's ID)
-and `host_name`. Deleting asks the machine to delete the VM or container, and
+`cua spaces ls` (and the app's sidebar) groups the Spaces a computer provides
+under that computer. In `list_spaces` each one carries `host` (the computer's ID)
+and `host_name`. Deleting asks the computer to delete the VM or container, and
the Space leaves the relay.
### Limits
@@ -392,15 +392,15 @@ the Space leaves the relay.
|---|---|---|
| macOS VMs on one Mac | 2 | Apple's macOS license allows two macOS VMs per Mac, and Apple Virtualization (which Lume runs on) enforces it. |
| Spaces at once | 4 | Set with `cua host config --max-spaces N` (0: no limit). |
-| Memory in total | none | The most memory the Spaces other machines create here may use together. Set with `cua host config --max-memory GB`. |
+| Memory in total | none | The most memory the Spaces other computers create here may use together. Set with `cua host config --max-memory GB`. |
| Disk in total | none | The most disk those Spaces may use together. Set with `cua host config --max-disk GB`. |
-| Running time | none | A Space made here by another machine stops after this many minutes (`cua host config --max-run-time MINUTES`); starting it again brings it back. |
+| Running time | none | A Space made here by another computer stops after this many minutes (`cua host config --max-run-time MINUTES`); starting it again brings it back. |
-The limits count only the Spaces other machines create on this machine, not the
-ones you make here yourself. They apply to everyone who asks: another machine, an
+The limits count only the Spaces other computers create on this computer, not the
+ones you make here yourself. They apply to everyone who asks: another computer, an
agent, or a Space that overflows from a tree of Spaces. A create past a limit is
-refused with "&lt;machine&gt; has no room for another Space", and `on="auto"` picks
-another machine or your linked cloud instead. Lowering a limit never stops a Space
+refused with "&lt;computer&gt; has no room for another Space", and `on="auto"` picks
+another computer or your linked cloud instead. Lowering a limit never stops a Space
that is running: it only refuses new ones, and Settings shows "Over limit" until
use drops below it. The same numbers are in **Settings**, under **Sharing**.
@@ -415,29 +415,29 @@ next ones. The host's cua-spacesd starts the cua daemon when a request comes in.
### Who can create Spaces on it
-- You, from any machine added to your account.
-- Accounts you share the machine with as editors (`cua host share` or
+- You, from any computer added to your account.
+- Accounts you share the computer with as editors (`cua host share` or
`cua spaces share relay:<machine> <who> --role editor`). They see and delete
only the Spaces they created. You see and delete all of them.
-- Nobody else. The relay refuses a machine that is not added to the account, and the machine
+- Nobody else. The relay refuses a computer that is not added to the account, and the computer
refuses an account shared as a viewer.
-Every remote create, delete and refusal is a line in the machine's hash-chained
+Every remote create, delete and refusal is a line in the computer's hash-chained
audit log (`~/.cua/host/spaces-audit.jsonl`). `cua host status` and the app show
it, and warn when the log does not verify.
-Agents follow [per-agent machine access](/spaces/guides/agent-memory-and-identity#access-to-your-machines): a
+Agents follow [per-agent computer access](/spaces/guides/agent-memory-and-identity#access-to-your-computers): a
persistent agent uses a Space on your spare Mac only after you allow it, and a
-grant on the machine does not reach the Spaces it provides.
+grant on the computer does not reach the Spaces it provides.
```bash test="cli-shape" id="cua-agent-allow-host-space"
cua agent allow-computer ada relay:space-0123456789abcdef
```
-### Use all your machines [#use-all-your-computers]
+### Use all your computers [#use-all-your-computers]
-Every machine signed in to your account that provides Spaces is part of one
-pool. There is nothing else to set up: sign in on each machine (the app, or
+Every computer signed in to your account that provides Spaces is part of one
+pool. There is nothing else to set up: sign in on each computer (the app, or
`cua auth login` and `cua host setup --share spaces`), then ask for `auto`:
```bash test="cli-shape" id="cua-spaces-create-auto"
@@ -446,33 +446,33 @@ cua sb run --on auto --count 200 -- sh -c 'echo hello from $(hostname)'
```
- `--on auto` (`on="auto"` in the SDK and MCP tools, **Auto** in the app's
- **Run on** menu) picks the least-loaded machine that can take the Space:
- this one, or one of your machines (or one shared with you as an editor)
+ **Run on** menu) picks the least-loaded computer that can take the Space:
+ this one, or one of your computers (or one shared with you as an editor)
that provides Spaces. Modal takes it only when you
[connected Modal](/cua-sdk/guides/your-cloud) and no
- machine has room. Without `on`, a Space or run stays on this machine.
-- A machine takes a Space while its CPU and memory are not all **reserved**
+ computer has room. Without `on`, a Space or run stays on this computer.
+- A computer takes a Space while its CPU and memory are not all **reserved**
by the Spaces on it. Other programs keeping its CPUs busy never refuse
- one: they only make the machine rank lower than an idle one. When every
- machine that matches is full, the create fails with a capacity error
+ one: they only make the computer rank lower than an idle one. When every
+ computer that matches is full, the create fails with a capacity error
(`HostCapacity` in the SDK, exit code 8 in `cua`) that says what is
reserved, not "not found". Delete a Space, ask for less (`--cpus`,
- `--memory`), or add a machine.
+ `--memory`), or add a computer.
- `cua sb run` runs a command in a new Space `--count` times, each deleted
afterwards. `cua sb runs` shows the runs and their jobs.
-- A run on your machines keeps going when your laptop sleeps: one of your
- machines that provides Spaces coordinates it, chosen through your
+- A run on your computers keeps going when your laptop sleeps: one of your
+ computers that provides Spaces coordinates it, chosen through your
account, and another one takes over if it goes away.
-- `cua spaces ls` and the app's sidebar show how loaded each machine is.
- To stop new work going to a machine, turn **Let other machines create Spaces here** off on it
+- `cua spaces ls` and the app's sidebar show how loaded each computer is.
+ To stop new work going to a computer, turn **Let other computers create Spaces here** off on it
(`cua host config --provide-spaces off`); turn it on again to resume. Work
- it had runs again on another machine.
+ it had runs again on another computer.
-#### Keep a Space on your machines
+#### Keep a Space on your computers
-A Space you want to outlive any one machine (an agent's long-running home, a
-build machine) is created **durable**: when its machine goes away (powered
-off, crashed, taken offline) it is created again on another of your machines
+A Space you want to outlive any one computer (an agent's long-running home, a
+build computer) is created **durable**: when its computer goes away (powered
+off, crashed, taken offline) it is created again on another of your computers
that provides Spaces, with the same name.
```bash test="cli-shape" id="cua-spaces-create-durable"
@@ -485,45 +485,45 @@ cua spaces delete research --force
SDK, `durable: true` in the `create_space` MCP tool). Without `--name` it
gets a generated one.
- `cua spaces ls` (and `list_spaces`, with `durable` set to its name) shows
- it like any Space, marked `(durable)`, under the machine it runs on now.
+ it like any Space, marked `(durable)`, under the computer it runs on now.
Use it by its name (`space="research"` in the SDK and MCP tools): the name
finds it wherever it is.
- When it moves it starts fresh: the new copy is a new Space of the same
image and size, not a copy of the old one's disk. Keep what must survive in
[Cua Volume](/spaces/guides/cua-volume) or your own storage.
- `cua spaces delete research` deletes it for good; deleting only the copy on
- one machine would have it created again.
+ one computer would have it created again.
#### What is guaranteed
-- **Each job has one result.** A job may run twice (a machine was cut off
+- **Each job has one result.** A job may run twice (a computer was cut off
and its job ran again elsewhere), but only one result is recorded and
shown. Make jobs safe to repeat.
-- **No job is lost** while one of your machines that can coordinate and one
+- **No job is lost** while one of your computers that can coordinate and one
that can run it are up: a job either ends with its result or says why it
could not run.
- **One coordinator at a time.** The relay hands out the coordinator's
lease with a number that only grows and refuses writes under an old
- number, so a machine that slept or lost its network cannot overwrite the
+ number, so a computer that slept or lost its network cannot overwrite the
current one, whatever its clock says.
-- **Only your machines.** Work goes only to machines you own or that were
- shared with you as an editor, that have **Let other machines create Spaces here** on, and each
- machine checks this itself. Every placement is recorded.
+- **Only your computers.** Work goes only to computers you own or that were
+ shared with you as an editor, that have **Let other computers create Spaces here** on, and each
+ computer checks this itself. Every placement is recorded.
Execution is at least once; results are exactly once. How it works, and how
it was checked (a model checker, simulation of the real code, and fault
-injection on real machines), is in the
+injection on real computers), is in the
[design](https://github.com/trycua/cua/blob/main/docs/rfcs/pool-self-coordination.md).
<Callout>
The relay keeps the pool's job log, but only sealed: each job's command,
-environment, input, output and result are encrypted on your machines with
-keys only your account's added machines hold, and the relay stores and
+environment, input, output and result are encrypted on your computers with
+keys only your account's added computers hold, and the relay stores and
forwards ciphertext. It reads only what it needs to keep one coordinator and
-one result per job: job ids, the kind of each change, which machine an
-attempt went to, and sizes. A machine you revoke cannot read anything written
-after it left. Details are in [What the relay can see](/spaces/guides/relay-security#runs-on-all-your-machines).
-Machines added only by address (no relay) are pooled by the machine you run
+one result per job: job ids, the kind of each change, which computer an
+attempt went to, and sizes. A computer you revoke cannot read anything written
+after it left. Details are in [What the relay can see](/spaces/guides/relay-security#runs-on-all-your-computers).
+Computers added only by address (no relay) are pooled by the computer you run
from, and their runs pause while it sleeps.
</Callout>
@@ -531,7 +531,7 @@ from, and their runs pause while it sleeps.
A spare Mac your laptop reaches by its [Tailscale](https://tailscale.com) (or
LAN) address can host Spaces without the cua.ai relay: no sign-in on either
-machine and no added machines.
+computer and no added computers.
With `--tailnet`, your tailnet (Tailscale or Headscale) also identifies who
calls, so you and the teammates you `--allow` need no token: see
@@ -565,7 +565,7 @@ The laptop keeps the token in its Spaces credential store
cua spaces create macos:26 --on "spare mac mini" --count 2
```
-`on="host:<name>"` looks at your machines on the relay first, then at the hosts
+`on="host:<name>"` looks at your computers on the relay first, then at the hosts
you added with `--host`, with the same matching rules. Each new Space runs on the
Mac with the same limits (four Spaces, two macOS VMs). It is not put on the
relay: the Mac forwards a port on its own address to the Space's cua-spacesd, and
@@ -577,7 +577,7 @@ restarts, the Mac opens the same port again.
<Callout type="warn">
The direct listener is plain HTTP, and the Mac's token is its owner: it creates
and deletes Spaces there and reaches the Mac's own shell and files, even with
- **Let other machines control this desktop** off. Treat it like an SSH key and use it only over
+ **Let other computers control this desktop** off. Treat it like an SSH key and use it only over
Tailscale or a LAN you trust. By default the Mac takes host calls, and
connections to the Spaces it forwards, only from loopback, Tailscale
(`100.64.0.0/10`, `fd7a:115c:a1e0::/48`) and private LAN addresses
@@ -592,23 +592,23 @@ restarts, the Mac opens the same port again.
| Error | Meaning | Fix |
|---|---|---|
-| `ambiguous_host` | Several of your machines fit the name. | Pick one of the listed IDs: `on="host:<id>"`. |
-| `not_found` | No machine fits the name. | Check `cua spaces ls`, or set the machine up with `--share spaces` or `--share both`. |
-| `host_capability_missing` | The machine is offline, does not provide Spaces, or cannot run that OS. | Run `cua host config --provide-spaces on` on it, or pick another machine. |
-| `limit_exceeded` | Two macOS VMs already run, or the machine is at one of its limits (Spaces, memory or disk). | Delete one with `cua spaces delete`, or raise the limit with `cua host config`. |
-| `permission_denied` | The machine is shared with you to watch only. | Ask its owner to share it as an editor. |
+| `ambiguous_host` | Several of your computers fit the name. | Pick one of the listed IDs: `on="host:<id>"`. |
+| `not_found` | No computer fits the name. | Check `cua spaces ls`, or set the computer up with `--share spaces` or `--share both`. |
+| `host_capability_missing` | The computer is offline, does not provide Spaces, or cannot run that OS. | Run `cua host config --provide-spaces on` on it, or pick another computer. |
+| `limit_exceeded` | Two macOS VMs already run, or the computer is at one of its limits (Spaces, memory or disk). | Delete one with `cua spaces delete`, or raise the limit with `cua host config`. |
+| `permission_denied` | The computer is shared with you to watch only. | Ask its owner to share it as an editor. |
## If it doesn't work
| What you see | What to do |
|---|---|
-| "That code didn't work" | A code works once and expires. Open **Add a machine** again for a new one. |
-| "This Mac can't make codes yet." | This machine isn't trusted yet. Choose **Trust this machine** on its page in **Machines**, or use **Sign in there**. |
-| The machine never appears | On that machine, run `cua host status`. It shows the service state and any missing permission. |
-| The machine shows **Offline** | It is off, asleep or disconnected. Wake it or reconnect it, then run `cua host status` on it. |
+| "That code didn't work" | A code works once and expires. Open **Add a computer** again for a new one. |
+| "This Mac can't make codes yet." | This computer isn't trusted yet. Choose **Trust this computer** on its page in **Computers**, or use **Sign in there**. |
+| The computer never appears | On that computer, run `cua host status`. It shows the service state and any missing permission. |
+| The computer shows **Offline** | It is off, asleep or disconnected. Wake it or reconnect it, then run `cua host status` on it. |
## Next
-- [Connect your agent](/spaces/guides/connect-your-agent): let an agent use the new machine.
+- [Connect your agent](/spaces/guides/connect-your-agent): let an agent use the new computer.
- [Create a Space](/spaces/guides/add-a-space): run a Space on it.
-- [Plans and Teams](/spaces/guides/teams): share machines with your team.
+- [Plans and Teams](/spaces/guides/teams): share computers with your team.
diff --git a/docs/content/docs/spaces/guides/add-a-space.mdx b/docs/content/docs/spaces/guides/add-a-space.mdx
index 071e9f534f..6730a4e960 100644
--- a/docs/content/docs/spaces/guides/add-a-space.mdx
+++ b/docs/content/docs/spaces/guides/add-a-space.mdx
@@ -1,15 +1,15 @@
---
title: Create a Space
-description: 'Create a Space on a machine you own from the app, the CLI or code: any image, progress, cancel, GPUs, adding an existing machine by address, then list, delete or remove it.'
+description: 'Create a Space on a computer you own from the app, the CLI or code: any image, progress, cancel, GPUs, adding an existing computer by address, then list, delete or remove it.'
---
import { Callout } from 'fumadocs-ui/components/callout';
import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
-A Space is one desktop on one of your machines. Ids are the sandbox refs
+A Space is one desktop on one of your computers. Ids are the sandbox refs
`cua sb ls` prints (`local:<name>`, `aws:<name>`, `direct:<host:port>`,
`relay:<machine-id>`); a bare name works when it matches one Space. To connect a
-whole machine first, see [Add a machine](/spaces/guides/add-a-computer).
+whole computer first, see [Add a computer](/spaces/guides/add-a-computer).
## Create a Space in the app
@@ -24,9 +24,9 @@ microVM) and the runtime. See [Space kinds](/spaces/concepts/space-kinds).
If the create fails, see [Troubleshoot](/spaces/guides/troubleshoot).
-## Add an existing machine by address
+## Add an existing computer by address
-Choose **Connect by address** in New Space, or register a machine from code.
+Choose **Connect by address** in New Space, or register a computer from code.
This example starts the canonical Linux image with a token:
```bash skip="no-runner"
@@ -127,8 +127,8 @@ result = await space.call_tool("add", '{"a": 2, "b": 3}', "mcp", None)
| Lifecycle, declared services, tunnels, public URLs, `list_tools` / `call_tool` with `service` | `bash`, files, streaming, presence, teleport, agent runs, the `driver` tool registry |
Spacesd features on an image without it fail with `CapabilityMissing`. The
-canonical images and machines set up with `cua host setup` run cua-spacesd, and
-so does any OCI image you create on this machine as a container or microVM
+canonical images and computers set up with `cua host setup` run cua-spacesd, and
+so does any OCI image you create on this computer as a container or microVM
(`alpine:3.20`, `node:20`): a static cua-spacesd is put into it and runs
beside the image's own command.
@@ -189,7 +189,7 @@ Sandboxes: `await sandboxes.cancel_create(name)` returns what was removed, or
| Removed | Kept |
|---|---|
-| The VM or container and its disks, the cloud claim, the relay machine, the registry entry, the create's journal | Anything that existed before the create |
+| The VM or container and its disks, the cloud claim, the relay computer, the registry entry, the create's journal | Anything that existed before the create |
| Partial downloads | Finished image layers in the engine's cache (Docker's; Lume's when its cache is on), so the next create resumes |
A Lume without `POST /lume/pull/cancel` cannot stop a pull: the create still
@@ -229,7 +229,7 @@ if cua set it. Metal apps in the guest may still need the per-workload shim:
cua spaces ls
```
-Lists registered Spaces and, when you are signed in, your machines on the
+Lists registered Spaces and, when you are signed in, your computers on the
relay (`relay:<machine-id>`, no `add` needed). Register or forget one from a
shell:
@@ -241,7 +241,7 @@ cua spaces rm studio
A [Tailscale](https://tailscale.com) address works here too (its IP or
MagicDNS name as the host:port): `cua spaces add` reaches it like any other
address and the Space registers as `direct:<addr>`. That only attaches one
-already-running Space. To host Spaces for `on="host:<name>"`, set the machine up
+already-running Space. To host Spaces for `on="host:<name>"`, set the computer up
with [`cua host setup`](/spaces/guides/add-a-computer#use-a-spare-mac-to-host-spaces).
`spaces.delete(id)` deletes a Space's sandbox and forgets it (a Space added by
diff --git a/docs/content/docs/spaces/guides/agent-memory-and-identity.mdx b/docs/content/docs/spaces/guides/agent-memory-and-identity.mdx
index 5239614fd0..ae2d8c7e83 100644
--- a/docs/content/docs/spaces/guides/agent-memory-and-identity.mdx
+++ b/docs/content/docs/spaces/guides/agent-memory-and-identity.mdx
@@ -1,6 +1,6 @@
---
title: Memory and identity
-description: 'A named agent keeps its memory in a home in the Cua Volume that outlives its runs and its Space, and gets its own notifications, pause and resume, and access to your machines by name.'
+description: 'A named agent keeps its memory in a home in the Cua Volume that outlives its runs and its Space, and gets its own notifications, pause and resume, and access to your computers by name.'
---
import { Callout } from 'fumadocs-ui/components/callout';
@@ -8,7 +8,7 @@ import { Callout } from 'fumadocs-ui/components/callout';
An agent you add with a name has three things: a harness, a Space to work in,
and a home in the [Cua Volume](/spaces/guides/cua-volume) at `agents/<name>/`.
The harness keeps its memory in that home, so the agent remembers across runs,
-across its Space being deleted and created again, and across machines.
+across its Space being deleted and created again, and across computers.
```bash test="cli-shape" id="memory-add"
cua agent add ada --harness hermes --in local:dev --env-from-host OPENAI_API_KEY
@@ -16,8 +16,8 @@ cua agent send ada "What did you learn yesterday?"
```
The name is the agent's identity everywhere: in the Cua Volume (`agent:ada`),
-in notifications, in machine-access grants and in the audit log. Named agents
-are kept by the Cua daemon of the machine you add them on.
+in notifications, in computer-access grants and in the audit log. Named agents
+are kept by the Cua daemon of the computer you add them on.
## How it works
@@ -77,7 +77,7 @@ firing.
|-------|-------|--------|
| Local | Suspends the Space. | Resumes it. |
| In your own cloud | Releases the Space after the home is saved. | Creates it again from the same image and restores the home. |
-| Your own machine or an added address | Only the agent pauses. | Only the agent resumes. |
+| Your own computer or an added address | Only the agent pauses. | Only the agent resumes. |
## What the agent gets
@@ -89,15 +89,15 @@ over the Space's own connection (no token enters the Space).
| `notify_user` | A notification in the Cua app. |
| `volume_ls`, `volume_read`, `volume_write` | The Cua Volume, as `agent:<name>`: its home, `public/` (read) and its Space's folder. |
| `volume_request_access` | Asks you for more; you approve in the app. |
-| `computer_list`, `computer_list_tools`, `computer_call` | Your machines you allowed this agent to use. |
+| `computer_list`, `computer_list_tools`, `computer_call` | Your computers you allowed this agent to use. |
| `request_site_login` | [Sign in to a site](/spaces/guides/keyvault#let-an-agent-sign-in-to-a-site) with a password from your Keyvault, after you approve. The agent never sees it. |
It also has the Space's own Cua Driver tools, like every agent run; see
[Computer use](/spaces/guides/agents-in-a-space#computer-use).
-## Access to your machines
+## Access to your computers
-`cua host setup` makes a machine a Space for your whole account. A named agent
+`cua host setup` makes a computer a Space for your whole account. A named agent
reaches it only if you allow that agent by name. Allowing asks for Touch ID or
your passphrase; revoking takes effect on the agent's next call; every grant,
use and refusal is audited.
@@ -117,7 +117,7 @@ cua agent revoke-computer ada
| Page | What it shows |
|------|---------------|
-| Agents | Each named agent on one line with Pause or Resume; the selected agent's Memory (its home, each file's text and history, Restore), Routines (add, on or off, remove) and Access to this machine (allow, revoke, recent uses and refusals). |
+| Agents | Each named agent on one line with Pause or Resume; the selected agent's Memory (its home, each file's text and history, Restore), Routines (add, on or off, remove) and Access to this computer (allow, revoke, recent uses and refusals). |
| Drive | The Cua Volume by folder, access requests from agents (Approve asks for Touch ID, Deny) and grants (Revoke). |
| Notifications | The daemon's feed, newest first, with Mark all read. New entries are posted as system notifications once each, while the app runs. |
diff --git a/docs/content/docs/spaces/guides/agent-schedules.mdx b/docs/content/docs/spaces/guides/agent-schedules.mdx
index f3dff72fff..73f945b1b0 100644
--- a/docs/content/docs/spaces/guides/agent-schedules.mdx
+++ b/docs/content/docs/spaces/guides/agent-schedules.mdx
@@ -37,7 +37,7 @@ last one did. Without a name it lists every agent's.
- A schedule never interrupts a turn. If the agent is busy or paused, that slot
is skipped.
-- If the daemon was asleep (your machine was off), a missed schedule fires
+- If the daemon was asleep (your computer was off), a missed schedule fires
once when it wakes, not once per missed slot.
- Each firing is a turn like any other: the agent's memory is restored first,
its home is saved after, and you get a notification when it ends.
diff --git a/docs/content/docs/spaces/guides/agents-from-a-link.mdx b/docs/content/docs/spaces/guides/agents-from-a-link.mdx
index 7fa8c6b09e..c49786c074 100644
--- a/docs/content/docs/spaces/guides/agents-from-a-link.mdx
+++ b/docs/content/docs/spaces/guides/agents-from-a-link.mdx
@@ -1,10 +1,10 @@
---
title: Connect an agent from a link
-description: 'Give an AI agent on any of your machines a one-line link that joins a Cua Space, add or connect things for you, and what it can and cannot do once it is in.'
+description: 'Give an AI agent on any of your computers a one-line link that joins a Cua Space, add or connect things for you, and what it can and cannot do once it is in.'
---
Cua Spaces gives you a one-line prompt for each job you want an agent to do:
-join a Space, add a machine, connect a cloud, set up S3 storage for Cua Volume.
+join a Space, add a computer, connect a cloud, set up S3 storage for Cua Volume.
Each prompt is one sentence and one link. Paste the whole line into your agent.
The link opens a short page of instructions written for the agent, the same for
everyone, and it never says anything about your Spaces.
@@ -16,28 +16,28 @@ In a Space, choose **Add an agent**, then copy the line. It looks like
once, for one Space, and expires in an hour by default. Using it needs your Cua
sign-in, so a leaked line alone gets nobody anywhere.
-The agent runs `cua join <code>` on your machine, picks a name and an icon, and
+The agent runs `cua join <code>` on your computer, picks a name and an icon, and
joins the thread as its own member with its owner shown next to it. It takes
tasks from the thread and answers there. For later sessions it can add Cua's tools
to its harness, so it doesn't need the link again.
What it gets: the Space's thread, its files and its members, and a key for this
-Space only, kept in your keychain and bound to this machine. It does not get the
+Space only, kept in your keychain and bound to this computer. It does not get the
desktop, other Spaces, Volume or Keyvault. Remove it from the Space, or remove the
-machine from your account, and its key stops at once.
+computer from your account, and its key stops at once.
-An agent that runs in the cloud and has no shell on your machine can't join yet.
-It tells you so, and you paste the line into an agent on your machine instead.
+An agent that runs in the cloud and has no shell on your computer can't join yet.
+It tells you so, and you paste the line into an agent on your computer instead.
## The other prompts
The pages for agents, which each agent reads from its prompt, are also
useful to read yourself:
-- [Add a machine](/agents/add-a-computer)
+- [Add a computer](/agents/add-a-computer)
- [Connect a cloud](/agents/connect-a-cloud)
- [Set up S3 storage for Cua Volume](/agents/volume-s3)
-- [Add a machine](/agents/add-a-machine)
+- [Add a computer](/agents/add-a-machine)
Agents ask before they act on anything that costs money or touches your cloud, and
never need your keys pasted into a chat.
diff --git a/docs/content/docs/spaces/guides/agents-in-a-space.mdx b/docs/content/docs/spaces/guides/agents-in-a-space.mdx
index 4f01ff0446..00d39c488a 100644
--- a/docs/content/docs/spaces/guides/agents-in-a-space.mdx
+++ b/docs/content/docs/spaces/guides/agents-in-a-space.mdx
@@ -5,10 +5,10 @@ description: 'Add a coding or computer-use agent to a Space, message it, and che
import { Tabs, Tab } from 'fumadocs-ui/components/tabs';
-An agent in a Space works on a machine of its own instead of on This Mac. You
+An agent in a Space works on a computer of its own instead of on This Mac. You
add it once, give it work, and come back later to read what it did. The Space
is the boundary: the agent approves its own tool calls inside it, and nothing
-it does reaches your machine unless you allow it.
+it does reaches your computer unless you allow it.
There are three ways to run one:
@@ -16,7 +16,7 @@ There are three ways to run one:
|---|---|
| An agent with a name that remembers across runs and can work on a schedule | `cua agent add NAME` |
| One task, then stop | `cua agent add NAME --once` |
-| A task that must survive a crash of the process or the machine driving it | `cua agent add NAME --durable` |
+| A task that must survive a crash of the process or the computer driving it | `cua agent add NAME --durable` |
A named agent keeps its memory in the [Cua Volume](/spaces/guides/cua-volume)
(see [Memory and identity](/spaces/guides/agent-memory-and-identity)) and can
@@ -62,9 +62,9 @@ re-driven after a crash (see
</Tab>
</Tabs>
-Named agents are kept by the Cua daemon on This Mac (or on the machine whose
+Named agents are kept by the Cua daemon on This Mac (or on the computer whose
daemon you use), and their Space can be any Space you can reach: a local one,
-one on a [machine you added](/spaces/guides/add-a-computer), or one in your own
+one on a [computer you added](/spaces/guides/add-a-computer), or one in your own
cloud.
## Message it
@@ -90,7 +90,7 @@ message. On a narrow window the Reply button is always visible.
After you talk to an agent, a small chip with its name and an X sits in the
box, and the next message goes to it until you @ someone else or press the X.
Cua Spaces adds the `@name` when you send, and says so quietly the first time.
-Which agent is kept for each Space on your machine, so it is still there after
+Which agent is kept for each Space on your computer, so it is still there after
a reload.
When you have not said who, the message goes to the one agent in the Space, or
@@ -132,15 +132,15 @@ cua agent notifications --unread
`cua agent ls` with no Space lists your named agents; with a Space it lists the
runs in it, including one-off tasks.
-## From another machine or person
+## From another computer or person
-A Space's thread and its agents live on the machine that provides the Space.
-When that machine is shared with you, directly or through a
+A Space's thread and its agents live on the computer that provides the Space.
+When that computer is shared with you, directly or through a
[team](/spaces/guides/teams), you read and post in the thread of each Space it
-provides from your own machine, and @mention its agents there, with the same
-tools as on that machine. When only a Space is shared with you, you reach that
-Space's thread the same way, and nothing else of the machine that provides it.
-Your role is the one the Space was shared with, and stopping the share ends it. Cua sends each call to that machine's daemon
+provides from your own computer, and @mention its agents there, with the same
+tools as on that computer. When only a Space is shared with you, you reach that
+Space's thread the same way, and nothing else of the computer that provides it.
+Your role is the one the Space was shared with, and stopping the share ends it. Cua sends each call to that computer's daemon
through the relay, signed in as you: what you post shows your name, and the
owner's roles and each agent's rights decide what you can do. Shared with you
to view, you can read the thread and see the agents, but you cannot post,
@@ -152,7 +152,7 @@ thread_read {space: "relay:space-7f2c41d0", after: 41, follow_ms: 20000}
```
`follow_ms` waits up to 25 seconds for new entries, so a client can follow the
-thread. The thread can be reached while that machine is online. If it runs an
+thread. The thread can be reached while that computer is online. If it runs an
older Cua, the answer says to update Cua on it.
## Coding agents
@@ -176,7 +176,7 @@ A harness needs a provider key. Save it once in **Cua Spaces, Settings,
Agents** (or `cua agent keys set`), and each run gets the keys its harness
reads, written 0600 inside the run and redacted from its log; see
[Agent keys](/spaces/guides/connect-your-agent#agent-keys). Credential files on
-your machine are never copied into a Space. The one exception is Claude Code's
+your computer are never copied into a Space. The one exception is Claude Code's
own sign-in, which you choose to import: Cua reads it once you agree and gives
Claude Code runs the access token only, never the refresh token (see
[Claude Code and your Claude plan](/spaces/guides/connect-your-agent#claude-code-and-your-claude-plan)).
diff --git a/docs/content/docs/spaces/guides/bring-your-own-compute.mdx b/docs/content/docs/spaces/guides/bring-your-own-compute.mdx
index f401938f41..01c87ccaee 100644
--- a/docs/content/docs/spaces/guides/bring-your-own-compute.mdx
+++ b/docs/content/docs/spaces/guides/bring-your-own-compute.mdx
@@ -1,12 +1,12 @@
---
title: Bring your own compute
-description: 'Run Cua Spaces on machines you already have: this Mac, a Mac mini, a Linux box or VPS, or a VM in your own cloud account. Cua does not rent you a machine.'
+description: 'Run Cua Spaces on computers you already have: this Mac, a Mac mini, a Linux box or VPS, or a VM in your own cloud account. Cua does not rent you a computer.'
---
import { Callout } from 'fumadocs-ui/components/callout';
-Cua Spaces runs on hardware you bring. You don't rent a machine from Cua. You
-add one you already have, and your agents and your other machines use it from
+Cua Spaces runs on hardware you bring. You don't rent a computer from Cua. You
+add one you already have, and your agents and your other computers use it from
there. This page shows four ways to do that. Pick the one that matches what you
have.
@@ -14,21 +14,21 @@ have.
|---|---|
| The Mac you are using now | [This Mac](#this-mac) |
| A Mac mini or another Mac you don't sit at | [A Mac mini](#a-mac-mini) |
-| A Linux machine, or a VPS you rent somewhere | [A Linux box or VPS](#a-linux-box-or-vps) |
+| A Linux computer, or a VPS you rent somewhere | [A Linux box or VPS](#a-linux-box-or-vps) |
| A VM in your own cloud account | [A VM in your cloud account](#a-vm-in-your-cloud-account) |
-Every route ends the same way. The machine shows up in **Machines** in the
-app and in `cua spaces ls`. Nothing connects inward to it: the machine calls
+Every route ends the same way. The computer shows up in **Computers** in the
+app and in `cua spaces ls`. Nothing connects inward to it: the computer calls
out to the cua.ai relay, so you don't open ports or set up a VPN.
## This Mac
-The quickest start. Your Mac becomes your first machine.
+The quickest start. Your Mac becomes your first computer.
1. Install Cua Spaces and sign in. [Install](/spaces/guides/install) has the
steps, and the [quickstart](/spaces/quickstart) walks through the first run.
-2. Open **This machine**, choose how to use it, and press **Set up for
- access**. Your other machines can now reach this Mac.
+2. Open **This computer**, choose how to use it, and press **Set up for
+ access**. Your other computers can now reach this Mac.
Prefer a terminal? Run:
@@ -43,7 +43,7 @@ System Settings, Privacy & Security, and turn both on.
## A Mac mini
A Mac mini in a closet is a good place to run Spaces for your laptop and your
-agents. Set it up as a spare machine: it runs Spaces for you, and its own
+agents. Set it up as a spare computer: it runs Spaces for you, and its own
desktop and files stay private.
On the mini, in Terminal:
@@ -54,7 +54,7 @@ cua host setup --share spaces --name "Mac mini"
If you only reach the mini over ssh, install without a screen and sign in with
a code instead. The first command installs. The second prints a web address and
-a short code. Open the address on any other machine and enter the code.
+a short code. Open the address on any other computer and enter the code.
```bash skip="no-runner"
curl -fsSL https://cua.ai/install.sh | sh -s -- -y --select spaces,host --no-onboarding
@@ -80,19 +80,19 @@ cua spaces create macos:26 --on "mac mini" --count 2
Spaces on a Mac need an Apple silicon Mac. One Mac runs at most two macOS
Spaces at once, because that is Apple's license limit. [Add a
-machine](/spaces/guides/add-a-computer#use-a-spare-mac-to-host-spaces) has the
+computer](/spaces/guides/add-a-computer#use-a-spare-mac-to-host-spaces) has the
rest: limits, Tailscale without the relay and fixes for common errors.
## A Linux box or VPS
-This works for a machine in your office or a small server you rent from any
+This works for a computer in your office or a small server you rent from any
provider. You can do it over ssh, with no screen.
-Before you start, make sure the machine can run Linux Spaces. They run in
+Before you start, make sure the computer can run Linux Spaces. They run in
containers, so **install Docker first**. Spaces on a Linux box are Linux
-Spaces. A Mac or Windows Space needs a Mac or a Windows machine.
+Spaces. A Mac or Windows Space needs a Mac or a Windows computer.
-1. Connect to the machine with ssh.
+1. Connect to the computer with ssh.
2. Install Cua Spaces without questions:
```bash skip="no-runner"
@@ -101,7 +101,7 @@ Spaces. A Mac or Windows Space needs a Mac or a Windows machine.
`-y` accepts the install without the checklist. `--select spaces,host`
picks the Cua Spaces app and hosting. `--no-onboarding` skips the sign-in
- prompt, because the machine has no browser.
+ prompt, because the computer has no browser.
3. Set it up and sign in with a code:
@@ -119,15 +119,15 @@ Spaces. A Mac or Windows Space needs a Mac or a Windows machine.
cua host status
```
-The server now appears in **Machines**. Setup installs it as a background
+The server now appears in **Computers**. Setup installs it as a background
service, so it comes back after a restart.
If the server only runs Spaces and you don't want to share its own desktop,
add `--share spaces` to the setup command.
-Already on the Cua Spaces app? You can skip the code. Open **Machines**, press
-**Add a machine**, and run the install command it shows on the server. See
-[Add a machine](/spaces/guides/add-a-computer#add-a-machine-from-the-app).
+Already on the Cua Spaces app? You can skip the code. Open **Computers**, press
+**Add a computer**, and run the install command it shows on the server. See
+[Add a computer](/spaces/guides/add-a-computer#add-a-computer-from-the-app).
## A VM in your cloud account
@@ -153,9 +153,9 @@ Because the VM is yours, so are its costs. A stopped VM is not reachable and
shows **Offline** in your list. Start it again and it reconnects on its own.
To remove it, run `cua host remove` on the VM, then delete the VM in your cloud
-console. Removing a machine from Cua doesn't delete anything on it.
+console. Removing a computer from Cua doesn't delete anything on it.
-## After you add a machine
+## After you add a computer
- **Create a Space on it.** See [Create a Space](/spaces/guides/add-a-space).
- **Let an agent use it.** See [Connect your agent](/spaces/guides/connect-your-agent).
@@ -164,5 +164,5 @@ console. Removing a machine from Cua doesn't delete anything on it.
`cua host remove` to take it out. See
[Check, pause or remove](/spaces/guides/add-a-computer#check-pause-or-remove).
-If a machine doesn't show up, run `cua host status` on it. It names the
+If a computer doesn't show up, run `cua host status` on it. It names the
problem. [Troubleshoot](/spaces/guides/troubleshoot) covers the rest.
diff --git a/docs/content/docs/spaces/guides/connect-a-cloud.mdx b/docs/content/docs/spaces/guides/connect-a-cloud.mdx
index f952d0d83b..e7588bdf82 100644
--- a/docs/content/docs/spaces/guides/connect-a-cloud.mdx
+++ b/docs/content/docs/spaces/guides/connect-a-cloud.mdx
@@ -1,15 +1,15 @@
---
title: Connect a cloud
-description: Steps an agent follows to link the user's AWS, Google Cloud or Azure account to Cua Spaces with no stored key, or Hetzner and Modal with an API token sealed to their machines, set a budget and a largest machine, and verify it.
+description: Steps an agent follows to link the user's AWS, Google Cloud or Azure account to Cua Spaces with no stored key, or Hetzner and Modal with an API token sealed to their computers, set a budget and a largest computer, and verify it.
---
Link your AWS, Google Cloud or Azure account once, with no stored key, and
-Spaces can run there from every machine and agent on your Cua account. This page is written for
+Spaces can run there from every computer and agent on your Cua account. This page is written for
the coding agent that does it for you. The Cua Spaces app gives you a prompt
like this one to paste into your agent:
> Connect my AWS account to Cua Spaces: region us-west-2, $200 monthly
-> budget, machines up to 4 vCPU and 16 GB. Follow `cua cloud connect aws --help`
+> budget, computers up to 4 vCPU and 16 GB. Follow `cua cloud connect aws --help`
> and https://cua.ai/docs/spaces/guides/connect-a-cloud until `cua cloud status aws`
> says connected.
@@ -41,7 +41,7 @@ The exit code says whose turn it is:
AWS is linked without any key. Cua signs 15-minute tokens for the person's
Cua account, and their AWS account trusts those tokens through one
CloudFormation stack, `cua-spaces`. The stack holds an OIDC provider and a
-role that can create, stop and delete only machines tagged
+role that can create, stop and delete only computers tagged
`cua-managed=true`. It holds no keys, and Cua never stores AWS credentials.
### 1. Ask the person for the limits
@@ -49,9 +49,9 @@ role that can create, stop and delete only machines tagged
Ask for three things, unless the prompt already gave them:
- the region (for example `us-west-2`);
-- a monthly budget in US dollars (required: Cua refuses new machines once it
+- a monthly budget in US dollars (required: Cua refuses new computers once it
is reached, and stopping and deleting always works);
-- the largest machine, as vCPUs and GB (for example 4 vCPU and 16 GB).
+- the largest computer, as vCPUs and GB (for example 4 vCPU and 16 GB).
Then run:
@@ -84,14 +84,14 @@ cua cloud connect aws --oidc --region us-west-2 --budget 200 --max-size 4x16 --a
```
The check gets a check token from Cua, exchanges it with AWS STS and dry-runs
-a machine. Nothing is created, and nothing is billed.
+a computer. Nothing is created, and nothing is billed.
- `connected` (exit code 0): done. Go to step 4.
- `needs-trust` again: the stack is missing, still being created, or was made
in another AWS account. Show the person `next.open` again, and confirm the
account id.
- `waiting-for-approval` (exit code 11): because an agent made the link, a
- person approves it in the Cua Spaces app before machines can be created.
+ person approves it in the Cua Spaces app before computers can be created.
Ask them to approve it.
- `failed`: read `checks` and `next.why`, fix what they say, and run the
check again.
@@ -103,7 +103,7 @@ cua cloud status aws
```
The AWS line says `connected`. The line under it shows the budget, what was
-spent this month, the largest machine, and "Signs in through Cua". Spaces can
+spent this month, the largest computer, and "Signs in through Cua". Spaces can
now go there:
```bash test="cli-shape" id="agents-connect-aws-use"
@@ -133,7 +133,7 @@ shell, and no MCP server offers it.
## What it costs
-Cua estimates what its machines cost from each one's list price and how long
+Cua estimates what its computers cost from each one's list price and how long
it ran. The cloud's own bill is the final word. To see the month so far by
Space, by agent, by day or by cloud:
@@ -146,14 +146,14 @@ cua cloud cost --cloud aws --by day --since 2026-10-01 --format csv
The CSV starts with the header `key,usd,hours,machines`. When a cloud has a
budget, Cua tells the person once each month when its spend passes half the
budget, then 80%, then all of it. The note shows in the Cua Spaces app and in
-`cua cloud audit`. At the full budget, new machines are refused until the
+`cua cloud audit`. At the full budget, new computers are refused until the
next month; stopping and deleting still work.
## Already connected?
A cloud linked before this, through the AWS CLI, gcloud, a Hetzner token or a
Modal profile, keeps working as it is. There is nothing to do after an
-update: the link, its region, its budget, the machines Cua made there and
+update: the link, its region, its budget, the computers Cua made there and
the cleanup of them all carry over. `cua cloud status aws` shows one line
offering the switch:
@@ -161,9 +161,9 @@ offering the switch:
cua cloud connect aws --oidc
```
-The switch keeps the region, budget, largest machine and lifetime the link
+The switch keeps the region, budget, largest computer and lifetime the link
had. The AWS CLI sign-in stays in force until the check passes. Switching to
-a different AWS account is refused while Cua still has machines in the old
+a different AWS account is refused while Cua still has computers in the old
one, so none are left out of reach. Running `cua cloud connect aws` again
without `--oidc`, for example to change the budget, keeps an OIDC link as it
is.
@@ -171,16 +171,16 @@ is.
## Hetzner and Modal
Hetzner and Modal have no OIDC, so they use an API token. Cua seals the
-token to the person's machines: the machine you run on encrypts it with the
-account's pool key, and only machines of the person's Cua account can open
-it. Cua's servers keep only the ciphertext. Any of the person's machines then
+token to the person's computers: the computer you run on encrypts it with the
+account's pool key, and only computers of the person's Cua account can open
+it. Cua's servers keep only the ciphertext. Any of the person's computers then
opens it in memory when it calls the cloud. No tool returns it, not to you
and not to any other agent.
### 1. Ask the person for the limits and the token
Ask for the location (Hetzner: for example `fsn1`), a monthly budget in US
-dollars and the largest machine. Then ask for the token:
+dollars and the largest computer. Then ask for the token:
- Hetzner: a Read & Write API token. In the Hetzner Cloud console, open the
project, then **Security**, **API tokens**, **Generate API token**.
@@ -204,7 +204,7 @@ sealed.
- `connected` (exit code 0): done.
- `waiting-for-approval` (exit code 11): because an agent gave the token, a
- person approves it in the Cua Spaces app first. Machines are refused until
+ person approves it in the Cua Spaces app first. Computers are refused until
then.
- `failed`: read `checks` and `next.why`. A read-only Hetzner token fails the
`permissions` check; ask for a Read & Write one.
@@ -215,45 +215,45 @@ sealed.
cua cloud status hetzner
```
-The line under Hetzner names the machines that can open the token ("can open
-it: ..."). At least one of them must be online for Cua to make machines
+The line under Hetzner names the computers that can open the token ("can open
+it: ..."). At least one of them must be online for Cua to make computers
there while the person is away.
-### On the person's other machines
+### On the person's other computers
-They do not paste the token again. On another machine of the same Cua
+They do not paste the token again. On another computer of the same Cua
account, link the account's sealed token:
```bash test="cli-shape" id="agents-connect-hetzner-other-device"
cua cloud connect hetzner --sealed --region fsn1 --budget 50
```
-### Sealed or kept on this machine
+### Sealed or kept on this computer
-Without `--sealed` or `--no-sealed`, the token is sealed when this machine has
+Without `--sealed` or `--no-sealed`, the token is sealed when this computer has
the account's pool keys (the `cua` of the Cua Spaces app, signed in) and a
budget is given, or when the link is sealed already. Otherwise the Hetzner
-token is kept in this machine's Cua credential store, as in earlier
+token is kept in this computer's Cua credential store, as in earlier
versions.
- `--sealed` insists on sealing. Without a token on standard input, it seals
- the token this machine already has (the saved one, `HCLOUD_TOKEN`, the
+ the token this computer already has (the saved one, `HCLOUD_TOKEN`, the
hcloud CLI's, or for Modal `MODAL_TOKEN_ID` and `MODAL_TOKEN_SECRET` or the
`~/.modal.toml` profile). This is how a link from an earlier version moves
to a sealed token.
-- `--no-sealed` keeps the Hetzner token on this machine only.
+- `--no-sealed` keeps the Hetzner token on this computer only.
### Replace or revoke the token
- Replace it: run the connect command again with the new token on standard
- input. It is sealed and swapped in for every machine.
+ input. It is sealed and swapped in for every computer.
- Revoke it: delete the token in the Hetzner Cloud console (or with
`modal token`), or run `cua cloud disconnect hetzner`, which deletes the
sealed token on Cua's servers.
-When the person removes a machine from their Cua account, the account's pool
-key moves to a new generation. The next machine that uses the token seals it
-again under the new key, so the removed machine cannot open it any more. To be
+When the person removes a computer from their Cua account, the account's pool
+key moves to a new generation. The next computer that uses the token seals it
+again under the new key, so the removed computer cannot open it any more. To be
sure, replace the token as well.
## Google Cloud
@@ -267,7 +267,7 @@ and no key.
### 1. Ask for the limits and the project
Ask for the project id (for example `my-project`), the region, the monthly
-budget and the largest machine. Then run:
+budget and the largest computer. Then run:
```bash test="cli-shape" id="agents-connect-gcp-start"
cua cloud connect gcp --oidc --project my-project --region us-central1 --budget 200 --max-size 4x16
@@ -286,7 +286,7 @@ The status is `needs-trust`. Send the person `next.open` and `next.paste`:
- They reply with the project number the script prints (it is also on the
project's dashboard).
-When you run on a machine that is signed in to `gcloud` with rights to manage
+When you run on a computer that is signed in to `gcloud` with rights to manage
IAM in the project, `next.run` is the same script instead
(`cua cloud trust gcp | bash -s -- …`), and the exit code is 10. Run it only
when the person asked you to set up the trust.
@@ -322,7 +322,7 @@ you say otherwise). Everything Cua creates stays in that group.
### 1. Ask for the limits
Ask for the region (for example `westus2`), the monthly budget and the
-largest machine. Then run:
+largest computer. Then run:
```bash test="cli-shape" id="agents-connect-azure-start"
cua cloud connect azure --region westus2 --budget 200 --max-size 4x16
@@ -341,7 +341,7 @@ link, and tell them:
- reply with the deployment's outputs `subscriptionId`, `tenantId` and
`clientId` (**Deployments**, **cua-spaces**, **Outputs**).
-When you run on a machine signed in to the `az` CLI, `next.run` deploys the
+When you run on a computer signed in to the `az` CLI, `next.run` deploys the
same template with `az deployment group create` and prints those outputs.
Run it only when the person asked you to set up the trust.
@@ -354,7 +354,7 @@ cua cloud connect azure --region westus2 --budget 200 --max-size 4x16 --subscrip
```
The check gets a check token from Cua, exchanges it with Microsoft Entra,
-reads the resource group and its permissions, and validates a machine
+reads the resource group and its permissions, and validates a computer
deployment. Nothing is created.
### 4. Verify
@@ -365,22 +365,22 @@ cua cloud status azure
## Other clouds
-Hetzner and Modal link with a token sealed to the person's machines (see
+Hetzner and Modal link with a token sealed to the person's computers (see
[Hetzner and Modal](#hetzner-and-modal)), or with their own sign-in on this
-machine, and Google Cloud too if the person prefers `gcloud` on this machine to
-a link without a key. The budget and largest machine work the same way:
+computer, and Google Cloud too if the person prefers `gcloud` on this computer to
+a link without a key. The budget and largest computer work the same way:
```bash test="cli-shape" id="agents-connect-other"
cua cloud connect gcp --project my-project --region us-central1 --budget 100 --max-size 4x16
cua cloud connect modal --environment spaces --budget 50
```
-The second command links Modal with the Modal CLI's sign-in on this machine
+The second command links Modal with the Modal CLI's sign-in on this computer
(`~/.modal.toml`) instead of a sealed token.
## What to ask the person, and what not to
-- Ask for: the region, the monthly budget, the largest machine, the AWS
+- Ask for: the region, the monthly budget, the largest computer, the AWS
account id, the Google Cloud project id and number, the Azure ids the
template prints, the Hetzner or Modal API token, and an approval in the Cua
Spaces app when the status says so.
diff --git a/docs/content/docs/spaces/guides/connect-your-agent.mdx b/docs/content/docs/spaces/guides/connect-your-agent.mdx
index e2d9e7fb71..bed70493b5 100644
--- a/docs/content/docs/spaces/guides/connect-your-agent.mdx
+++ b/docs/content/docs/spaces/guides/connect-your-agent.mdx
@@ -20,7 +20,7 @@ desktop and share a Space whenever you ask.
## Connect from the app
-On first run, **Pick your agent** lists the agents found on this machine,
+On first run, **Pick your agent** lists the agents found on this computer,
most used first: Hermes, Claude Code, Codex, Cursor, then the rest. Each row
names the settings file Cua changes. Press **Connect** on each agent you want:
the app adds the Cua skills and MCP server to that agent's settings. Nothing is
@@ -28,36 +28,36 @@ connected until you press it. If an agent was already open, close it and open
it again. Connecting none is fine: connect agents later in **Settings,
Connections**.
-### Per machine
+### Per computer
-Everything on this screen belongs to this machine only:
+Everything on this screen belongs to this computer only:
- The Cua skills and MCP server go into each agent's settings on this
- machine. On another machine, install Cua Spaces there and pick its agents.
-- **Sign-ins and keys** stay on this machine too. Another machine keeps its
+ computer. On another computer, install Cua Spaces there and pick its agents.
+- **Sign-ins and keys** stay on this computer too. Another computer keeps its
own.
### Codex and ChatGPT
Codex signs in with your ChatGPT account on its own, with `codex login`. When
Codex is connected, the screen shows **ChatGPT sign-in**: press **Sign in**
-and finish in the browser that opens. Codex keeps the sign-in on this machine,
-and Cua never reads or copies it. On another machine, sign in to Codex there
+and finish in the browser that opens. Codex keeps the sign-in on this computer,
+and Cua never reads or copies it. On another computer, sign in to Codex there
(press **Sign in** in its first run, or run `codex login`).
-An agent that Cua runs in a Space uses the provider keys saved on the machine
+An agent that Cua runs in a Space uses the provider keys saved on the computer
that hosts the Space: the **OpenAI key** for Codex and the **Anthropic key** for
Claude Code. Add them on **Pick your agent** or in **Settings, Connections**. They stay
-in this machine's Keychain (Credential Manager on Windows).
+in this computer's Keychain (Credential Manager on Windows).
### Claude Code and your Claude plan
-If you already use Claude Code on this machine, Cua can run it in your Spaces
+If you already use Claude Code on this computer, Cua can run it in your Spaces
with the same Claude plan. Press **Connect** next to Claude Code in **Settings,
Connections**. Before it reads anything, Cua says what it will do and waits for
you to press **Use my sign-in**:
-1. Cua reads the sign-in Claude Code already keeps on this machine. On a Mac
+1. Cua reads the sign-in Claude Code already keeps on this computer. On a Mac
that is the Keychain item "Claude Code-credentials", and macOS asks you to
allow it. On Linux and Windows, and when Claude Code keeps it in a file, it
is `.credentials.json` in Claude Code's folder (`~/.claude`, or the folder
@@ -83,7 +83,7 @@ every five minutes). Only when there is nothing newer does the row read **Needs
reconnect**, with **Reconnect**: open Claude Code once, or run `claude auth
login`, then press Reconnect.
-If Claude Code isn't signed in on this machine, Cua offers the ways on in this
+If Claude Code isn't signed in on this computer, Cua offers the ways on in this
order: sign in with Claude Code (`claude auth login` in Terminal, then try
again), paste a token made with `claude setup-token` (a long-lived token for
people who prefer one), or use an Anthropic API key. Sign out removes Cua's copy
@@ -118,7 +118,7 @@ codex mcp add cua -- cua daemon mcp
```
`cua daemon mcp` starts `cua daemon` if it is not running, so every agent on
-this machine shares the same Spaces, sandboxes and streams.
+this computer shares the same Spaces, sandboxes and streams.
## Check that it works
@@ -129,11 +129,11 @@ this machine shares the same Spaces, sandboxes and streams.
their own window or terminal.
Then try the request the app offers at the end of its first run. The agent makes
-a Space on this machine:
+a Space on this computer:
> Make a Linux Space on this Mac and show its desktop in a new window.
-On Windows the request says "this PC", and on Linux "this machine". When
+On Windows the request says "this PC", and on Linux "this computer". When
that works, try a bigger task:
| Ask your agent | What it does |
@@ -148,7 +148,7 @@ lists the tools it gets.
## What your agent can do
The cua MCP server gives an agent 33 Spaces tools plus sandbox and computer
-tools. For the machine the agent runs on, use [Cua Driver](/cua-driver/quickstart)
+tools. For the computer the agent runs on, use [Cua Driver](/cua-driver/quickstart)
instead. The main ones:
```text output
@@ -355,10 +355,10 @@ as the macOS Keychain.
| The agent has no `cua` tools | Run `cua agents status`. Then start a new session in the agent. In Hermes, run `/reload-mcp`. |
| "The Cua daemon isn't running. Start Cua, or run `cua daemon start`." | Open Cua Spaces, or run `cua daemon start`. |
| Your agent is not in the app's list | Run `cua agents detect` to see every supported agent, or add the server by hand as shown above. |
-| The agent can't reach a Space on another machine | Sign in on this machine, and make sure the machine is added to your account. See [Add a machine](/spaces/guides/add-a-computer#reach-it-from-your-other-machines). |
+| The agent can't reach a Space on another computer | Sign in on this computer, and make sure the computer is added to your account. See [Add a computer](/spaces/guides/add-a-computer#reach-it-from-your-other-computers). |
## Next
- [Create a Space](/spaces/guides/add-a-space): run an agent's work in a new desktop.
-- [Add a machine](/spaces/guides/add-a-computer): give your agent another machine.
+- [Add a computer](/spaces/guides/add-a-computer): give your agent another computer.
- [Agents in a Space](/spaces/guides/agents-in-a-space): agents with a name, a memory and schedules.
diff --git a/docs/content/docs/spaces/guides/connections.mdx b/docs/content/docs/spaces/guides/connections.mdx
index 2845152eb6..9b7f3b9ce0 100644
--- a/docs/content/docs/spaces/guides/connections.mdx
+++ b/docs/content/docs/spaces/guides/connections.mdx
@@ -11,7 +11,7 @@ with nothing to set up inside the Space.
## Connect a provider
Open **Settings, Connections** and scroll to **Providers**, below **Coding
-apps** and **On another machine**. Each row is one provider on one line: its
+apps** and **On another computer**. Each row is one provider on one line: its
icon, its name, a grey line saying what is saved (for example **Signed in as
[email protected] (Claude Max)** or **API key ending 4f2a**) or **Not
connected**, and then either **Connect** or a check and **Connected**.
@@ -28,8 +28,8 @@ more than one key for the provider, it lists them, each with **Remove**, and
such as **Work key**. The first key is the one the row shows and the one every
app uses unless you tell an app otherwise (see [Pick which key an app uses](#pick-which-key-an-app-uses)).
-The sheet shows only the ways that apply on this machine. For Anthropic that
-can be your Claude sign-in (found on this machine, for Claude Code only) or an
+The sheet shows only the ways that apply on this computer. For Anthropic that
+can be your Claude sign-in (found on this computer, for Claude Code only) or an
API key. For OpenAI it is an API key, or your ChatGPT sign-in for Codex.
Every other provider takes an API key. Anthropic, OpenAI, OpenRouter, Google
AI Studio, xAI, DeepSeek, Kimi and Custom endpoint are up front; press **Show
@@ -95,10 +95,10 @@ providers as fallbacks when you have not chosen one, and turns off borrowing sig
Hermes cannot reach its provider, the run fails and the thread shows the
**Connect** card for it.
-### A server on your own machine
+### A server on your own computer
Use **Custom endpoint** with the server's base URL, for example LM Studio or
-Ollama. A Space that is isolated from your machine cannot reach a server on it,
+Ollama. A Space that is isolated from your computer cannot reach a server on it,
and Cua does not change that for you: allow the port for that Space in its
network settings first. The key is optional.
@@ -112,7 +112,7 @@ checked, and providers Cua has not run end to end yet, are not listed.
| Provider | How to connect | Works with |
| --- | --- | --- |
-| Anthropic | Your sign-in on this machine, A pasted Claude token, API key | Claude Code, OpenCode, Goose, Pi, Hermes, OpenClaw, T3 Code |
+| Anthropic | Your sign-in on this computer, A pasted Claude token, API key | Claude Code, OpenCode, Goose, Pi, Hermes, OpenClaw, T3 Code |
| OpenAI | Plan sign-in, API key | Codex, OpenCode, Goose, Pi, Hermes, OpenClaw, T3 Code |
| OpenRouter | API key | OpenCode, Goose, Pi, Hermes, OpenClaw |
| Google AI Studio | API key | Gemini CLI, Antigravity, OpenCode, Goose, Pi, Hermes |
diff --git a/docs/content/docs/spaces/guides/create-a-space-with-the-sdk.mdx b/docs/content/docs/spaces/guides/create-a-space-with-the-sdk.mdx
index c18c20fbbc..6f7b604795 100644
--- a/docs/content/docs/spaces/guides/create-a-space-with-the-sdk.mdx
+++ b/docs/content/docs/spaces/guides/create-a-space-with-the-sdk.mdx
@@ -1,6 +1,6 @@
---
title: Use Spaces from code
-description: Create a Linux Space on your own machine from Python or TypeScript, run a command in it, take a screenshot, ask Cua Driver for its windows, watch it, and delete it. Then start from a full agent app in TypeScript, Rust or Swift.
+description: Create a Linux Space on your own computer from Python or TypeScript, run a command in it, take a screenshot, ask Cua Driver for its windows, watch it, and delete it. Then start from a full agent app in TypeScript, Rust or Swift.
keywords:
- Cua Spaces example
- TypeScript agent app
@@ -10,9 +10,9 @@ keywords:
import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
This walkthrough is for developers. A Space is a desktop your agents can use and
-you can watch. You create one on your own machine from code, run a command in it,
+you can watch. You create one on your own computer from code, run a command in it,
take a screenshot, ask Cua Driver which windows it sees, watch the desktop,
-and delete the Space. Nothing leaves your machine.
+and delete the Space. Nothing leaves your computer.
Requirements: Docker (or Podman or Colima) and about 4 GB of free memory.
@@ -42,7 +42,7 @@ npm install @trycua/cua
## 2. Create a Space and use it
-The program passes no location, so the Space runs on this machine: the
+The program passes no location, so the Space runs on this computer: the
canonical Linux desktop (`ghcr.io/trycua/linux:24.04`) in a container.
<Tabs groupId="sdk-lang" persist items={['Python', 'TypeScript']}>
@@ -208,10 +208,10 @@ Each app needs a Space: create one with **New Space**, or add one by address.
## Next
-- [Reach another machine](/cua-sdk#reach-another-machine): connect the SDK to
- any machine that runs cua-spacesd, by address and token.
-- [Add a machine](/spaces/guides/add-a-computer#use-a-spare-mac-to-host-spaces):
- let your laptop create Spaces on another machine, over the relay, ssh or
+- [Reach another computer](/cua-sdk#reach-another-machine): connect the SDK to
+ any computer that runs cua-spacesd, by address and token.
+- [Add a computer](/spaces/guides/add-a-computer#use-a-spare-mac-to-host-spaces):
+ let your laptop create Spaces on another computer, over the relay, ssh or
Tailscale.
- [Create a Space](/spaces/guides/add-a-space): any image, progress, GPUs.
- [Space kinds](/spaces/concepts/space-kinds): pass `kind` (`container`, `vm`
diff --git a/docs/content/docs/spaces/guides/cua-volume.mdx b/docs/content/docs/spaces/guides/cua-volume.mdx
index ac9a102716..3a476b4b2f 100644
--- a/docs/content/docs/spaces/guides/cua-volume.mdx
+++ b/docs/content/docs/spaces/guides/cua-volume.mdx
@@ -26,7 +26,7 @@ still reach the old content.
| Principal | `public/` | `agents/<self>/` | `agents/<other>/` | `spaces/<this>/` | `spaces/<other>/` |
|-----------|-----------|------------------|-------------------|------------------|-------------------|
-| You (app, CLI, agents on your machine) | rw | rw | rw | rw | rw |
+| You (app, CLI, agents on your computer) | rw | rw | rw | rw | rw |
| Agent A in Space S | r | rw | none | rw | none |
| Space S, no agent | r | none | none | rw | none |
@@ -174,7 +174,7 @@ the full set of numbers, including 1 GB rows and sync latency.
Every Space mounts the same volume, so a program in the guest reads and
writes it like any folder. The guest sees only that Space's view (the
Space's row in the table above, or its agent's), and it never holds keys:
-your machine serves the view over the Space's own connection and applies the
+your computer serves the view over the Space's own connection and applies the
access rules, the audit log and the secret scanner there.
| Guest | How it mounts | Where |
@@ -197,7 +197,7 @@ not need to reconnect the Space:
so no dead mount is left behind.
- When it starts, the daemon unmounts anything a previous daemon left at the
mount path (a crash, a force-quit) before it does anything else.
-- Your machine notices the connection closed, or that the new daemon reports
+- Your computer notices the connection closed, or that the new daemon reports
the volume detached, and mounts the volume again, then restarts the hotspot
if one was on. It retries with a growing wait (2 s, then 4 s, up to a
minute) while the daemon is still coming up, and keeps a persistent agent's
@@ -301,11 +301,11 @@ Python: `await space.send_file(path, cua.SpaceSendFileOptions(target_directory="
Agents use the MCP tool `send_file` ([what your agent can do](/spaces/guides/connect-your-agent#what-your-agent-can-do)).
The options are in the [`send_file` reference](/spaces/reference/spaces#send_file).
-## Sync across machines
+## Sync across computers
-Two machines using the same bucket see each other's changes within
+Two computers using the same bucket see each other's changes within
seconds. Each change is also written to a small change log in the bucket
-itself (`.cua-feed/`), and every machine checks it with a single listing
+itself (`.cua-feed/`), and every computer checks it with a single listing
request, twice a second while things change, backing off to every 5 seconds
when idle. No Cua service is involved; it works with your own S3, R2 or
MinIO bucket.
@@ -317,7 +317,7 @@ at p95 for a 1 KiB file, and shows in the other's mounted volume 2 ms to
0.34 s). While nothing changes, the check backs off, so the first change
after a quiet period can take up to 5 seconds.
-When two machines change the same file, the write that reaches the bucket
+When two computers change the same file, the write that reaches the bucket
last becomes the current version, and the other one is kept next to it as
`name (conflict from <machine> <date>).ext`. Both stay in the file's
history. Nothing is dropped silently.
@@ -328,7 +328,7 @@ cua volume status --json
<Callout type="info">
Keep the change log small with a bucket lifecycle rule that expires
-noncurrent versions under `.cua-feed/` after a day. Each machine already
+noncurrent versions under `.cua-feed/` after a day. Each computer already
deletes feed entries older than a day.
</Callout>
@@ -361,21 +361,21 @@ without saving anything. Keys go to the credential store, never to
**Menu bar.** The menu shows the volume's sync state next to the number of
Spaces (Synced, Syncing, Offline) and any conflicts, which open the Volume
-page. Nothing shows while the files stay on this Mac with no other machine.
+page. Nothing shows while the files stay on this Mac with no other computer.
**Volume page.** Status, not a file browser: Finder is. Open in Finder
-shows the volume, mounting it first when it is not mounted. Machines lists every
-machine on the bucket, this one with its pending uploads and last sync.
-Conflicts lists files two machines wrote at once: Open shows the other
+shows the volume, mounting it first when it is not mounted. Computers lists every
+computer on the bucket, this one with its pending uploads and last sync.
+Conflicts lists files two computers wrote at once: Open shows the other
copy in Finder, Resolve clears the entry and keeps both files.
-![The Volume page with two machines and a conflict](/img/spaces/spaces-volume-page.png)
+![The Volume page with two computers and a conflict](/img/spaces/spaces-volume-page.png)
## Storage
| Backend | Where | Set up |
|---------|-------|--------|
-| `fs` (default) | `~/.cua/volume/data` on this machine | Nothing |
+| `fs` (default) | `~/.cua/volume/data` on this computer | Nothing |
| `s3` | Any S3-compatible bucket with versioning on (AWS S3, R2, MinIO) | `cua volume config set` and `cua volume config set-keys` |
```bash test="cli-shape" id="cua-volume-config"
diff --git a/docs/content/docs/spaces/guides/install.mdx b/docs/content/docs/spaces/guides/install.mdx
index 1608ba8b0c..14ffded425 100644
--- a/docs/content/docs/spaces/guides/install.mdx
+++ b/docs/content/docs/spaces/guides/install.mdx
@@ -56,9 +56,9 @@ At a console the installer shows a checklist first. Add `--cli-only`
`--no-host`, `--dry-run` and `--yes` (`-Select`, `-CliOnly` and so on on Windows).
In a terminal the installer then signs you in. Over ssh, or on Linux without a
-display, it shows a code to approve in a browser on another machine. Signing in
-adds this machine to your account, so it shows up in Cua Spaces on your other
-machines. It provides Spaces and keeps its screen private; a machine set up
+display, it shows a code to approve in a browser on another computer. Signing in
+adds this computer to your account, so it shows up in Cua Spaces on your other
+computers. It provides Spaces and keeps its screen private; a computer set up
before keeps its settings. Add `--no-host` (`-NoHost`) to sign in without
adding it.
@@ -69,14 +69,14 @@ The first time you open the app, it walks you through a short setup. The
| Step | What it does |
|---|---|
-| Your machines, shared by your team and its agents | The welcome. |
-| Pick your agent | The agents found on this machine, most used first (Hermes, Claude Code, Codex, Cursor, then the rest). Press **Connect** on each one you want; nothing is connected until you do. See [Connect your agent](/spaces/guides/connect-your-agent). |
-| Add your other machines | Optional. Signing in lets your other machines and your cloud use this machine's Spaces. **Not now** keeps Cua on this machine only. |
-| Try it in your agent | A request to paste into the agent you connected, which makes a Space on this machine. With no agent, a first Space in one click: Linux, or macOS on a Mac with Apple silicon. |
+| Your computers, shared by your team and its agents | The welcome. |
+| Pick your agent | The agents found on this computer, most used first (Hermes, Claude Code, Codex, Cursor, then the rest). Press **Connect** on each one you want; nothing is connected until you do. See [Connect your agent](/spaces/guides/connect-your-agent). |
+| Add your other computers | Optional. Signing in lets your other computers and your cloud use this computer's Spaces. **Not now** keeps Cua on this computer only. |
+| Try it in your agent | A request to paste into the agent you connected, which makes a Space on this computer. With no agent, a first Space in one click: Linux, or macOS on a Mac with Apple silicon. |
If you skip the setup, **Finish setting up** at the bottom of the sidebar opens it again.
-Cua Spaces launches at login by default, so the Spaces this machine provides
+Cua Spaces launches at login by default, so the Spaces this computer provides
and your persistent agents come back after a restart. Turn it off in **Settings,
General**.
@@ -89,7 +89,7 @@ authentication agent, local or over a remote desktop such as xrdp. `sudo apt rem
turns off what the app set up (see
[Check, pause or remove](/spaces/guides/add-a-computer#check-pause-or-remove)).
-The download page offers the x64 package. On an arm64 machine, take
+The download page offers the x64 package. On an arm64 computer, take
`cua-spaces_<version>_arm64.deb` from the
[GitHub release](https://github.com/trycua/cua/releases) instead: `apt` refuses
the x64 package there with a list of packages it cannot install. The .deb
@@ -101,10 +101,10 @@ browser sandbox (it starts with `--no-sandbox`), and without the system's
confirmation prompt you cannot share a Space and the Keyvault is unavailable.
Use it to try Cua Spaces without installing, and install the .deb to keep it.
-For Linux Spaces created on this machine, the `cua` CLI uses Docker (gVisor
+For Linux Spaces created on this computer, the `cua` CLI uses Docker (gVisor
`runsc`, when installed, adds isolation) or QEMU. QEMU needs read and write
access to `/dev/kvm` to run same-architecture guests quickly. Run
-`cua runtime doctor` to see what this machine has.
+`cua runtime doctor` to see what this computer has.
## Updates
diff --git a/docs/content/docs/spaces/guides/keep-an-agent-running.mdx b/docs/content/docs/spaces/guides/keep-an-agent-running.mdx
index c24b00e034..77194e7bc3 100644
--- a/docs/content/docs/spaces/guides/keep-an-agent-running.mdx
+++ b/docs/content/docs/spaces/guides/keep-an-agent-running.mdx
@@ -1,12 +1,12 @@
---
title: Keep an agent running through crashes
-description: 'Run a coding agent so a crash of the process or machine driving it resumes the same session, with tool calls journaled before they run and a newer driver cutting off an older one.'
+description: 'Run a coding agent so a crash of the process or computer driving it resumes the same session, with tool calls journaled before they run and a newer driver cutting off an older one.'
---
import { Callout } from 'fumadocs-ui/components/callout';
A durable agent runs under a re-driver. When the process that drives the agent
-dies, or the machine it runs on does, the session is started again, the
+dies, or the computer it runs on does, the session is started again, the
agent's own session is reloaded, and the agent is told what had already
happened. It works with any harness that speaks the Agent Client Protocol
(ACP); the same runner drives all of them.
@@ -26,7 +26,7 @@ cua agent run --durable --on auto auto claude-code "Fix the failing tests in /wo
The two commands do the same: `cua agent add --durable` is `cua agent run
--durable` with the agent's name as the session's name. `--on` picks the
-machine the driver runs on (`auto`, or one of your machines by name; the
+computer the driver runs on (`auto`, or one of your computers by name; the
default is this one), `--in` a durable Space to work in (default none),
`--max-attempts` caps the drives (default 5) and `--stall-secs` sets when a
silent driver counts as wedged (default 120).
@@ -46,10 +46,10 @@ today.
The session keeps a journal in its state directory (`CUA_SESSION_STATE_DIR`,
or `$CUA_JOB_DATA/session` when that is empty). `cua agent add --durable`
-leaves it empty, so the journal sits in the run's data folder on the machine
+leaves it empty, so the journal sits in the run's data folder on the computer
that drives it: it outlives the driver's Space, and a driver that dies or stalls
-is started again on the same machine with the same conversation. A new drive on
-another machine does not find it and starts the task from the beginning. It holds:
+is started again on the same computer with the same conversation. A new drive on
+another computer does not find it and starts the task from the beginning. It holds:
| File | What |
|---|---|
@@ -60,28 +60,28 @@ another machine does not find it and starts the task from the beginning. It hold
## What to expect, by kind of failure
-Measured on real machines (Linux, Docker with gVisor, three machines on a
+Measured on real computers (Linux, Docker with gVisor, three computers on a
private account, a scripted model so no model keys or spend; three runs per
cell, so read the times as rough).
| What fails | What happens | Same conversation? |
|---|---|---|
| The agent process dies (`kill -9`) | The runner restarts it in place and resumes the session, in seconds | Yes, the recovery note lists what ran and what may have run halfway |
-| The runner (the driver process) dies | Noticed at once; a new driver starts a new Space on the same machine, 40 to 80 s with Claude Code and Codex | Yes by the journal: the harness's own session files are gone with the old Space, so the recovery note carries the journal's summary instead of the conversation |
-| The driver's Space is killed or runs out of memory | The machine sees the Space stop within a few seconds and ends the driver; a new driver starts a new Space on the same machine, about 55 s from the kill to the resumed agent with Claude Code | Same as above |
+| The runner (the driver process) dies | Noticed at once; a new driver starts a new Space on the same computer, 40 to 80 s with Claude Code and Codex | Yes by the journal: the harness's own session files are gone with the old Space, so the recovery note carries the journal's summary instead of the conversation |
+| The driver's Space is killed or runs out of memory | The computer sees the Space stop within a few seconds and ends the driver; a new driver starts a new Space on the same computer, about 55 s from the kill to the resumed agent with Claude Code | Same as above |
| The driver's Space is removed, or the driver freezes | Noticed only by the stall limit (`--stall-secs`, default 120 s): about 140 to 170 s from the fault to the resumed agent | Same as above |
-| The machine running the agent stops answering | After about 65 to 75 s the session records the lost machine and starts the next drive on **another machine** (see the cases below) | **No.** The task starts from the beginning |
-| The daemon on the machine running the agent restarts (an update) | The driver is lost 2 to 11 s later (the job runner lives in the daemon) and the next drive starts on the same machine about a second after the 2 s backoff; it finishes 35 to 55 s after the restart. The old driver's Space is removed by the machine within 30 s | Yes, by the journal, on the same machine |
-| The daemon on the machine that coordinates restarts | Nothing visible; a run on another machine is not disturbed (down 0.7 to 14 s, five runs) | Not applicable |
-| The disk of the machine is full | Each drive crashes at its first write (`exit 1`, 38 to 61 s) and uses a try; the status line names `ENOSPC`. With the space freed in time the next drive finishes: two runs ended done on drive 4 of 5 | Yes, by the journal |
-| The machine's clock is 10 minutes ahead or behind | The machine is shown `down` and a session pinned to it waits; the message says the clock is off. When the coordinator machine's clock is 10 minutes ahead the first drive starts about 86 s late; 10 minutes behind made no difference | Not applicable |
+| The computer running the agent stops answering | After about 65 to 75 s the session records the lost computer and starts the next drive on **another computer** (see the cases below) | **No.** The task starts from the beginning |
+| The daemon on the computer running the agent restarts (an update) | The driver is lost 2 to 11 s later (the job runner lives in the daemon) and the next drive starts on the same computer about a second after the 2 s backoff; it finishes 35 to 55 s after the restart. The old driver's Space is removed by the computer within 30 s | Yes, by the journal, on the same computer |
+| The daemon on the computer that coordinates restarts | Nothing visible; a run on another computer is not disturbed (down 0.7 to 14 s, five runs) | Not applicable |
+| The disk of the computer is full | Each drive crashes at its first write (`exit 1`, 38 to 61 s) and uses a try; the status line names `ENOSPC`. With the space freed in time the next drive finishes: two runs ended done on drive 4 of 5 | Yes, by the journal |
+| The computer's clock is 10 minutes ahead or behind | The computer is shown `down` and a session pinned to it waits; the message says the clock is off. When the coordinator computer's clock is 10 minutes ahead the first drive starts about 86 s late; 10 minutes behind made no difference | Not applicable |
| The network is slow (300 ms added, 5% loss, three runs) | About 2.5 times slower (340 to 369 s against 138 s for a 20 step task); no restart and no move | Not applicable |
-The machine-lost case in numbers (three machines, Claude Code and Codex, a
-scripted model; the machine was cut off with a firewall rule):
+The lost-computer case in numbers (three computers, Claude Code and Codex, a
+scripted model; the computer was cut off with a firewall rule):
- **Cut off from the account but still running** (traffic to the relay dropped,
- the model server still reachable), eight runs: the other machines declare it
+ the model server still reachable), eight runs: the other computers declare it
lost after 64 to 66 s and the next drive is running 67 s after the cut. Its
first tool step comes 107 to 121 s after the cut (median 114 s, the six runs
where it was timed). **The old
@@ -90,32 +90,32 @@ scripted model; the machine was cut off with a firewall rule):
drivers at once for 8 to 17 s), and the new driver repeats every step the old
one had done. When the cut ends, the coordinator's cancel stops the old
driver within 2 to 11 s; the epoch fence does not, because it is a file on
- each machine. A task whose side effects leave the machine (a `git push`, an
+ each computer. A task whose side effects leave the computer (a `git push`, an
API call, a message) can run twice at the same time.
- **Cut off completely**, four runs: lost after 65.6 to 65.9 s. The old driver
cannot reach the model, so it stops by itself within a step; no overlap.
-- **When the cut-off machine also held the coordinator**, six runs: the next
+- **When the cut-off computer also held the coordinator**, six runs: the next
drive starts 94 to 186 s after the cut, because the new coordinator starts
counting the silence only when it takes over.
-- **Three machine losses in a row** on one session: it moved between the two
- machines each time, finished on drive 4 of 5, and each drive started the task
- from the beginning. A drive that comes back to a machine that ran an earlier
- drive resumes that machine's old journal (and sees only its old working
+- **Three computer losses in a row** on one session: it moved between the two
+ computers each time, finished on drive 4 of 5, and each drive started the task
+ from the beginning. A drive that comes back to a computer that ran an earlier
+ drive resumes that computer's old journal (and sees only its old working
folder), not the progress made elsewhere.
-- **Every machine unreachable:** the session waits (`waiting for a machine that
- can take work`) with no deadline and uses no try; when the machines answer
+- **Every computer unreachable:** the session waits (`waiting for a computer that
+ can take work`) with no deadline and uses no try; when the computers answer
again it carries on, or ends `failed` at the limit.
-Other measurements: signing out of the account on the machine you type on leaves a
+Other measurements: signing out of the account on the computer you type on leaves a
running session alone, but `cua agent sessions` then lists only the sessions of this
-machine without a warning and other commands wait about a minute before saying you
-are not signed in. Signing the machine that runs the agent out lets the driver
-finish, but the session stays `running` until the machine signs in again. Starting
-the same name again from another machine used to start a second driver; since
-#6236 it does not. Twenty agents pinned to one 4 CPU, 7.7 GB machine took 1643 s one
+computer without a warning and other commands wait about a minute before saying you
+are not signed in. Signing the computer that runs the agent out lets the driver
+finish, but the session stays `running` until the computer signs in again. Starting
+the same name again from another computer used to start a second driver; since
+#6236 it does not. Twenty agents pinned to one 4 CPU, 7.7 GB computer took 1643 s one
at a time when each driver reserved 4 GiB; the driver now reserves 1.5 GiB and four
run at once (12 of 12 sessions finished on drive 1 with no out-of-memory kill). A
-killed agent waits for a free slot when the machine is full: 158 s from the kill to
+killed agent waits for a free slot when the computer is full: 158 s from the kill to
the resumed request with six running.
**By harness** (a runner kill, from the kill to the first model request that
@@ -124,26 +124,26 @@ carries the recovery note): Claude Code 50 to 80 s, Codex 38 s, OpenCode 47 s
lost its own (three runs), Pi 49 s (one run, since Pi runs through the same driver
as the others). Three runs per cell elsewhere, so read them as rough.
-When a drive moves to another machine, the new one does not have the journal,
+When a drive moves to another computer, the new one does not have the journal,
the conversation or the working folder of the old one. Plan for it:
- Put the files the task needs, and the results you want to keep, in
[Cua Volume](/spaces/guides/cua-volume). The default storage, This Mac, is a
- folder on one machine, so another machine does not see it. Use your own
- S3-compatible bucket (AWS S3, R2, MinIO) so every machine reaches the same
+ folder on one computer, so another computer does not see it. Use your own
+ S3-compatible bucket (AWS S3, R2, MinIO) so every computer reaches the same
files. `cua agent add --durable --on auto` says so when more than one
- machine is signed in and Cua Volume is still on This Mac. The same goes for
- a durable Space (`durable=true`): it is created again on another machine
+ computer is signed in and Cua Volume is still on This Mac. The same goes for
+ a durable Space (`durable=true`): it is created again on another computer
with an empty disk, and a Volume on This Mac is not visible from there.
- Write the task so running it again from the start is safe.
- A session makes at most 5 drives by default (`--max-attempts`), counting the
first one and every restart for any reason. When they are used up it ends
`failed` and says it gave up after 5 of 5 drives, with the last failure.
-- A drive that no machine has room for waits and says what it waits for, for
+- A drive that no computer has room for waits and says what it waits for, for
example `waiting for a machine with 1 CPU and 1.5 GB memory free`. A driver
- that runs a harness asks for 1 CPU and 1.5 GiB, so a machine with 8 GB runs
+ that runs a harness asks for 1 CPU and 1.5 GiB, so a computer with 8 GB runs
four of them at once.
-- A durable Space whose machine is lost is created again on another machine
+- A durable Space whose computer is lost is created again on another computer
within about a minute, with the same name and an empty disk; the old record
stays listed as offline until you delete it.
@@ -157,14 +157,14 @@ output; `cua agent status` has the history of every drive.
## What happens when it crashes
1. The re-driver issues a higher **epoch** and starts the driver again, on the
- machine that ran the last drive when it has room, else on another one (which
+ computer that ran the last drive when it has room, else on another one (which
starts the task from the beginning, see above).
2. The new driver raises the fence first. An older driver that is still alive
- **on the same machine** sees the higher floor on its next write, stops, and
+ **on the same computer** sees the higher floor on its next write, stops, and
exits with code 75 without writing anything. The fence is a file in the
- machine's own run folder, so it cannot reach an old driver on a machine that
+ computer's own run folder, so it cannot reach an old driver on a computer that
is cut off from the account; the coordinator's cancel stops that one when the
- machine is reachable again.
+ computer is reachable again.
3. The driver reloads the agent's session (`session/resume`, else
`session/load`). A harness with neither gets a **new** session and the run
is marked `degraded`: the recovery note then carries a summary of the
@@ -205,18 +205,18 @@ transactional mode keeps the workspace image in its log); the ACP driver's journ
holds the agent's conversation and tool ledger, not the Space's files, so
the agent is told which calls completed but must recreate the files itself.
-## Files on all your machines
+## Files on all your computers
-With one machine signed in, the Volume lives on that machine only. Once you are
-signed in on a second machine and no bucket is set as the Volume's storage, the
-Cua Spaces daemon keeps a copy of the Volume on each of your machines, with no
-cloud involved. One machine owns writes at a time and the others receive them.
-A write counts as durable when two machines hold it, and it never waits for a
-machine that is away. When the owner goes away, the most reliable machine with
+With one computer signed in, the Volume lives on that computer only. Once you are
+signed in on a second computer and no bucket is set as the Volume's storage, the
+Cua Spaces daemon keeps a copy of the Volume on each of your computers, with no
+cloud involved. One computer owns writes at a time and the others receive them.
+A write counts as durable when two computers hold it, and it never waits for a
+computer that is away. When the owner goes away, the most reliable computer with
a copy takes over, and if the old owner wakes up later it is fenced: it loses
nothing and writes nothing over the new owner.
-Durable Spaces are placed on the most reliable machine that has room: an
+Durable Spaces are placed on the most reliable computer that has room: an
always-on desktop before a laptop on power, a laptop on power before a laptop
on battery, and never the laptop you are using unless it is the only one that
fits. Closing a laptop's lid still puts it to sleep unless it is plugged in
@@ -227,7 +227,7 @@ daemon with `CUA_REPLICA=0`. Turning it on never costs data: the Volume's
current heads are backed up first, a Volume prepared by a newer Cua Spaces is
refused with a message instead of being rewritten, and a build that does not
know replication can still read the same folder. History from before a second
-machine joined stays on the machine that wrote it, and two copies are kept.
+computer joined stays on the computer that wrote it, and two copies are kept.
## What is and is not guaranteed
diff --git a/docs/content/docs/spaces/guides/keyvault.mdx b/docs/content/docs/spaces/guides/keyvault.mdx
index d7466f651c..66611442e2 100644
--- a/docs/content/docs/spaces/guides/keyvault.mdx
+++ b/docs/content/docs/spaces/guides/keyvault.mdx
@@ -150,7 +150,7 @@ From the SDK the same call is `space.request_site_login(url, options)`
(`requestSiteLogin` in Swift, TypeScript and Kotlin). See the
[Keyvault tool reference](/spaces/reference/agents#keyvault) for the full result shape.
-Requests also show up in the CLI, for a machine without the app open:
+Requests also show up in the CLI, for a computer without the app open:
```bash test="cli-shape" id="approve-login"
cua keyvault requests
diff --git a/docs/content/docs/spaces/guides/relay-security.mdx b/docs/content/docs/spaces/guides/relay-security.mdx
index 3fee722588..a4d3f4aa0e 100644
--- a/docs/content/docs/spaces/guides/relay-security.mdx
+++ b/docs/content/docs/spaces/guides/relay-security.mdx
@@ -7,7 +7,7 @@ import { Callout } from 'fumadocs-ui/components/callout';
`relay.cua.ai` (and any self-hosted `cua-relay`) does two jobs:
-- **For Cua machines, it coordinates a WireGuard®-based mesh.**
+- **For Cua computers, it coordinates a WireGuard®-based mesh.**
It introduces the two ends. When they can't reach each other directly, it
forwards their traffic as ciphertext it can't read. This is the default
for current versions of the Cua app, CLI and SDK.
@@ -21,21 +21,21 @@ page: tell us.
## Which path you are on
-| Your Cua version | Connections to your machines |
+| Your Cua version | Connections to your computers |
|---|---|
| `cua` CLI and SDK 0.7.0 or later, Cua Spaces app 0.13.0 or later, `cua-spacesd` 0.7.0 or later | **The mesh by default** (`CUA_MESH=prefer`): end to end. They use the HTTPS path only when the mesh isn't available (see [Turn it off, or require it](#turn-it-off-or-require-it)). |
| Older versions (`cua` 0.6.x and earlier, Cua Spaces app 0.12.x and earlier) | **The relay's HTTPS path**, unless the mesh beta was turned on. They keep working, but the relay can read their sessions in transit. Update to get the mesh. |
-A connection uses the mesh only when **both ends** support it: the machine you
-connect from and the machine you host. A mixed account (a new laptop and an
-old machine, say) uses the HTTPS path for that pair. Update in this order:
+A connection uses the mesh only when **both ends** support it: the computer you
+connect from and the computer you host. A mixed account (a new laptop and an
+old computer, say) uses the HTTPS path for that pair. Update in this order:
the Cua Spaces app first, then the `cua` CLI and SDK, then each hosted
-machine (`cua host setup` again, or let the app update it).
+computer (`cua host setup` again, or let the app update it).
## The short version
- **Over the mesh (Cua apps, CLI, SDK and daemon, on current versions):**
- traffic between your machine is encrypted end to end with
+ traffic between your computer is encrypted end to end with
WireGuard between keys that never leave the two ends. Most connections go
directly between the two networks; when they cannot, the relay forwards
the encrypted packets. **The relay cannot read or change shell output,
@@ -50,43 +50,43 @@ machine (`cua host setup` again, or let the app update it).
shell output, file contents, the desktop media stream, keystrokes and
clipboard data sent as input, and, unless sealed (below), Keyvault
passwords and teleport session bundles.
-- **Runs on all your machines** (`cua sb run --on auto`, durable Spaces):
- the relay stores the job log and passes requests between your machines,
- but everything a job is and produces is **sealed on your machines** with
- keys only your added machines hold. The relay sees job ids, the kind of
- each change, which machine an attempt went to, and sizes; never a command,
+- **Runs on all your computers** (`cua sb run --on auto`, durable Spaces):
+ the relay stores the job log and passes requests between your computers,
+ but everything a job is and produces is **sealed on your computers** with
+ keys only your added computers hold. The relay sees job ids, the kind of
+ each change, which computer an attempt went to, and sizes; never a command,
environment, input, output or result. See
- [Runs on all your machines](#runs-on-all-your-machines).
+ [Runs on all your computers](#runs-on-all-your-computers).
- It does not **store** traffic, env tokens or account tokens on either
path. On the HTTPS path it strips a client's credentials and forwards a
short-lived signed assertion instead (account mode), or forwards a
self-hosted relay's env token unmodified without persisting it (static
mode). On the mesh, account tokens go only to the relay, never to the
- machine, and a static relay never sees the env token at all (a machine
- proves it holds the token to the machine itself). See the relay README
+ computer, and a static relay never sees the env token at all (a computer
+ proves it holds the token to the computer itself). See the relay README
(`libs/cua-spacesd/crates/cua-relay/README.md` in the cua repository) for
the exact claims and how they are enforced in code.
- **The relay is still a trusted coordinator.** In account mode, the relay
- tells each machine which peers are yours (your machines, and
- the accounts a machine is shared with) and what each peer's mesh public
+ tells each computer which peers are yours (your computers, and
+ the accounts a computer is shared with) and what each peer's mesh public
key is. Both ends trust that list, just as they trust the relay's signed
- assertions on the HTTPS path. So a compromised relay could add a machine of
- its own as a peer, or hand your machine a key of its own in place of a
- machine's key, and then sit in the middle of the connections that follow.
+ assertions on the HTTPS path. So a compromised relay could add a computer of
+ its own as a peer, or hand your computer a key of its own in place of a
+ computer's key, and then sit in the middle of the connections that follow.
It can't decrypt traffic sent under keys it doesn't hold. A
- static-token relay can do less: each machine accepts only the machines that
+ static-token relay can do less: each computer accepts only the computers that
proved they hold its env token, and ignores any other peer the relay names.
- We are working on machine-signed keys, so that only your added machines can
+ We are working on computer-signed keys, so that only your added computers can
vouch for a peer's key. Until then, if you need a coordinator you don't
have to trust, run your own relay or [use your own
tailnet](/spaces/guides/your-tailnet).
- **The HTTPS path is quiet by default.** With the default `CUA_MESH=prefer`,
a connection that can't use the mesh falls back to the HTTPS path, and only
- a log line says so. Set `CUA_MESH=require` on your machines,
+ a log line says so. Set `CUA_MESH=require` on your computers,
and their connections never fall back to a path the relay can read.
- A compromised relay process, relay host, or a memory dump of either, is
- equivalent to a compromised session for every machine currently routed
- through it on the **HTTPS path**: it can mint assertions the machines still
+ equivalent to a compromised session for every computer currently routed
+ through it on the **HTTPS path**: it can mint assertions the computers still
trust, and read whatever crosses it meanwhile.
## The mesh (on by default)
@@ -95,7 +95,7 @@ machine (`cua host setup` again, or let the app update it).
on by default. When both ends and the relay support them, a `relay:` Space no longer goes through
the HTTPS path, and the relay forwards only ciphertext it cannot read or change.
Everything in the next sections describes the HTTPS path, which stays in use for
-everything else: the browser viewer, web-hosted agents, machines
+everything else: the browser viewer, web-hosted agents, computers
without the mesh, and anything where the mesh is not available (or you set
`CUA_MESH=off`).
@@ -104,9 +104,9 @@ without the mesh, and anything where the mesh is not available (or you set
These always use the relay's HTTPS path, so the relay can read them in
transit, whichever Cua version you run:
-- **The browser viewer**, and anything else that opens a machine through
+- **The browser viewer**, and anything else that opens a computer through
`https://<relay>/m/<computer>/…`: web or Cloudflare-hosted agents, and MCP
- clients that connect to a machine through a relay URL.
+ clients that connect to a computer through a relay URL.
- **Share links** (`cua share`): a private, team or public link is served
through the relay to whoever opens it.
- **A Keyvault site-login password** sent to a `relay:` Space over the HTTPS
@@ -115,7 +115,7 @@ transit, whichever Cua version you run:
And for Cua's own apps, CLI and SDK, these use the HTTPS path:
-- machines on [older versions](#which-path-you-are-on);
+- computers on [older versions](#which-path-you-are-on);
- anything set to `CUA_MESH=off`;
- a connection that fell back from the mesh under the default `prefer`;
- a self-hosted relay started without `--mesh on`.
@@ -127,87 +127,87 @@ And for Cua's own apps, CLI and SDK, these use the HTTPS path:
| gRPC (shell, files, input) | Ciphertext only (direct when possible) | Parsed and forwarded: **readable** |
| Desktop media stream | Ciphertext only; QUIC over the mesh, direct or relayed | Parsed and forwarded (TCP over the relay): **readable** |
| `/files` transfers | Ciphertext only | Parsed and forwarded: **readable** |
-| Account tokens | Sent to the relay only, to join the mesh; never to the machine | Stripped and replaced with a signed assertion |
-| Env tokens (static relays) | Never sent to the relay (a proof to the machine instead); travel to the machine inside WireGuard | Forwarded unmodified, not stored: **readable in transit** |
-| Keyvault site-login password | Inside WireGuard to the machine | **Gated**: refused over a `relay:` Space by default; sending anyway needs your explicit, per-sign-in acknowledgement (see below) |
-| Teleport session bundle (cookies, Safe Storage keys) | Inside WireGuard to the machine | **Sealed** once the Space's guest key is pinned; **gated** otherwise |
-| Who connects to which machine, when, how much | Visible (it coordinates and may relay) | Visible |
-| Batch runs' job log and requests (`--on auto`) | Stored sealed: commands, environments, outputs and results are ciphertext; job ids, placements and sizes are visible | Same (sealed before it leaves the machine) |
-
-Which path a connection took shows in the logs of the machine (`relay
+| Account tokens | Sent to the relay only, to join the mesh; never to the computer | Stripped and replaced with a signed assertion |
+| Env tokens (static relays) | Never sent to the relay (a proof to the computer instead); travel to the computer inside WireGuard | Forwarded unmodified, not stored: **readable in transit** |
+| Keyvault site-login password | Inside WireGuard to the computer | **Gated**: refused over a `relay:` Space by default; sending anyway needs your explicit, per-sign-in acknowledgement (see below) |
+| Teleport session bundle (cookies, Safe Storage keys) | Inside WireGuard to the computer | **Sealed** once the Space's guest key is pinned; **gated** otherwise |
+| Who connects to which computer, when, how much | Visible (it coordinates and may relay) | Visible |
+| Batch runs' job log and requests (`--on auto`) | Stored sealed: commands, environments, outputs and results are ciphertext; job ids, placements and sizes are visible | Same (sealed before it leaves the computer) |
+
+Which path a connection took shows in the logs of the computer (`relay
Space over the mesh`, or `using the relay's HTTPS path` with the reason).
-With `CUA_MESH=require`, a machine never falls back to the HTTPS path.
+With `CUA_MESH=require`, a computer never falls back to the HTTPS path.
-## Runs on all your machines
+## Runs on all your computers
-A batch run on your machines (`cua sb run --on auto`, `on="auto"` in the SDK
-and MCP tools) and a durable Space are coordinated by one of your machines,
-and the relay keeps their job log so that another machine can take over.
-That log, its snapshots, and the requests and answers between your machines
+A batch run on your computers (`cua sb run --on auto`, `on="auto"` in the SDK
+and MCP tools) and a durable Space are coordinated by one of your computers,
+and the relay keeps their job log so that another computer can take over.
+That log, its snapshots, and the requests and answers between your computers
are encrypted end to end:
-- **Your machines hold the keys.** Each signed-in machine has a pool key
- (X25519, in the same store as its machine key: the OS keychain for
- Cua-signed builds). It signs the pool key with its own machine key and
+- **Your computers hold the keys.** Each signed-in computer has a pool key
+ (X25519, in the same store as its computer key: the OS keychain for
+ Cua-signed builds). It signs the pool key with its own computer key and
registers it with the relay. The account's data key is wrapped to each
- machine's pool key with HPKE (RFC 9180) in authenticated mode, so a machine
- only accepts keys another of your machines wrapped. The relay stores the
+ computer's pool key with HPKE (RFC 9180) in authenticated mode, so a computer
+ only accepts keys another of your computers wrapped. The relay stores the
wraps and cannot open them.
-- **Everything about a job is sealed** before it leaves the machine, with
+- **Everything about a job is sealed** before it leaves the computer, with
XChaCha20-Poly1305: its command, environment, input, image and resources,
- its output and result, durable Spaces' addresses and tokens, your machines'
- details, and every request and answer between your machines. Each sealed
+ its output and result, durable Spaces' addresses and tokens, your computers'
+ details, and every request and answer between your computers. Each sealed
entry is bound to its position and readable fields, so the relay cannot
move it, swap it or change it unnoticed.
-- **New and revoked machines.** A machine you add is given the keys by any of
- your machines that has them, within seconds, and can then take over runs.
- At least one of those machines must be online for that: until then, a run
- on your machines from the new machine fails within seconds and names the
- machines that hold the keys and when the relay last saw them (`cua
- machines` shows them too). Open Cua on one of them, or revoke the ones
- you no longer have. A new machine never makes new keys on its own while a
- machine that holds them is still in your account, however long ago it was seen:
+- **New and revoked computers.** A computer you add is given the keys by any of
+ your computers that has them, within seconds, and can then take over runs.
+ At least one of those computers must be online for that: until then, a run
+ on your computers from the new computer fails within seconds and names the
+ computers that hold the keys and when the relay last saw them (`cua
+ computers` shows them too). Open Cua on one of them, or revoke the ones
+ you no longer have. A new computer never makes new keys on its own while a
+ computer that holds them is still in your account, however long ago it was seen:
only you can tell an asleep laptop from a lost one, and the relay can't
- make your machines drop the keys by hiding the others. Runs on the machine
+ make your computers drop the keys by hiding the others. Runs on the computer
itself (`--on local`, the default for `cua run`) never need the keys.
- When you revoke a machine, the relay refuses anything sealed under the
- keys it had until one of your machines makes new ones without it, which
+ When you revoke a computer, the relay refuses anything sealed under the
+ keys it had until one of your computers makes new ones without it, which
happens on the next write: nothing written after it left is readable by
it, even with the relay's help. What it could read before stays readable to
- it. If every machine that held the keys is revoked, the next machine starts
+ it. If every computer that held the keys is revoked, the next computer starts
new keys and the log nobody can read is dropped (its runs are lost).
| The relay can see | The relay cannot see |
|---|---|
| Job ids, run ids, and how many jobs a run has | Commands, arguments, environment variables, input |
| The kind of each change (submitted, dispatched, running, ended) and which entry ends a job | Outputs, exit codes, errors and results |
-| Which of your machines an attempt went to, and the attempt's number | Images, resources and timeouts |
-| Which machine coordinates, its epoch, and when | Durable Spaces' names, addresses and tokens |
-| Sizes and timing of every entry and request | Your machines' details as the coordinator records them |
-| Which machines hold the keys, and the key generation | The keys |
+| Which of your computers an attempt went to, and the attempt's number | Images, resources and timeouts |
+| Which computer coordinates, its epoch, and when | Durable Spaces' names, addresses and tokens |
+| Sizes and timing of every entry and request | Your computers' details as the coordinator records them |
+| Which computers hold the keys, and the key generation | The keys |
The relay checks what it can without the keys: it stores only sealed data
(anything else is refused), only under the newest key generation, keyrings
-wrapped by and to your account's added machines, and the fencing that
+wrapped by and to your account's added computers, and the fencing that
keeps one coordinator and one result per job. How this was checked (a model
checker, a simulation of the real code, and fault injection on real
-machines) is in the
+computers) is in the
[design](https://github.com/trycua/cua/blob/main/docs/rfcs/pool-self-coordination.md).
<Callout type="warn">
- The relay still decides which machines are your account's. A relay that is
- actively malicious could add a machine of its own (as it could add a
+ The relay still decides which computers are your account's. A relay that is
+ actively malicious could add a computer of its own (as it could add a
peer to the mesh, above) and be given the keys for what is written after
- that; it could not read anything sealed before, and the machine shows in
+ that; it could not read anything sealed before, and the computer shows in
`cua devices ls` and in the app as one the keys are
shared with. Run your own relay if that is not acceptable. Jobs reach your
- machines over the mesh (ciphertext); with the mesh off they use the HTTPS
+ computers over the mesh (ciphertext); with the mesh off they use the HTTPS
path, where the relay can read them in transit (above).
</Callout>
## Sealed delivery: where it stands
-We seal teleport secrets end to end to the destination machine's own key, so
+We seal teleport secrets end to end to the destination computer's own key, so
the relay forwards only ciphertext for a sealed delivery. The construction:
an ephemeral X25519 key per delivery, HKDF-SHA256, XChaCha20Poly1305, bound
to the Space id, a purpose string and a timestamp, with replay rejection
@@ -241,41 +241,41 @@ against. The gate and sealing apply to the HTTPS path only.
## Other hardening already shipped
-- **A second factor for new machines.** Re-signing in adds only
- your own machine (a re-key, or your account's first machine). A brand-new
- machine on an account that already has an added machine needs an approval
- from an added machine, or a sign-in whose token itself proves a second
+- **A second factor for new computers.** Re-signing in adds only
+ your own computer (a re-key, or your account's first computer). A brand-new
+ computer on an account that already has an added computer needs an approval
+ from an added computer, or a sign-in whose token itself proves a second
factor. A verified email alone is not enough.
-- **New machines are flagged.** A machine registered without an added
- machine's signature or MFA is marked unconfirmed until an added machine
+- **New computers are flagged.** A computer registered without an added
+ computer's signature or MFA is marked unconfirmed until an added computer
vouches for it.
-- **A separate origin for machine content.** Machines no longer render as
+- **A separate origin for computer content.** Computers no longer render as
HTML, register a Service Worker, or set cookies on the relay's own
origin outside the one known viewer path; a fully separate registrable
- domain for machine content is designed and partly implemented in code,
+ domain for computer content is designed and partly implemented in code,
pending a DNS/TLS rollout.
-- **Bounded relay memory.** A per-machine cap on buffered bytes and streams,
- plus a relay-wide budget with backpressure, so one machine (or one
+- **Bounded relay memory.** A per-computer cap on buffered bytes and streams,
+ plus a relay-wide budget with backpressure, so one computer (or one
account's worth of them) with slow-reading clients cannot take down every
- other machine's connection.
+ other computer's connection.
- **A tamper-evident, exportable audit log**, hash-chained like the
Keyvault's own, with `GET /v1/audit?format=jsonl` for export to your own
SIEM or backup.
- **The migration grace period (a stolen session alone reaching every
- machine) is off by default**, and time-boxed to an announced rollout
+ computer) is off by default**, and time-boxed to an announced rollout
window when it does run.
- **State writes that fail loudly.** The relay appends audit events and
sessions to their own logs instead of rewriting its state per event, cleans
- up after an interrupted write at startup, refuses a machine
+ up after an interrupted write at startup, refuses a computer
change it could not store (rather than acknowledging it), and keeps a
- reserve of free space that pool data cannot use, so sign-ins and machine
+ reserve of free space that pool data cannot use, so sign-ins and computer
changes keep working when pools fill the volume. A self-hosted relay
reports this on `GET /readyz` (a real write probe, free space, each
store's last write) and `GET /metrics`; alert when `/readyz` fails, free
space drops under 20%, or any write fails. The relay's
[README](https://github.com/trycua/cua/tree/main/libs/cua-spacesd/crates/cua-relay#state-and-monitoring)
lists the rules.
-- **No Nagle delay on relayed calls.** The relay and machines disable
+- **No Nagle delay on relayed calls.** The relay and computers disable
Nagle's algorithm on the tunnel, which used to add about 80 ms to each
small relayed call.
@@ -283,19 +283,19 @@ against. The gate and sealing apply to the HTTPS path only.
<Callout type="info">
**On by default** in the Cua Spaces app (every channel), the `cua` CLI and
- hosted machines, once they are on a version that includes it. Where the mesh
- cannot be used (a self-hosted relay without one, an older machine, a
+ hosted computers, once they are on a version that includes it. Where the mesh
+ cannot be used (a self-hosted relay without one, an older computer, a
network that blocks it) Cua uses the relay's HTTPS path, as before. To turn
it off, set `CUA_MESH=off` (below).
</Callout>
-With the mesh on, a machine that opens a Space on one of your machines
+With the mesh on, a computer that opens a Space on one of your computers
(`relay:<machine>`) connects to it over a WireGuard®-based mesh that runs
inside Cua itself, instead of through the relay's HTTPS path. The relay
coordinates the mesh but never holds a session key: shell, files, input,
screen and Keyvault deliveries cross it only as ciphertext.
-- **End to end.** Each machine makes its own key pair on first
+- **End to end.** Each computer makes its own key pair on first
use; the private half never leaves it. Traffic between two of them is
encrypted with WireGuard between those two keys.
- **Direct when possible.** Two ends on the same network connect directly.
@@ -309,8 +309,8 @@ screen and Keyvault deliveries cross it only as ciphertext.
### Turn it off, or require it
-Both ends use the mesh when it is available: the machine you connect from and
-the machine you host. Each end decides for itself with `CUA_MESH`.
+Both ends use the mesh when it is available: the computer you connect from and
+the computer you host. Each end decides for itself with `CUA_MESH`.
| `CUA_MESH` | Behavior |
|---|---|
@@ -318,27 +318,27 @@ the machine you host. Each end decides for itself with `CUA_MESH`.
| `off` | The relay's HTTPS path only, as before the mesh. |
| `require` | The mesh or nothing: a relay that could read the session is never used. |
-- **On the machine:** set `CUA_MESH` where `cua` runs (your shell, or the
+- **On the computer:** set `CUA_MESH` where `cua` runs (your shell, or the
environment of the cua daemon; restart the daemon with `cua daemon stop`
after changing it).
-- **On a hosted machine:** to turn it off there, run `cua host setup` with
+- **On a hosted computer:** to turn it off there, run `cua host setup` with
`CUA_MESH=off` set. The setting is kept for the host's service until you run
setup again without it.
-`cua spaces ls` lists the same machines either way. With `prefer`, a machine
+`cua spaces ls` lists the same computers either way. With `prefer`, a computer
or relay that does not speak the mesh is used over HTTPS, so mixing
-updated and older machines works.
+updated and older computers works.
### Who can connect
The relay applies the rules you already manage:
-- A machine added to your account reaches the machines your account owns
+- A computer added to your account reaches the computers your account owns
and those shared with it, while their sharing is on.
-- The machine sees each machine with the same identity as before (account,
+- The computer sees each computer with the same identity as before (account,
verified email, owner, editor or viewer), and its own host policy still
decides what that caller may do.
-- Stopping sharing, removing someone from a share list, or revoking a machine
+- Stopping sharing, removing someone from a share list, or revoking a computer
takes it off the mesh within seconds and cuts its open connections. The
next call says why.
@@ -346,7 +346,7 @@ The relay applies the rules you already manage:
A desktop view, terminal or agent session over the mesh counts toward your
plan's live sessions, the same as one over the relay's HTTPS path, and one
-machine reached both ways at once counts once. Remote hours count only the
+computer reached both ways at once counts once. Remote hours count only the
time a session's traffic goes through the relay: a direct connection uses
none. `cua usage` and the app's Settings show both.
@@ -361,8 +361,8 @@ going through the relay resumes when the relay is back.
### Self-hosted relays
A self-hosted `cua-relay` coordinates a mesh when you turn it on with
-`--mesh on` (or `CUA_RELAY_MESH=on`); without it, machines use the HTTPS
-path. Give it a UDP port for STUN so machines learn their public addresses:
+`--mesh on` (or `CUA_RELAY_MESH=on`); without it, computers use the HTTPS
+path. Give it a UDP port for STUN so computers learn their public addresses:
```bash skip="no-runner"
cua-relay --tokens "$TOKEN" --public-url https://relay.example.com \
@@ -371,15 +371,15 @@ cua-relay --tokens "$TOKEN" --public-url https://relay.example.com \
The relay advertises `relay.example.com:3478` (override with
`--mesh-stun`). Open UDP 3478 to it. `--mesh off` (the default) leaves the
-mesh off (machines then use the HTTPS path); `--mesh-relay off` keeps the
-coordinator but stops relaying packets (machines that cannot reach each other
+mesh off (computers then use the HTTPS path); `--mesh-relay off` keeps the
+coordinator but stops relaying packets (computers that cannot reach each other
directly then cannot connect over the mesh). The mesh registry persists next
-to the state file (`<state>.mesh.json`), so a restart keeps every machine's
+to the state file (`<state>.mesh.json`), so a restart keeps every computer's
keys.
-On a self-hosted relay with static tokens, a machine reaches a machine only
-after proving it holds that machine's env token. The machine checks the
-proof itself and remembers the machines it accepted; the relay only passes the
+On a self-hosted relay with static tokens, a computer reaches a computer only
+after proving it holds that computer's env token. The computer checks the
+proof itself and remembers the computers it accepted; the relay only passes the
proof along and never sees the token.
### Use your own tailnet instead
@@ -411,12 +411,12 @@ on its own disk.
| Data | Why | How long |
|---|---|---|
-| Your account id, email and name; your machines' names, owners and share lists | Routing, and checking who may connect | Until you remove the machine or delete your account |
-| Your added machines: their public keys and sessions | Adding a machine to your account | An addition ends 30 days after it was last used; removed when you revoke the machine |
-| Mesh registry: each machine's and machine's WireGuard public key, and the network addresses it reports (up to 32 public and local IP addresses per node) | Introducing the two ends of a connection | While the machine is registered |
-| Which accounts reached each machine recently, and whose access was revoked (grants) | Making a revoke also cut the short-lived tickets a machine issued | About a day: each entry is dropped after 24 hours |
+| Your account id, email and name; your computers' names, owners and share lists | Routing, and checking who may connect | Until you remove the computer or delete your account |
+| Your added computers: their public keys and sessions | Adding a computer to your account | An addition ends 30 days after it was last used; removed when you revoke the computer |
+| Mesh registry: each computer's and computer's WireGuard public key, and the network addresses it reports (up to 32 public and local IP addresses per node) | Introducing the two ends of a connection | While the computer is registered |
+| Which accounts reached each computer recently, and whose access was revoked (grants) | Making a revoke also cut the short-lived tickets a computer issued | About a day: each entry is dropped after 24 hours |
| Your account's audit log (hash-chained) | Your own audit trail, exportable with `GET /v1/audit?format=jsonl` | The latest 5,000 entries per account |
-| Pool keys (wrapped to your machines) and the sealed job log | [Runs on all your machines](#runs-on-all-your-machines) | Kept with your account; the relay can't open them |
+| Pool keys (wrapped to your computers) and the sealed job log | [Runs on all your computers](#runs-on-all-your-computers) | Kept with your account; the relay can't open them |
| Usage totals (hosted relay) | Your plan's allowance | Totals for the current calendar month |
| Usage analytics events (PostHog, EU) | Product metrics on relay usage | Sent under a pseudonymous id derived from your account id, with no person profile; PostHog's retention applies |
| Server logs | Operating the service | 30 days. Your account id can appear in them; emails are redacted |
@@ -442,8 +442,8 @@ harbor for good-faith security research.
- [End-to-end encrypted connections](#end-to-end-encrypted-connections): the
mesh in full, and [Use your tailnet](/spaces/guides/your-tailnet) to run on
your own Tailscale or Headscale network instead.
-- [Add a machine](/spaces/guides/add-a-computer#reach-it-from-your-other-machines):
- adding a machine to your account, in full.
+- [Add a computer](/spaces/guides/add-a-computer#reach-it-from-your-other-computers):
+ adding a computer to your account, in full.
- [Share a Space](/spaces/guides/share-a-space): the allowlist and audit trail
for sharing.
- [Keyvault](/spaces/guides/keyvault) and
diff --git a/docs/content/docs/spaces/guides/repo-cache.mdx b/docs/content/docs/spaces/guides/repo-cache.mdx
index 355e2bd38e..4499911632 100644
--- a/docs/content/docs/spaces/guides/repo-cache.mdx
+++ b/docs/content/docs/spaces/guides/repo-cache.mdx
@@ -1,12 +1,12 @@
---
title: Repo cache
-description: 'How Cua keeps verified copies of public git repositories on this machine so a repeat git clone in a Space is fast, what it never caches, the setting, how to clear it and what it reports.'
+description: 'How Cua keeps verified copies of public git repositories on this computer so a repeat git clone in a Space is fast, what it never caches, the setting, how to clear it and what it reports.'
---
import { Callout } from 'fumadocs-ui/components/callout';
The first time a Space clones a public repository, Cua downloads it as usual.
-In the background, the Cua daemon on your machine also keeps a verified copy
+In the background, the Cua daemon on your computer also keeps a verified copy
of that repository. The next Space that clones it starts from that copy, so a
repository that took about 5 seconds to clone takes about a second, and only
what changed since is downloaded. Your agent runs the same `git clone URL` as
@@ -24,12 +24,12 @@ always. There is nothing to set up per repository and no list to maintain.
- **Repositories, not dependencies yet.** The row in Settings is called
**Repo and dependency cache** because it will hold more later. Today it holds
repositories.
-- **This machine's disk only.** Nothing is sent anywhere to fill it, and a
- copy is never shared with another machine.
+- **This computer's disk only.** Nothing is sent anywhere to fill it, and a
+ copy is never shared with another computer.
## How a clone uses it
-The copies live in a folder that Linux container Spaces on this machine see
+The copies live in a folder that Linux container Spaces on this computer see
read-only. A small helper that Cua puts next to the Space's git, never the
agent, makes `git clone` ask the remote for its current tip and take the
objects it already has from the copy:
diff --git a/docs/content/docs/spaces/guides/sandbox-sdks.mdx b/docs/content/docs/spaces/guides/sandbox-sdks.mdx
index 90df725996..e5227b369f 100644
--- a/docs/content/docs/spaces/guides/sandbox-sdks.mdx
+++ b/docs/content/docs/spaces/guides/sandbox-sdks.mdx
@@ -1,16 +1,16 @@
---
title: Use the E2B, Daytona or Modal SDK with Spaces
sidebarTitle: E2B, Daytona & Modal SDKs
-description: "The unmodified E2B, Daytona or Modal SDK talks to Cua: its sandboxes, images, volumes and functions become Spaces on your own machines."
+description: "The unmodified E2B, Daytona or Modal SDK talks to Cua: its sandboxes, images, volumes and functions become Spaces on your own computers."
---
import { Callout } from 'fumadocs-ui/components/callout';
import { Tabs, Tab } from 'fumadocs-ui/components/tabs';
Code written for the E2B, Daytona or Modal SDK runs on Cua Spaces without a
-code change. The SDK talks to a Cua gateway on your machine that speaks the
+code change. The SDK talks to a Cua gateway on your computer that speaks the
provider's API, and every sandbox it creates (and every container a Modal
-Function runs in) is a Space on your machines, your pool or your own cloud
+Function runs in) is a Space on your computers, your pool or your own cloud
accounts. Requests never reach the provider, and no provider account is needed.
## How it works
@@ -30,7 +30,7 @@ cua run --compat daytona -- python agent.py
cua run --compat modal -- python agent.py
```
-**Point an SDK on this machine at a gateway.** `cua compat serve` runs the
+**Point an SDK on this computer at a gateway.** `cua compat serve` runs the
gateway until you stop it, and `cua compat env` prints the exports a client
needs. In another shell, evaluate them and run your program as usual.
@@ -121,10 +121,10 @@ results.
</Tab>
</Tabs>
-## What you get on your own machines
+## What you get on your own computers
With no options, sandboxes run where every Cua create runs by default (this
-machine, or its overflow when a cloud is linked), as a VM where the machine has
+computer, or its overflow when a cloud is linked), as a VM where the computer has
KVM or Hypervisor.framework and as a container where it does not. Each SDK
carries Cua placement in a field it already has:
@@ -136,7 +136,7 @@ carries Cua placement in a field it already has:
`cua.on` is `local`, `host:<machine>`, a pool or one of your own cloud
accounts; `cua.kind` is `vm`, `container` or `microvm`. Daytona sizes come from
the SDK's own resources. Modal's `region` and `cloud` have no meaning on your
-own machines and are ignored with a warning. Forks, snapshots and pauses are
+own computers and are ignored with a warning. Forks, snapshots and pauses are
copy-on-write, and Daytona's computer use works on Linux, macOS and Windows
Spaces.
@@ -187,7 +187,7 @@ second. The default size is E2B's default, 2 vCPU and 2 GiB.
For Python, you can also swap the dependency instead of running a gateway.
`cua-e2b` installs a top-level `e2b` module, so code written for e2b 2.42,
2.56 or 2.58 keeps working, and every sandbox is a Linux VM Space on your
-machines. Install one or the other in an environment, not both.
+computers. Install one or the other in an environment, not both.
```bash skip="pseudo"
uv pip uninstall e2b
@@ -197,10 +197,10 @@ uv pip install "cua-e2b @ git+https://github.com/trycua/cua#subdirectory=libs/py
| e2b | cua-e2b |
|---|---|
| `create(template=...)` | A Cua checkpoint (the sandbox is forked from it, memory included) or an image. `None` or `"base"` is the canonical Linux image. |
-| Placement | `CUA_E2B_ON` (default `auto`: the least-loaded of your machines), `CUA_E2B_KIND` (default `vm`), `CUA_E2B_CPUS`, `CUA_E2B_MEMORY_MB`. |
+| Placement | `CUA_E2B_ON` (default `auto`: the least-loaded of your computers), `CUA_E2B_KIND` (default `vm`), `CUA_E2B_CPUS`, `CUA_E2B_MEMORY_MB`. |
| `timeout`, `set_timeout`, `lifecycle` | A Space lifetime kept by the daemon: the Space is deleted (or suspended for `on_timeout="pause"`) even after your process exits. |
| `commands`, `pty`, `git`, `files`, `watch_dir` | cua-spacesd's process and file services; commands run as `/bin/bash -l -c`, other users through `sudo -n`. |
-| `get_host(port)` | A loopback `host:port` forwarded to the Space on any of your machines. It is plain TCP, so use `http://`; code that hard-codes `https://` runs through `cua run --compat e2b`, which serves TLS. |
+| `get_host(port)` | A loopback `host:port` forwarded to the Space on any of your computers. It is plain TCP, so use `http://`; code that hard-codes `https://` runs through `cua run --compat e2b`, which serves TLS. |
| `download_url`, `upload_url` | Signed `/files` URLs minted by cua-spacesd (24 hours at most). |
| `pause`, `connect`, `fork`, snapshots | Suspend and resume, copy-on-write forks of a running VM, pinned checkpoints. |
| `Template` builder, `Volume` | Recipes run in a VM and saved as a snapshot; volumes are folders of Cua Volume. |
@@ -216,7 +216,7 @@ row, is in
A sandbox boots with its desktop, because computer use is part of a Daytona
sandbox. The label `cua.desktop=false` leaves it out for a faster boot and more
-sandboxes per machine; computer use calls then answer Daytona's 503 naming the
+sandboxes per computer; computer use calls then answer Daytona's 503 naming the
missing desktop.
| Daytona | On Cua |
@@ -227,7 +227,7 @@ missing desktop.
| `stop` | The Space is suspended (memory kept) where its runtime cannot cold-stop, so background processes survive `stop`/`start`. |
| Secrets | Cua Spaces have no egress proxy to substitute a secret into outbound requests. Add the label `cua.secrets=plaintext` to inject the value into the environment variable; without it, creating with `secrets` is refused with this reason. |
| Volumes | A volume is a folder of Cua Volume bound at the mount path, so Cua Volume must be mounted in the Space. A Space writes only its own folder, so a folder that several sandboxes share needs a grant you confirm (`cua volume grant space:<id> daytona-volumes/<volume id>/ --rw`); without it the create answers 400 and says which grant it needs. |
-| Warm pools | A Cua pool of the snapshot's image, on this machine. |
+| Warm pools | A Cua pool of the snapshot's image, on this computer. |
| Egress rules | An nftables policy in the guest (Linux guests). |
## Modal
@@ -242,7 +242,7 @@ Every Sandbox, and every container a Function runs in, is a Space.
| Sidecar containers, private-registry bases (`from_aws_ecr`, `from_gcp_artifact_registry`), NetworkFileSystem, workspace administration, billing, metrics series | `UnimplementedError` with the reason. |
| Volumes | Version 1 only: a Sandbox sees a copy of the volume, its changes are committed to the volume (a folder of Cua Volume) every few seconds and when it ends, and `reload_volumes` fetches what others committed. The whole volume is copied in at mount; file modes and ownership are not stored. `version=2` raises `InvalidError`. |
| Image bases | A base must run cua-spacesd. `from_registry` accepts Cua images, `python:*`, `ubuntu:*`, `debian:*` and images you map in `images.json`; another base raises `ImageBuildError` that says how to map it. |
-| `snapshot_filesystem` | A Cua checkpoint of the machine; a Sandbox made from it has the files, and the snapshotted machine's processes continue in the copy. |
+| `snapshot_filesystem` | A Cua checkpoint of the computer; a Sandbox made from it has the files, and the snapshotted computer's processes continue in the copy. |
| Tunnels | `https://<port>-<sandbox id>.modal.localhost:<port>` names served by the gateway; its CA is in `SSL_CERT_FILE`. Unencrypted ports are loopback listeners. Ports declared with `h2_ports` negotiate HTTP/2. |
| Container privileges | Processes run as root. |
diff --git a/docs/content/docs/spaces/guides/share-a-space.mdx b/docs/content/docs/spaces/guides/share-a-space.mdx
index 550b502390..2a173541a3 100644
--- a/docs/content/docs/spaces/guides/share-a-space.mdx
+++ b/docs/content/docs/spaces/guides/share-a-space.mdx
@@ -1,6 +1,6 @@
---
title: Share a Space
-description: 'Let someone in your team watch or use one of your Spaces through the relay, and reach a Space from your other machines.'
+description: 'Let someone in your team watch or use one of your Spaces through the relay, and reach a Space from your other computers.'
---
import { Callout } from 'fumadocs-ui/components/callout';
@@ -83,14 +83,14 @@ change it, share with the team again with the other role.
## How it works
Sharing uses the same relay and allowlist as an
-[added machine](/spaces/guides/add-a-computer#add-a-machine-from-a-terminal):
+[added computer](/spaces/guides/add-a-computer#add-a-computer-from-a-terminal):
- A host (`relay:<id>` from `cua host setup`) is shared directly.
- Any other Space is published on the relay on its first share. The owner's
- account registers a machine for it, and the Space's own driver dials out
+ account registers a computer for it, and the Space's own driver dials out
over WSS, so no inbound port opens.
-- The relay keeps two lists per machine: `allow` (editors) and `viewers`.
-- Invitees need a verified email or account ID and an [added machine](/spaces/guides/add-a-computer#reach-it-from-your-other-machines).
+- The relay keeps two lists per computer: `allow` (editors) and `viewers`.
+- Invitees need a verified email or account ID and an [added computer](/spaces/guides/add-a-computer#reach-it-from-your-other-computers).
- Removing someone, or changing their role, cuts their open streams at once.
- Team membership comes from your team in your Cua account, not from the
relay. The Cua account service checks it when you share and again each time
@@ -98,8 +98,8 @@ Sharing uses the same relay and allowlist as an
leaves your team, they lose access to what you shared with them. If a team
is deleted, its shares stop.
- A team share works differently. The Space goes on the team's list of
- machines, and each time someone opens it, the relay checks with the Cua
- account service that they are still in the team and that their machine is
+ computers, and each time someone opens it, the relay checks with the Cua
+ account service that they are still in the team and that their computer is
approved.
```rust test="excerpt" id="rs-share-space" source="libs/cua/crates/cua-spaces/tests/share_space_e2e.rs#rs-share-space"
@@ -124,9 +124,9 @@ Sharing asks you first:
Removing someone needs no confirmation.
-## Reach a Space from your other machines
+## Reach a Space from your other computers
-To reach a Space from your phone or another machine without sharing it with
+To reach a Space from your phone or another computer without sharing it with
anyone, publish it on the relay:
```bash test="cli-shape" id="cua-spaces-relay-register"
@@ -138,7 +138,7 @@ cua spaces relay-unregister local:studio
let reg = ada.relay_register(&info.id).await.unwrap();
```
-Only your account's added machines reach it until you share it. The MCP
+Only your account's added computers reach it until you share it. The MCP
tools are `relay_register_space` and `relay_unregister_space`.
## Audit
@@ -156,7 +156,7 @@ tools are `relay_register_space` and `relay_unregister_space`.
| Space | Shareable | Why |
|---|---|---|
| Host (`relay:<id>`) | yes | Already on the relay. |
-| Local container or VM | yes, while this machine runs it | Its driver dials the relay. Suspending it disconnects everyone. |
+| Local container or VM | yes, while this computer runs it | Its driver dials the relay. Suspending it disconnects everyone. |
| In your own cloud (AWS, Google Cloud, Modal) | yes | Its driver dials the relay from the cloud. |
| Added by address (`direct:`) | yes, if its driver supports `relay_attach` | Older drivers report `capability_missing`. |
| A Space shared with you | no | Only the owner can share (`permission_denied`). |
diff --git a/docs/content/docs/spaces/guides/teams.mdx b/docs/content/docs/spaces/guides/teams.mdx
index b0f1e8f3b4..24ea02d832 100644
--- a/docs/content/docs/spaces/guides/teams.mdx
+++ b/docs/content/docs/spaces/guides/teams.mdx
@@ -1,13 +1,13 @@
---
title: Plans and Teams
-description: 'Cua Spaces Free, Pro and Teams: what each plan includes and how to see your usage. How to buy Teams, invite people, pair team machines, approve machines and manage seats.'
+description: 'Cua Spaces Free, Pro and Teams: what each plan includes and how to see your usage. How to buy Teams, invite people, pair team computers, approve computers and manage seats.'
---
import { Callout } from 'fumadocs-ui/components/callout';
-Cua Spaces is bring-your-own compute: you connect your own machines, and Cua
+Cua Spaces is bring-your-own compute: you connect your own computers, and Cua
does not rent them out. The plans cover the app, sharing and the hosted relay
-that lets your machines reach your machines. Current prices are on
+that lets your computers reach your computers. Current prices are on
[cua.ai/pricing](https://cua.ai/pricing), which is the source of truth.
## Plans
@@ -18,18 +18,18 @@ that lets your machines reach your machines. Current prices are on
| Pro | $18 a month or $180 a year, one person | 5 | 200 a month |
| Teams | $30 per seat a month or $300 per seat a year, 1 to 100 seats | 5 per seat | 200 per seat a month, pooled across the team |
-Every plan includes Spaces on every machine you connect and Teleport. Pro adds
+Every plan includes Spaces on every computer you connect and Teleport. Pro adds
more live sessions and remote hours. Teams adds sharing a Space with your team,
-team-owned machines, roles and machine approval. Sharing is for teams: Free and
+team-owned computers, roles and computer approval. Sharing is for teams: Free and
Pro accounts without a team cannot share a Space. SSO and audit export are not
included yet.
## What counts toward the limits
-**Remote hours** are the time you spend using your machines from somewhere
-else. Using a machine from itself is free.
+**Remote hours** are the time you spend using your computers from somewhere
+else. Using a computer from itself is free.
-A **live session** is one person or agent holding a stream open to a machine
+A **live session** is one person or agent holding a stream open to a computer
through the relay, such as a desktop view, a terminal or an agent's process
stream. Each hour with at least one live session counts as one remote hour, per
calendar month (UTC).
@@ -60,17 +60,17 @@ refunds.
## Buy Teams
-Teams turns the machines your team already has into shared desktops for people
-and their agents. Machines belong to the team instead of one person's account,
-an owner and admins decide who can do what, and a new machine must be approved
-before it can reach a team machine.
+Teams turns the computers your team already has into shared desktops for people
+and their agents. Computers belong to the team instead of one person's account,
+an owner and admins decide who can do what, and a new computer must be approved
+before it can reach a team computer.
<VideoDemo
src="https://trycua.github.io/assets/videos/cua-spaces/teams.mp4"
poster="https://trycua.github.io/assets/videos/cua-spaces/teams-poster.jpg"
title="Cua Spaces Teams"
>
- Create a team, invite a teammate and add a machine for the team (29 seconds, no sound).
+ Create a team, invite a teammate and add a computer for the team (29 seconds, no sound).
</VideoDemo>
Teams starts with 1 seat, for you. Start with just yourself, then add a seat for
@@ -115,105 +115,105 @@ A team has one owner, and any number of admins and members.
| | Owner | Admin | Member |
|---|---|---|---|
-| Open team machines (from an approved machine) | yes | yes | yes |
-| Request approval for a new machine | not needed | yes | yes |
+| Open team computers (from an approved computer) | yes | yes | yes |
+| Request approval for a new computer | not needed | yes | yes |
| Leave the team | no | yes | yes |
| Invite people | yes | yes | no |
| Remove members | yes, admins too | members only | no |
-| Add and remove team machines | yes | yes | no |
-| Approve or deny machines | yes | yes | no |
+| Add and remove team computers | yes | yes | no |
+| Approve or deny computers | yes | yes | no |
| Make a member an admin, or an admin a member | yes | no | no |
| Cancel the subscription, delete the team | yes | no | no |
The owner's role cannot change and the owner cannot leave: to close a team,
-cancel the subscription first, then delete the team. The owner's own machines need
+cancel the subscription first, then delete the team. The owner's own computers need
no approval. Admins cannot remove other admins or the owner.
Owners and admins remove a member in the Members list on the Team page. Removal
-takes effect at once, and the person's machine approvals for the team are deleted.
+takes effect at once, and the person's computer approvals for the team are deleted.
A member leaves with **Leave team** on the same page.
-## Team machines
+## Team computers
-A **team machine** belongs to the team. Every member, and their agents, sees it
-in the Cua Spaces app and can open it, from a machine an admin has approved. A
-**personal machine** stays on your own account, as described in
-[Add a machine](/spaces/guides/add-a-computer), and only you and the accounts
+A **team computer** belongs to the team. Every member, and their agents, sees it
+in the Cua Spaces app and can open it, from a computer an admin has approved. A
+**personal computer** stays on your own account, as described in
+[Add a computer](/spaces/guides/add-a-computer), and only you and the accounts
you [share it with](/spaces/guides/share-a-space) can reach it.
-| | Personal machine | Team machine |
+| | Personal computer | Team computer |
|---|---|---|
| Belongs to | One account | The team |
| Who sees it | You, and accounts you share it with | Every member |
-| Who can open it | You, and people you share it with | Every member, as an editor, from an approved machine |
+| Who can open it | You, and people you share it with | Every member, as an editor, from an approved computer |
| Who adds or removes it | You | Owners and admins |
-Team members have full use of a team machine: there are no view-only team
+Team members have full use of a team computer: there are no view-only team
members. To let someone only watch, share a Space with them as a viewer instead.
-### Pair a machine to the team
+### Pair a computer to the team
Pairing needs Cua Spaces 0.8.0 or later. An owner or admin does this.
-1. In the Cua Spaces app, open **Machines**, press **Add a machine** and choose
+1. In the Cua Spaces app, open **Computers**, press **Add a computer** and choose
your team next to **For** at the bottom of the sheet. Then pick **Open a
link**, **Scan a QR code**, **Run a command** or **Enter a code**. Each one
carries a one-time pairing code that looks like `K7QM-4XPB-2RHD`. For the
- personal version of these steps, see [Add a machine](/spaces/guides/add-a-computer).
-2. On the machine you are adding, open the link, or run the install command the
+ personal version of these steps, see [Add a computer](/spaces/guides/add-a-computer).
+2. On the computer you are adding, open the link, or run the install command the
app shows. With the `cua` CLI installed, the code alone is enough:
```bash test="cli-shape" id="cua-host-setup-pair-team"
cua host setup --pair K7QM-4XPB-2RHD
```
-If the machine already has the Cua Spaces app, you don't need the command:
-open **Add a machine** in the app there, choose **Have a code? Enter it**, and
+If the computer already has the Cua Spaces app, you don't need the command:
+open **Add a computer** in the app there, choose **Have a code? Enter it**, and
paste the code or the link. The app asks before it joins.
-The machine joins the team that made the code, with no sign-in on that machine.
+The computer joins the team that made the code, with no sign-in on that computer.
A code works once and expires after 30 minutes; while the sheet is open, it
renews by itself. Revoke an unused one from the sheet's **⋯** menu.
-The machine then appears under **Machines** at
+The computer then appears under **Computers** at
[app.cua.ai/machines](https://app.cua.ai/machines), where an owner or admin can
-remove it from the team. Removing a machine does not delete anything on it.
+remove it from the team. Removing a computer does not delete anything on it.
-Mac, Windows and Linux machines can all be team machines, and all join with
+Mac, Windows and Linux computers can all be team computers, and all join with
`cua host setup`. See [Install](/spaces/guides/install) to get the `cua` CLI.
-Members open team machines from the Cua Spaces app (macOS 26 or later) or the
+Members open team computers from the Cua Spaces app (macOS 26 or later) or the
Windows and Linux apps on the [download page](https://cua.ai/download).
-### Approve a machine
+### Approve a computer
-A member's machine can open team machines only once an owner or admin approves
+A member's computer can open team computers only once an owner or admin approves
it.
-1. The member opens a team machine from a new machine. That asks for approval
+1. The member opens a team computer from a new computer. That asks for approval
on its own (or run `cua team request <team>` to ask first).
-2. The machine shows as waiting for approval in the list at
+2. The computer shows as waiting for approval in the list at
[app.cua.ai/machines](https://app.cua.ai/machines). The member
sees that it is waiting for an admin.
-3. An owner or admin chooses **Approve** or **Deny**. A denied machine cannot open
- team machines.
+3. An owner or admin chooses **Approve** or **Deny**. A denied computer cannot open
+ team computers.
-Members see their own machines. Owners and admins see everyone's. Removing a
+Members see their own computers. Owners and admins see everyone's. Removing a
member deletes their approvals.
-### Who can open a team machine
+### Who can open a team computer
-A person can open a team machine when all of these hold. The relay checks them
+A person can open a team computer when all of these hold. The relay checks them
with the Cua account service and caches the answer for up to a minute.
- They are a member of the team. Their role is read from the team itself, so a
removed member loses access at once.
-- The machine is on the team's list.
-- Their machine is approved (the owner's machines always are).
+- The computer is on the team's list.
+- Their computer is approved (the owner's computers always are).
### Share a Space with the team
-To make a Space you already have a team machine, share it with the team. Every
-member of the team, and their agents, then sees it and can open it from a machine
+To make a Space you already have a team computer, share it with the team. Every
+member of the team, and their agents, then sees it and can open it from a computer
an admin has approved, either as **Can edit** (full control) or **Can view**
(watch only).
@@ -223,7 +223,7 @@ an admin has approved, either as **Can edit** (full control) or **Can view**
- **In a terminal:** run `cua spaces share <space> team:<team id>`, or
`cua team add-machine <team> <space>`. `cua team ls` shows the team ID.
- Only an owner or admin of the team can do this, and only for a Space they
- own. A team can hold as many shared machines as its seats allow.
+ own. A team can hold as many shared computers as its seats allow.
- Choose **Can view** or **Can edit** for the whole team. Share again with the
other role to change it.
- To stop, remove the team in the Share window, or run
@@ -254,7 +254,7 @@ See the [Plan Terms](https://cua.ai/spaces-terms) for the details.
Cancel Pro or Teams in the billing portal at any time. The plan stays active
until the end of the period you paid for, then you move to Free (a team moves to
-Free as a whole). Your Spaces and everything in them stay on your machines.
+Free as a whole). Your Spaces and everything in them stay on your computers.
Monthly plans have no refund for partial months. On a yearly plan, cancelling
within 14 days of the first yearly charge refunds it in full, and after that
diff --git a/docs/content/docs/spaces/guides/teleport-an-app.mdx b/docs/content/docs/spaces/guides/teleport-an-app.mdx
index e6f2d7b600..d945adc0a5 100644
--- a/docs/content/docs/spaces/guides/teleport-an-app.mdx
+++ b/docs/content/docs/spaces/guides/teleport-an-app.mdx
@@ -1,12 +1,12 @@
---
title: Teleport an app
-description: 'Bring an app from this machine into a Space: install it there, open your files in it, or move its signed-in state, with a consent screen for everything that leaves.'
+description: 'Bring an app from this computer into a Space: install it there, open your files in it, or move its signed-in state, with a consent screen for everything that leaves.'
---
import { Callout } from 'fumadocs-ui/components/callout';
import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
-**Teleport an app** lists every app installed on this machine and says what
+**Teleport an app** lists every app installed on this computer and says what
teleport can do with each one in a Space:
| Level | What happens in the Space | Moves |
@@ -32,10 +32,10 @@ cookies), **Saved passwords** and **Browsing history**. In the SDK these are
the entry's `sensitive_groups` and `TeleportPlanOptions.sensitive_groups`.
Chrome (and Chromium) encrypts cookies and saved passwords at rest with a
-per-machine **Safe Storage** key held in this Mac's login Keychain, so they
-cannot simply be copied to another machine. When **Keep me signed in** is
+per-computer **Safe Storage** key held in this Mac's login Keychain, so they
+cannot simply be copied to another computer. When **Keep me signed in** is
checked, teleport decrypts the cookies here (the OS asks you to allow that
-Keychain read) and carries the decrypted values, not the source machine's
+Keychain read) and carries the decrypted values, not the source computer's
key; the Space re-encrypts them under its own Safe Storage key before Chrome
ever reads them. The source's key never leaves this Mac.
@@ -258,8 +258,8 @@ cua teleport push --app com.google.Chrome --url http://10.0.0.5:3211 --token "$T
only. `--sandbox NAME` routes through your own [Cua Keyvault](/spaces/guides/keyvault)
(one combined Touch ID prompt for the whole capture-and-deliver, and nothing
raw ever leaves it). `--url` names a destination that is not one of your
-Spaces, such as another machine's address, and goes the same way: the Cua
-daemon on this machine reads the app, you approve it with the same Keyvault
+Spaces, such as another computer's address, and goes the same way: the Cua
+daemon on this computer reads the app, you approve it with the same Keyvault
prompt, it is recorded in the audit log, and the copy is wiped on the same
schedule. The destination is only where it goes, and it is not kept in your
Spaces afterwards. Because the daemon does the reading, macOS uses the Full
diff --git a/docs/content/docs/spaces/guides/troubleshoot.mdx b/docs/content/docs/spaces/guides/troubleshoot.mdx
index 614b5966c4..fda878f5c9 100644
--- a/docs/content/docs/spaces/guides/troubleshoot.mdx
+++ b/docs/content/docs/spaces/guides/troubleshoot.mdx
@@ -1,16 +1,16 @@
---
title: Troubleshoot
-description: 'Fix a Space that does not create (disk, container engine, virtualization, the two-VM limit, Local Network), find help for agents and machines that will not connect, and ask for help.'
+description: 'Fix a Space that does not create (disk, container engine, virtualization, the two-VM limit, Local Network), find help for agents and computers that will not connect, and ask for help.'
---
import { Callout } from 'fumadocs-ui/components/callout';
-Most problems are a Space that won't create, or an agent or machine that won't
+Most problems are a Space that won't create, or an agent or computer that won't
connect. This page covers a failed create in detail and points to the fix for the
rest.
<Callout type="info">
- If sign-in, connecting a machine or a download fails for everyone, check
+ If sign-in, connecting a computer or a download fails for everyone, check
[System status](https://status.cua.ai) first. We post outages and updates there.
</Callout>
@@ -25,7 +25,7 @@ time. Cua Spaces tries those once more by itself, and the Space says
**Retrying…** while it does. You only see the failure if the second try
fails too.
-When a Space fails twice in a row for the same reason, on the same machine
+When a Space fails twice in a row for the same reason, on the same computer
and with the same image, Cua Spaces shows the fix for that reason instead of
**Try again**: for example **Copy cua cache prune** when the disk is full, or
**Copy cua runtime doctor** when no container engine is running.
@@ -61,15 +61,15 @@ for the full list.
| The image download failed, was refused or stopped partway (`image_pull_network`, `image_pull_not_found`, `image_pull_auth`, `image_pull_rate_limited`, `image_pull`) | Check your network and try again. Finished image layers are kept, so the next attempt resumes. If the registry rate-limited you, wait a few minutes. If you use your own image, check its name and that you can pull it. |
| Not enough disk space (`insufficient_disk`) | The New Space screen shows how much space is needed and available. A macOS Space needs about 50 GB. Free some space, or delete Spaces you no longer need with `cua spaces delete`. |
| No container engine is running (`runtime_missing`, `runtime_not_running`, `runtime_permission`) | Start Docker Desktop, or install a container engine such as Docker, Colima or Podman. If the message says permission denied, give your user access to the engine. Run `cua runtime doctor` to check. |
-| This machine can't run virtual machines (`virtualization_unavailable`) | macOS Spaces need an Apple silicon Mac. On Linux and Windows, turn on hardware virtualization in the firmware settings. Or create a Linux container Space instead. |
+| This computer can't run virtual machines (`virtualization_unavailable`) | macOS Spaces need an Apple silicon Mac. On Linux and Windows, turn on hardware virtualization in the firmware settings. Or create a Linux container Space instead. |
| Two macOS VMs already run (`vm_limit`) | Apple allows two macOS VMs at a time on one Mac. Stop or delete one, then try again. |
| The VM started but never answered (`vm_boot_timeout`, `services_unreachable`) | The first macOS Space unpacks a large image and can run out of time. Try again: the image is already downloaded, so it is much faster. |
-| macOS blocked the connection to the new VM (`local_network`) | Open **System Settings, Privacy & Security, Local Network**, turn on Cua Spaces, then try again. If nobody sits at the Mac (you use it over SSH or from another machine), macOS can't ask: run the three commands in [Add a machine](/spaces/guides/add-a-computer#over-ssh-or-tailscale) once on it. |
+| macOS blocked the connection to the new VM (`local_network`) | Open **System Settings, Privacy & Security, Local Network**, turn on Cua Spaces, then try again. If nobody sits at the Mac (you use it over SSH or from another computer), macOS can't ask: run the three commands in [Add a computer](/spaces/guides/add-a-computer#over-ssh-or-tailscale) once on it. |
| "The Cua daemon isn't running. Start Cua, or run `cua daemon start`." | Open Cua Spaces, or run `cua daemon start`. |
-### Creating on another machine
+### Creating on another computer
-To create a Space on one of your other machines, that machine must be online,
+To create a Space on one of your other computers, that computer must be online,
provide Spaces, and be set up for your account. If the create fails with a name
such as `ambiguous_host` or `host_capability_missing`, see the
[spare Mac errors](/spaces/guides/add-a-computer#spare-mac-errors).
@@ -84,7 +84,7 @@ attempt resumes. See [Cancel a create](/spaces/guides/add-a-space#cancel-a-creat
Versions of Cua Spaces after 0.9.4 add **Send a report...** to a failed Space.
It builds a report from the error, the phase it failed in, the image and the app
-and system versions. Before anything leaves your machine:
+and system versions. Before anything leaves your computer:
- You review the report and can edit it or leave parts out.
- Cua removes tokens, email addresses, home folders, hostnames and public IP
@@ -106,11 +106,11 @@ system, and the Cua Spaces version from **Settings, About**.
| What you see | Where to look |
|---|---|
| The agent has no `cua` tools, or can't reach a Space | [If it doesn't work](/spaces/guides/connect-your-agent#if-it-doesnt-work) in Connect your agent |
-| A machine never appears, or shows **Offline** | [If it doesn't work](/spaces/guides/add-a-computer#if-it-doesnt-work) in Add a machine |
+| A computer never appears, or shows **Offline** | [If it doesn't work](/spaces/guides/add-a-computer#if-it-doesnt-work) in Add a computer |
| On Linux, Share fails at once with "user presence was not confirmed" | [Sharing on Linux](/spaces/guides/share-a-space) in Share a Space: install the latest .deb and use a desktop session with a polkit agent |
| An error name such as `capability_missing` or `permission_denied` | [Errors](/spaces/reference#errors) in the Spaces reference |
| You want Cua Spaces gone, or a clean reinstall | [Uninstall Cua Spaces](/spaces/guides/uninstall), then [Install](/spaces/guides/install) |
-| Sign-in, connecting a machine, downloads or billing fail for everyone, or the problem started suddenly | [System status](https://status.cua.ai): we post outages and updates there |
+| Sign-in, connecting a computer, downloads or billing fail for everyone, or the problem started suddenly | [System status](https://status.cua.ai): we post outages and updates there |
| Something else | Email [email protected] as described above |
## Next
diff --git a/docs/content/docs/spaces/guides/uninstall.mdx b/docs/content/docs/spaces/guides/uninstall.mdx
index aca942de3e..5aedf3dc44 100644
--- a/docs/content/docs/spaces/guides/uninstall.mdx
+++ b/docs/content/docs/spaces/guides/uninstall.mdx
@@ -7,8 +7,8 @@ import { Callout } from 'fumadocs-ui/components/callout';
import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
One command removes Cua Spaces, the `cua` CLI and what they set up on this
-machine. It lists what it found and asks before it removes anything. Run it
-again any time: a machine that has nothing left, or only part of Cua, is fine.
+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.
<Tabs items={['macOS and Linux', 'Windows']}>
<Tab value="macOS and Linux">
@@ -36,13 +36,13 @@ curl -fsSL https://cua.ai/uninstall.sh | sh -s -- --dry-run
- 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 machine no longer shows up
- as a machine in your account.
+- The host service, after `cua host remove`, so this computer no longer shows up
+ as a computer in your account.
- The Cua Spaces skills and the `cua` MCP server in your AI agents, the way
`cua connect remove` does. Entries from other tools stay, and so do Cua Driver's
`cua-driver` skill and MCP server (see [Other Cua tools](#other-cua-tools)).
- Launch at login.
-- Your sign-in and the machine key: macOS Keychain items (including the old
+- Your sign-in and the computer key: macOS Keychain items (including the old
`run.cua.ai` one), Windows Credential Manager entries.
- Cua's settings, caches and logs.
@@ -53,13 +53,13 @@ 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
-machine key) and the app's settings, for a later reinstall. Programs, services,
+computer 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
<Callout type="warn">
-`--delete-spaces` deletes the Spaces on this machine, the local Cua Volume files
+`--delete-spaces` deletes the Spaces on this computer, the local Cua Volume files
and the Keyvault. It cannot be undone.
</Callout>
diff --git a/docs/content/docs/spaces/guides/your-tailnet.mdx b/docs/content/docs/spaces/guides/your-tailnet.mdx
index 94f2131320..23de56dbbe 100644
--- a/docs/content/docs/spaces/guides/your-tailnet.mdx
+++ b/docs/content/docs/spaces/guides/your-tailnet.mdx
@@ -7,21 +7,21 @@ import { Callout } from 'fumadocs-ui/components/callout';
If your team already runs [Tailscale](https://tailscale.com) or a
self-hosted [Headscale](https://github.com/juanfont/headscale) network, a
-machine can host Spaces on that tailnet instead of the cua.ai relay. Your
+computer can host Spaces on that tailnet instead of the cua.ai relay. Your
tailnet then does the networking and decides who is who:
- **Identity.** A teammate is identified by their tailnet login (through
your identity provider and its SSO and MFA). They need no Cua env token.
-- **Access.** Your tailnet's ACLs decide which machines can reach the
- machine at all; the machine's share list decides what each user may do.
+- **Access.** Your tailnet's ACLs decide which computers can reach the
+ computer at all; the computer's share list decides what each user may do.
- **Rollout.** Your MDM or RMM installs the tailnet client as it already
does; Cua uses it, and never installs or reconfigures it.
-Nothing goes through cua.ai: no relay, no sign-in, no added machines.
+Nothing goes through cua.ai: no relay, no sign-in, no added computers.
-## Set the machine up
+## Set the computer up
-On the machine, with the tailnet client running and logged in (`tailscale
+On the computer, with the tailnet client running and logged in (`tailscale
up`, or `tailscale up --login-server https://headscale.example.com` for
Headscale):
@@ -29,10 +29,10 @@ Headscale):
cua host setup --tailnet --share spaces --allow [email protected]
```
-`--tailnet` serves on the machine's tailnet address (`tailscale ip -4`) on
+`--tailnet` serves on the computer's tailnet address (`tailscale ip -4`) on
port 3211 and identifies callers by their tailnet login:
-- the machine's own tailnet user owns it (full access, as with an env token);
+- the computer's own tailnet user owns it (full access, as with an env token);
- each `--allow` user can use it too;
- anyone else on the tailnet who can reach it still needs the env token.
@@ -50,10 +50,10 @@ change who may use it.
## How identity works
-For each call from a tailnet address, the machine asks the local tailnet
-client which user owns the calling machine (`tailscale whois`, the same
+For each call from a tailnet address, the computer asks the local tailnet
+client which user owns the calling computer (`tailscale whois`, the same
lookup `tailscale serve` uses). It never trusts a name the caller sends. A
-machine tagged by ACL (`tag:ci`) belongs to no user, so it needs the env
+computer tagged by ACL (`tag:ci`) belongs to no user, so it needs the env
token. Login names match the share list case-insensitively; with Headscale
they are the Headscale user names (`bob`), with Tailscale usually emails.
@@ -78,17 +78,17 @@ The same policy works in Headscale's ACL file.
| | Your tailnet (`--tailnet`) | The cua.ai relay and mesh (default) |
|---|---|---|
| Who runs the network | You (Tailscale or Headscale) | Cua, inside the app |
-| Identity | Your tailnet's logins and SSO | Your cua.ai account and added machines |
-| Access rules | Your tailnet ACLs plus the machine's share list | Owner, share lists and sharing switch |
+| Identity | Your tailnet's logins and SSO | Your cua.ai account and added computers |
+| Access rules | Your tailnet ACLs plus the computer's share list | Owner, share lists and sharing switch |
| Encryption | Your tailnet's WireGuard | Cua's [WireGuard®-based mesh](/spaces/guides/relay-security#end-to-end-encrypted-connections) |
| Browser viewer from anywhere | Only on the tailnet | Yes, through the relay |
-Both keep your traffic end to end encrypted. A machine set up on the cua.ai
+Both keep your traffic end to end encrypted. A computer set up on the cua.ai
relay also finds direct paths over your tailnet on its own when both ends
are on it: tailnet addresses are among the mesh's candidate paths.
<Callout type="warn">
- The machine's listener speaks plain HTTP inside the tailnet (the tailnet
+ The computer's listener speaks plain HTTP inside the tailnet (the tailnet
encrypts it). Keep `--tailnet` on the tailnet address it picks; do not
expose port 3211 on a public interface.
</Callout>
diff --git a/docs/content/docs/spaces/index.mdx b/docs/content/docs/spaces/index.mdx
index 48b6596ece..9a385ffce0 100644
--- a/docs/content/docs/spaces/index.mdx
+++ b/docs/content/docs/spaces/index.mdx
@@ -1,16 +1,16 @@
---
title: Cua Spaces
-description: 'Machines for you and your agents. Install the Cua Spaces app, connect an AI agent, and watch it work on a machine you own.'
+description: 'Computers for you and your agents. Install the Cua Spaces app, connect an AI agent, and watch it work on a computer you own.'
landing:
summary: 'Computers for you and your agents. Install the app, connect an agent and watch it work.'
cta: Explore Cua Spaces
---
-Cua Spaces gives your AI agents their own machines to work on, and lets you
-watch, step in and share them. You bring the machines: a Mac on your desk, a
+Cua Spaces gives your AI agents their own computers to work on, and lets you
+watch, step in and share them. You bring the computers: a Mac on your desk, a
spare Linux box, a VM in your own cloud account. Cua does not rent them.
-A **Space** is one desktop on one of those machines, set up for a task. Your
+A **Space** is one desktop on one of those computers, set up for a task. Your
agent runs commands in it and uses its apps and browser. You see the same
screen and take over when you want. You can share a Space with anyone who has
a cua.ai account, to watch it or to work in it. On the Teams plan you can also
@@ -22,8 +22,8 @@ share it with your whole team.
run a first task. About five minutes.
2. [Connect your agent](/spaces/guides/connect-your-agent): add Spaces to
Claude Code, Codex, Cursor and other agents.
-3. [Add a machine](/spaces/guides/add-a-computer): connect another Mac, Linux
- or Windows machine you own.
+3. [Add a computer](/spaces/guides/add-a-computer): connect another Mac, Linux
+ or Windows computer you own.
## What do you want to do?
@@ -31,7 +31,7 @@ share it with your whole team.
|---|---|
| Install on Mac, Windows or Linux | [Install](/spaces/guides/install) |
| Let my agent use Spaces | [Connect your agent](/spaces/guides/connect-your-agent) |
-| Use another machine I own, or reach my machines from my other machines | [Add a machine](/spaces/guides/add-a-computer) |
+| Use another computer I own, or reach my computers from my other computers | [Add a computer](/spaces/guides/add-a-computer) |
| Let someone else watch or work in a Space | [Share a Space](/spaces/guides/share-a-space) |
| Compare Free, Pro and Teams, or set up a team | [Plans and Teams](/spaces/guides/teams) |
| Fix a Space that won't create | [Troubleshoot](/spaces/guides/troubleshoot) |
diff --git a/docs/content/docs/spaces/quickstart.mdx b/docs/content/docs/spaces/quickstart.mdx
index d7320c13c2..ec7d8477b2 100644
--- a/docs/content/docs/spaces/quickstart.mdx
+++ b/docs/content/docs/spaces/quickstart.mdx
@@ -7,7 +7,7 @@ import { Callout } from 'fumadocs-ui/components/callout';
import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
In about five minutes you install Cua Spaces, connect your AI coding agent, make
-this machine your first Space and ask your agent to use it while you watch.
+this computer your first Space and ask your agent to use it while you watch.
<VideoDemo
src="https://trycua.github.io/assets/videos/cua-spaces/quickstart.mp4"
@@ -22,10 +22,10 @@ this machine your first Space and ask your agent to use it while you watch.
- A Mac (macOS 26 or later), a Windows PC (preview) or a Linux PC (Ubuntu 24.04).
- An AI coding agent, such as Claude Code, Codex or Cursor. See the
[supported agents](/cua-cli/guides/mcp-server#supported-agents).
-- A free Cua account, only to reach this machine from your other machines.
- Everything on this machine works without one.
+- A free Cua account, only to reach this computer from your other computers.
+ Everything on this computer works without one.
-Your machine is your first Space, so there is nothing big to download. An extra
+Your computer is your first Space, so there is nothing big to download. An extra
Space is optional: a Linux Space needs a container engine such as Docker, and a
macOS Space needs an Apple silicon Mac and about 50 GB of free disk.
@@ -60,25 +60,25 @@ has the details for each system.
## 2. Pick your agent
-Open Cua Spaces. The first screen says "Your machines, shared by your team and its agents."
+Open Cua Spaces. The first screen says "Your computers, shared by your team and its agents."
Press **Get started**.
-**Pick your agent** lists the agents found on this machine, such as Hermes,
+**Pick your agent** lists the agents found on this computer, such as Hermes,
Claude Code, Codex, Cursor or OpenClaw, each with the settings file Cua adds
itself to. Press **Connect** on each one you want to use. Nothing is connected
until you press it, and you can connect more later. Codex also shows its
**ChatGPT sign-in**, and Claude Code and Codex show the provider key they use
-in a Space; these stay on this machine.
+in a Space; these stay on this computer.
No agent found? The screen offers to install one, or to use the `cua` command
in a terminal instead. If your agent was already open, close it and open it
again so it loads the new tools. See [Connect your agent](/spaces/guides/connect-your-agent).
-## 3. Add your other machines (optional)
+## 3. Add your other computers (optional)
-**Sign in** lets your other machines and your cloud use this machine's
-Spaces, after you sign in on them too. The app then adds this machine to your
-account by itself. **Not now** keeps Cua on this machine only; **Sign in** at
+**Sign in** lets your other computers and your cloud use this computer's
+Spaces, after you sign in on them too. The app then adds this computer to your
+account by itself. **Not now** keeps Cua on this computer only; **Sign in** at
the bottom of the sidebar does it later.
## 4. Try it in your agent
@@ -89,7 +89,7 @@ The app names the agent you connected and gives you a request to paste into it:
Press **Copy**, paste it into your agent, and the agent makes the Space.
The line under it turns green when your agent has used Cua. On Windows and
-Linux the request says "this PC" or "this machine".
+Linux the request says "this PC" or "this computer".
With no agent connected, the screen offers a first Space instead: choose
**Linux** for the quickest one (a Mac with Apple silicon can also make a macOS
@@ -98,7 +98,7 @@ keeps getting made after the window closes, and you get a notice when it's
ready.
Press **Done** whenever you like. To let your agent control this Mac itself,
-open **Machines, This Mac**: it lists the two settings macOS asks for once.
+open **Computers, This Mac**: it lists the two settings macOS asks for once.
<Callout type="info">
Home's sidebar keeps a **Get started** list (for example "Get started 2/5").
@@ -109,7 +109,7 @@ open **Machines, This Mac**: it lists the two settings macOS asks for once.
## Next
-- [Add a machine](/spaces/guides/add-a-computer): use another machine you own.
+- [Add a computer](/spaces/guides/add-a-computer): use another computer you own.
- [Share a Space](/spaces/guides/share-a-space): let a teammate watch or work in it.
- [Plans and Teams](/spaces/guides/teams): what Free, Pro and Teams include.
- Using code instead? [Use Spaces from code](/spaces/guides/create-a-space-with-the-sdk).