Scale computer-use 2.0 with open-source drivers, cross-OS sandboxes, and benchmarks for training, evaluation, and data generation.
Rust agentai-agentapplecomputer-usecomputer-use-agentcontainerizationcuadesktop-automationhacktoberfestlumemacosmanusoperatorswiftvirtualizationvirtualization-frameworkwindowswindows-sandbox
docs(spaces): say "machine" everywhere and rewrite the machines concepts page (#6164)
ddupont2e4a874cb443
diff --git a/docs/content/docs/agents/add-a-machine.mdx b/docs/content/docs/agents/add-a-machine.mdxindex 85ca9ad7ba..7af562cc46 100644--- a/docs/content/docs/agents/add-a-machine.mdx+++ b/docs/content/docs/agents/add-a-machine.mdx@@ -1,6 +1,6 @@---title: Add a machine-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.'+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.'---Cua Spaces can't start this image on that cloud itself, so your user wants it run@@ -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 computer, add it with its address and the token. Keep the+3. From your user's machine, add it with its address and the token. Keep thetoken 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 computer from here. Tell your user the+You can't reach your user's cloud account or machine from here. Tell your user theimage, cloud and steps above, and ask them to run them or to paste this link into an-agent on their computer.+agent on their machine.## Check it worked@@ -61,5 +61,5 @@ firewall and the token, and try again. Don't open the port wider to make it pass- Your user can forget it with `cua spaces rm <name>`. That does not stop themachine: 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 computers or devices. How they differ:- [Computers, devices and Spaces](/spaces/concepts/computers-devices-and-spaces).+ your user's machines. How they differ:+ [Machines and Spaces](/spaces/concepts/machines-and-spaces).diff --git a/docs/content/docs/cua-cli/guides/authentication.mdx b/docs/content/docs/cua-cli/guides/authentication.mdxindex 1a216ab223..cd2f4cc4e3 100644--- a/docs/content/docs/cua-cli/guides/authentication.mdx+++ b/docs/content/docs/cua-cli/guides/authentication.mdx@@ -35,7 +35,7 @@ refresh automatically and are never printed.looks like a new app to the Keychain every time you rebuild it, so it uses thefile and never asks for Keychain access.-Older versions kept the session, the device key and the other secrets under the+Older versions kept the session, this machine's key and the other secrets under theservice `run.cua.ai` (`staging.run.cua.ai` for staging). The first `cua` thatreads them after you update moves each item to `ai.cua.session`, checks the newitem and then deletes the old one, so you stay signed in. A `cua` signed by Cuadiff --git a/docs/content/docs/cua-cli/guides/share-a-link.mdx b/docs/content/docs/cua-cli/guides/share-a-link.mdxindex acdef2dae9..6ad93f2677 100644--- a/docs/content/docs/cua-cli/guides/share-a-link.mdx+++ b/docs/content/docs/cua-cli/guides/share-a-link.mdx@@ -7,7 +7,7 @@ import { Callout } from 'fumadocs-ui/components/callout';import { Tab, Tabs } from 'fumadocs-ui/components/tabs';A `localhost` link only works on the machine that printed it. `cua share` gives-you a Cua link that opens on any of your signed-in devices, your phone+you a Cua link that opens on any of your signed-in machines, your phoneincluded. Coding agents use it when they start a preview, a dashboard or write areport: they hand you the link, not a port number.@@ -26,7 +26,7 @@ prints the share instead: `id`, `url`, `access`, `target`, `owner`,| Flag | Who | Ends || --- | --- | --- |-| none (private) | Only your cua.ai account, on any of your devices | Until you stop it |+| none (private) | Only your cua.ai account, on any of your machines | Until you stop it || `--team` | Members of your team, signed in | Until you stop it || `--public --ttl 1h` | Anyone with the link | After the TTL (60 s to 24 h, default 1 h) |diff --git a/docs/content/docs/cua-cli/index.mdx b/docs/content/docs/cua-cli/index.mdxindex 08402719f4..5411f7a8a7 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-computer-from-a-terminal) to this machine. |+| `cua host` | | [Unattended access](/spaces/guides/add-a-computer#add-a-machine-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.mdxindex d353daba6b..1d709502c1 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 yourselfOn a machine you own, `cua host setup` installs spacesd as a service-([Unattended access](/spaces/guides/add-a-computer#add-a-computer-from-a-terminal)). To run the binary by+([Unattended access](/spaces/guides/add-a-computer#add-a-machine-from-a-terminal)). To run the binary byhand:```bash skip="no-runner"diff --git a/docs/content/docs/cua-sdk/guides/your-cloud-without-a-key.mdx b/docs/content/docs/cua-sdk/guides/your-cloud-without-a-key.mdxindex 40e3222c47..21ae70a752 100644--- a/docs/content/docs/cua-sdk/guides/your-cloud-without-a-key.mdx+++ b/docs/content/docs/cua-sdk/guides/your-cloud-without-a-key.mdx@@ -5,7 +5,7 @@ description: Link Google Cloud or Azure to Cua with no stored key, through workl`cua cloud connect` can link AWS, Google Cloud and Azure with no key storedanywhere. Cua's issuer (`oidc.cua.ai`) signs a 15-minute token for your Cua-account each time a device needs the cloud, and your cloud trusts those+account each time a machine needs the cloud, and your cloud trusts thosetokens. AWS is in [Use your own cloud](/cua-sdk/guides/your-cloud#link-aws-without-a-key);Google Cloud and Azure are below. An agent can do all of it for you: see[Connect a cloud (for agents)](/spaces/guides/connect-a-cloud).@@ -31,7 +31,7 @@ creates:only its own name as the audience, and has the condition`assertion.sub=='account:<account>'`. It maps `google.subject` and`attribute.account` to the subject, and `attribute.device` and- `attribute.purpose` to the device and purpose of each token, which Cloud+ `attribute.purpose` to the machine and purpose of each token, which CloudAudit Logs show;- the custom role `cuaSpaces` with the[15 Compute Engine permissions](/cua-sdk/guides/your-cloud-safety#google-cloud)diff --git a/docs/content/docs/cua-sdk/guides/your-cloud.mdx b/docs/content/docs/cua-sdk/guides/your-cloud.mdxindex 75dcffb426..a9da9af9f6 100644--- a/docs/content/docs/cua-sdk/guides/your-cloud.mdx+++ b/docs/content/docs/cua-sdk/guides/your-cloud.mdx@@ -13,7 +13,7 @@ SDK calls and `cua-bench` runs work there, and you pay the cloud directly.Each sandbox dials out to the cua.ai relay as a machine of your account, sonothing in your cloud listens on the internet. Your laptop, your agents and theCua Spaces app reach it wherever they are. Streams, files and presence pass-through relay.cua.ai, and only your devices and the accounts you share a Space+through relay.cua.ai, and only your machines and the accounts you share a Spacewith can reach the sandbox. The guest holds only its own machine token, neveryour account credentials. An account holds at most 32 machines, and each cloudsandbox uses one until you delete it.@@ -32,10 +32,10 @@ sandbox uses one until you delete it.- **Google Cloud**: `gcloud auth login` and a project with the Compute EngineAPI enabled.- **Hetzner**: a project API token with Read & Write access. Hetzner has no- sign-in, so Cua seals the token to your devices (see- [Hetzner and Modal tokens](#hetzner-and-modal-tokens-sealed-to-your-devices)).+ sign-in, so Cua seals the token to your machines (see+ [Hetzner and Modal tokens](#hetzner-and-modal-tokens-sealed-to-your-machines)).- **Modal**: a profile in `~/.modal.toml` (`modal token new`), or its token- sealed to your devices.+ sealed to your machines.- **Azure**: nothing on this machine. Azure is always linked through Cua'ssign-in, with no key. See[Link a cloud without a key](/cua-sdk/guides/your-cloud-without-a-key#azure).@@ -105,9 +105,9 @@ how many machines run there.With `--oidc`, Cua stores no AWS credentials, on this machine or anywhereelse. Cua's issuer (`oidc.cua.ai`) signs a 15-minute token for your Cua-account each time a device needs AWS, and your AWS account trusts those tokens-through one CloudFormation stack, `cua-spaces`. Every signed-in device, and-every agent on those devices, can then use the link, so you link the account+account each time a machine needs AWS, and your AWS account trusts those tokens+through one CloudFormation stack, `cua-spaces`. Every signed-in machine, and+every agent on those machines, can then use the link, so you link the accountonce:```bash test="cli-shape" id="cua-cloud-connect-oidc"@@ -159,23 +159,23 @@ cua daemon that runs is older than the cua you call it from, a link with`--oidc` or a budget is refused with a message to update and restart thedaemon, instead of falling back to the CLI sign-in.-### Hetzner and Modal tokens, sealed to your devices+### Hetzner and Modal tokens, sealed to your machinesHetzner and Modal have no OIDC, so they need an API token. Cua seals it to-your devices, and you give it once for all of them:+your machines, and you give it once for all of them:```bash test="cli-shape" id="cua-cloud-connect-hetzner-sealed"cua cloud connect hetzner --token-stdin --region fsn1 --budget 50 --max-size 4x8cua cloud connect modal --token-stdin --budget 50```-Cua checks the token first and creates nothing. Your device encrypts it with+Cua checks the token first and creates nothing. Your machine encrypts it withyour account's pool key, so Cua's servers keep only ciphertext, and any of-your devices opens it in memory when it calls the cloud. `cua cloud status+your machines opens it in memory when it calls the cloud. `cua cloud statushetzner` lists the devices that can open it. On another device, `cua cloudconnect hetzner --sealed --budget 50` links the same token without pasting-it. `--no-sealed` keeps the Hetzner token on this device only. Replacing,-revoking and removed devices are covered in+it. `--no-sealed` keeps the Hetzner token on this machine only. Replacing,+revoking and removed machines are covered in[Connect a cloud](/spaces/guides/connect-a-cloud#hetzner-and-modal).## Create sandboxes and Spaces@@ -317,8 +317,8 @@ its disk.- Give the token to `cua cloud connect hetzner` on standard input(`--token-stdin`) or in `HCLOUD_TOKEN`; the `hcloud` CLI's active contextalso works. Only a token that passes the checks is used. It is- [sealed to your devices](#hetzner-and-modal-tokens-sealed-to-your-devices),- or with `--no-sealed` saved in this device's credential store (the system+ [sealed to your machines](#hetzner-and-modal-tokens-sealed-to-your-machines),+ or with `--no-sealed` saved in this machine's credential store (the systemvault on a Cua-signed Mac, a private file in the cua home elsewhere),never in `config.toml`.- **Container images only.** Hetzner Cloud servers have no `/dev/kvm`, so@@ -339,7 +339,7 @@ its disk.- **Modal**:- One environment per connection (`--environment`) and a `~/.modal.toml`profile (`--profile`), or a token- [sealed to your devices](#hetzner-and-modal-tokens-sealed-to-your-devices)+ [sealed to your machines](#hetzner-and-modal-tokens-sealed-to-your-machines)(`--token-stdin`, given as `<token id>:<token secret>`).- Sandboxes run under gVisor by default. `--runtime microvm` uses Modal's VMruntime. Neither has `/dev/kvm`, so only Linux images run.diff --git a/docs/content/docs/index.mdx b/docs/content/docs/index.mdxindex 6f8be00d2b..041665b834 100644--- a/docs/content/docs/index.mdx+++ b/docs/content/docs/index.mdx@@ -1,6 +1,6 @@---title: Cua Docs-description: 'Give your agents their own computers with Cua Spaces. Watch them work, step in when you want, and share with your team.'+description: 'Give your agents their own machines with Cua Spaces. Watch them work, step in when you want, and share with your team.'landing:hero: Cua Docspath: 'Start with the Cua Spaces quickstart. It takes about five minutes.'@@ -32,7 +32,7 @@ import { Card, Cards } from 'fumadocs-ui/components/card';<Cards><Card title="Cua Spaces" href="/spaces">- Computers for you and your agents. Install the app, connect an agent and watch it work. Start with the five-minute [quickstart](/spaces/quickstart).+ Machines for you and your agents. Install the app, connect an agent and watch it work. Start with the five-minute [quickstart](/spaces/quickstart).</Card><Card title="Cua Driver" href="/cua-driver">Let an agent use the apps on your computer in the background, on macOS, Windows and Linux. Start with the [quickstart](/cua-driver/quickstart).@@ -43,8 +43,8 @@ import { Card, Cards } from 'fumadocs-ui/components/card';- [Quickstart](/spaces/quickstart): install the app, connect your agent and run a first task in about five minutes.- [Connect your agent](/spaces/guides/connect-your-agent): add Spaces to Claude Code, Codex, Cursor and other agents.-- [Add a computer](/spaces/guides/add-a-computer): connect another Mac, Linux or Windows computer you own.-- [Teams](/spaces/guides/teams): share computers with your team, and what each plan includes.+- [Add a machine](/spaces/guides/add-a-computer): connect another Mac, Linux or Windows machine you own.+- [Teams](/spaces/guides/teams): share machines with your team, and what each plan includes.- [How Spaces works](/spaces/concepts/how-spaces-works): what runs where, in plain words.## Cua Driver@@ -67,7 +67,7 @@ import { Card, Cards } from 'fumadocs-ui/components/card';## Examples-- [Cua Bots](/spaces/examples/cua-bots): bots that each have their own computer, in a Mac and iPhone app. The same kind of app in TypeScript, Rust and Swift is in [Use Spaces from code](/spaces/guides/create-a-space-with-the-sdk).+- [Cua Bots](/spaces/examples/cua-bots): bots that each have their own machine, in a Mac and iPhone app. The same kind of app in TypeScript, Rust and Swift is in [Use Spaces from code](/spaces/guides/create-a-space-with-the-sdk).- [Background computer use with Cua Driver](/cua-driver/guides/recipes): your agent builds and tests a Windows app while you keep working ([video](https://x.com/trycua/status/2059688966085853245)).diff --git a/docs/content/docs/redirects.json b/docs/content/docs/redirects.jsonindex 89a79a3ec7..4391fb4994 100644--- a/docs/content/docs/redirects.json+++ b/docs/content/docs/redirects.json@@ -287,9 +287,10 @@"how-to-guides/sandbox/troubleshoot-fleet-pools": "cua-sdk/guides/cua-cloud-ended","how-to-guides/sandbox/tunneling": "cua-sdk/guides/services","spaces/agents": "spaces/guides/agents-from-a-link",+ "spaces/concepts/computers-devices-and-spaces": "spaces/concepts/machines-and-spaces","how-to-guides/spaces/add-a-space": "spaces/guides/add-a-space","how-to-guides/spaces/install-cua": "spaces/quickstart",- "how-to-guides/spaces/set-up-unattended-access": "spaces/guides/add-a-computer#add-a-computer-from-a-terminal",+ "how-to-guides/spaces/set-up-unattended-access": "spaces/guides/add-a-computer#add-a-machine-from-a-terminal","how-to-guides/spaces/stream-a-desktop": "spaces/guides/stream-a-desktop","how-to-guides/spaces/teleport-an-app": "spaces/guides/teleport-an-app","how-to-guides/spaces/use-spaces-from-an-agent": "spaces/guides/connect-your-agent#what-your-agent-can-do",@@ -400,7 +401,7 @@"reference/sandbox-sdk/runtime-support": "cua-sdk/reference/runtime-support","reference/sandbox-sdk/typescript": "cua-sdk/reference/typescript","sandboxes": "cua-sdk",- "spaces/guides/set-up-unattended-access": "spaces/guides/add-a-computer#add-a-computer-from-a-terminal",+ "spaces/guides/set-up-unattended-access": "spaces/guides/add-a-computer#add-a-machine-from-a-terminal","spaces/guides/use-spaces-from-an-agent": "spaces/guides/connect-your-agent#what-your-agent-can-do","tutorials": "","start-here": "spaces/quickstart",@@ -446,7 +447,7 @@"cua-sdk/reference/spaces/app-core/keyvault": "cua-sdk/reference/spaces/keyvault-app-core","cua-sdk/reference/spaces/app-core/keyvault-screens": "cua-sdk/reference/spaces/keyvault-app-core/screens","spaces/teams": "spaces/guides/teams",- "spaces/teams/machines": "spaces/guides/teams#team-computers",+ "spaces/teams/machines": "spaces/guides/teams#team-machines","spaces/teams/faq": "spaces/guides/teams#questions","cua-cli/reference/cli/fleet": "cua-sdk/guides/cua-cloud-ended","cua-sdk/guides/cloud": "cua-sdk/guides/cua-cloud-ended",@@ -471,13 +472,13 @@"lume/guides/api-and-mcp": "lume/guides/manage-vms#drive-lume-from-scripts-and-ai-clients","cua-bench/guides/convert-benchmark-images": "cua-bench/guides/benchmarks#build-a-benchmark-image","spaces/guides/add-a-machine": "spaces/guides/add-a-computer",- "spaces/guides/unattended-access": "spaces/guides/add-a-computer#add-a-computer-from-a-terminal",+ "spaces/guides/unattended-access": "spaces/guides/add-a-computer#add-a-machine-from-a-terminal","spaces/guides/host-spaces-on-your-spare-mac": "spaces/guides/add-a-computer#use-a-spare-mac-to-host-spaces","spaces/guides/updates": "spaces/guides/install#updates","spaces/guides/use-from-an-agent": "spaces/guides/connect-your-agent#what-your-agent-can-do","spaces/guides/agent-keys": "spaces/guides/connect-your-agent#agent-keys","spaces/guides/plans": "spaces/guides/teams#plans",- "spaces/guides/teams/machines": "spaces/guides/teams#team-computers",+ "spaces/guides/teams/machines": "spaces/guides/teams#team-machines","spaces/guides/teams/faq": "spaces/guides/teams#questions","spaces/guides/send-files": "spaces/guides/cua-volume#send-a-file-into-a-space","spaces/guides/site-login": "spaces/guides/keyvault#let-an-agent-sign-in-to-a-site",diff --git a/docs/content/docs/spaces/concepts/computers-devices-and-spaces.mdx b/docs/content/docs/spaces/concepts/computers-devices-and-spaces.mdxdeleted file mode 100644index df5bfcaa01..0000000000--- a/docs/content/docs/spaces/concepts/computers-devices-and-spaces.mdx+++ /dev/null@@ -1,33 +0,0 @@-----title: Computers, devices and Spaces-description: 'The difference between a signed-in device, a machine, its shared desktop and a sandbox Space, and why one computer can show up twice.'------One computer can be both a device you connect from and a machine that runs-Spaces. These names describe different roles:--| Name | What it is | Where you see or use it |-| --- | --- | --- |-| Signed-in device | A computer enrolled to reach your account's machines, once, with a second factor. Signing in does not make it a host. | The **Machines** tab (a machine that is only signed in shows as **Signed in, not sharing**) or `cua devices ls`, with an id such as `dev_…`. |-| Machine | A computer set up with **Add a computer** or `cua host setup` to share its desktop, provide Spaces, or both. | The **Machines** tab. When **Provide Spaces** is on, `--on host:<machine-id>` creates new Spaces on it. |-| The machine's shared desktop | The computer's own screen, input, shell and files as a Space, while **Share this desktop** is on. It is not a sandbox. | `relay:<machine-id>` for a computer set up on the relay. A direct host (set up with `--direct`, no relay record) is its own `direct:<host:port>` Space, added with `cua spaces add <host:port> --host`. For a relay computer, its row on **Machines** says **Desktop shared**, or **Desktop and 2 Spaces** when it also runs Spaces; the desktop is not counted among them. |-| Sandbox Space | A container, VM or microVM created for work, on this computer or on a machine that provides Spaces. See [Space kinds](/spaces/concepts/space-kinds). | `local:<name>` on this computer. On a relay machine that provides Spaces it has its own `relay:` id, with `host` naming the computer that runs it. On a direct host (set up with `--direct`, no relay) it has a `direct:<host:port>` id, whether created on that host or added by address. |--**Share this desktop** and **Provide Spaces** are separate settings. Hosting-alone never enrolls a computer as a device: a computer that only hosts joins-with its own token and can't reach your other computers.--## Why one computer can show up twice--A computer set up with `cua host setup` on the relay has a machine record. (A direct host, set up with `--direct` and no relay, has no relay record and is listed from your laptop's own host list.) Signing in on-that computer, in the app or with `cua auth login`, also gives it a device-record. The relay keeps the two apart and doesn't link them: they are one-computer in two roles, not two computers.--The **Machines** 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. A row that is only signed in-(**Signed in, not sharing**) is not a host, so **Run on** in **New Space** never offers it.--See [Add a computer](/spaces/guides/add-a-computer) for the two settings and-[How Spaces works](/spaces/concepts/how-spaces-works#space-ids) for Space ids.diff --git a/docs/content/docs/spaces/concepts/how-spaces-works.mdx b/docs/content/docs/spaces/concepts/how-spaces-works.mdxindex e595a98529..cb9978665d 100644--- a/docs/content/docs/spaces/concepts/how-spaces-works.mdx+++ b/docs/content/docs/spaces/concepts/how-spaces-works.mdx@@ -1,32 +1,31 @@---title: How Spaces works-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.'+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.'----Cua Spaces connects three things: the computers you own, the Spaces on them, and+Cua Spaces connects three things: the machines you own, the Spaces on them, andthe people and agents who use those Spaces.-## Computers and Spaces+## Machines and Spaces-A **computer** is a Mac, Windows or Linux computer-you own or rent. A **Space** is one desktop on a computer, set up for a task. A-Space is a container, a VM or a microVM, or the computer's own desktop. See-[Space kinds](/spaces/concepts/space-kinds).+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+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+and [Space kinds](/spaces/concepts/space-kinds) for the kinds.-A computer you also sign in on is a device too, a separate record, so one-computer can show up twice. See-[Computers, devices and Spaces](/spaces/concepts/computers-devices-and-spaces).--Cua doesn't rent computers. You bring them, and your cloud provider bills you for+Cua doesn't rent machines. You bring them, and your cloud provider bills you forany VM you run in your own account. Cua provides the app, sharing and the relay-that lets your devices reach your computers.+that lets your machines reach each other.## Where a Space runs| Location | What it is ||---|---|-| 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). |+| 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). || 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@@ -37,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 device connects to+- **Directly.** On the same network, or over Tailscale, your machine connects tothe Space with its address and a token. No account is needed, and the trafficdoesn't use the relay.-- **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 enrolled- devices, and people you share a Space with, reach it through the relay. Relay+- **Through the relay.** A machine 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. Relayuse counts toward your [plan's](/spaces/guides/teams#plans) live sessions andremote hours.@@ -53,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 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 |+| 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 |The app, the `cua` CLI, the SDKs and `cua daemon` share one registry-(`~/.cua/spaces.json`). Relay computers come from your account's directory and+(`~/.cua/spaces.json`). Relay machines come from your account's directory andare never written to `spaces.json`.## Who can do what-You own your computers and the Spaces on them. You can+You own your machines 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 computer can belong to the+an editor, and with [Teams](/spaces/guides/teams) a machine can belong to theteam instead of one person. Your agents act through the `cua` MCP server, and youchoose 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.mdxnew file mode 100644index 0000000000..16676feb0e--- /dev/null+++ b/docs/content/docs/spaces/concepts/machines-and-spaces.mdx@@ -0,0 +1,67 @@+---+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.'+---++Cua Spaces has two things to know: **machines** and **Spaces**. A machine+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`. |++## One list of machines++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.++The state on a row is one of these:++- **Online** or **Offline**.+- **Desktop shared**, or **Desktop and 2 Spaces** when it also provides Spaces.+ 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**.++Machines you have not seen for 30 days collapse into **Offline for 30+ days**,+and machines your team shares appear under **Team machines**.++Open a machine 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.++## What a machine provides++Two switches decide what a machine 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+ 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+that shares nothing is simply signed in.++## One machine, 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+`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+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.++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.++See [Add a machine](/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/meta.json b/docs/content/docs/spaces/concepts/meta.jsonindex 9384535dd8..b2d929697c 100644--- a/docs/content/docs/spaces/concepts/meta.json+++ b/docs/content/docs/spaces/concepts/meta.json@@ -2,7 +2,7 @@"title": "Concepts","pages": ["how-spaces-works",- "computers-devices-and-spaces",+ "machines-and-spaces","space-kinds"]}diff --git a/docs/content/docs/spaces/concepts/space-kinds.mdx b/docs/content/docs/spaces/concepts/space-kinds.mdxindex b39bbd1bfb..6e4ebd5dfe 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 computers 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 machines 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 computer it runs on, how fast it starts, and which images it runs.+from the machine 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-computers. Use a VM for Windows or macOS, or a full Linux desktop OS. Use a+machines. Use a VM for Windows or macOS, or a full Linux desktop OS. Use amicroVM to run any Linux image, such as untrusted code, behind its own kernel.-## Which computers run which kind+## Which machines run which kind-| Computer | `container` | `vm` | `microvm` |+| Machine | `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,9 +64,9 @@ The microVM runtimes:An [egress policy](/cua-sdk/guides/egress) is enforced on FirecrackermicroVMs. On `vz` and Containerization microVMs it is refused.-### Your own cloud and your other computers+### Your own cloud and your other machines-- **Another of your computers** runs the kinds it reports to your account.+- **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 machinetypes Cua offers, only bare metal (`c6g.metal`) has it. A metal machine costsdollars an hour, so a single small request is refused unless you allow it@@ -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 computer can accelerate them, else+`cua compat serve` makes VMs where this machine can accelerate them, elsecontainers.## Pick a kind@@ -158,10 +158,10 @@ const sb = await embedded().sandboxes().create(In Cua Spaces, press **New Space**, then open **Advanced** in **Choose asystem**. **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 computer.+the engine: for a microVM, the microVM runtimes ready on this machine.-**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+**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 whenit 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.`). Theapp sends the same `kind="microvm"` as the CLI.diff --git a/docs/content/docs/spaces/guides/add-a-computer.mdx b/docs/content/docs/spaces/guides/add-a-computer.mdxindex 5e77e554ac..311e75d8f9 100644--- a/docs/content/docs/spaces/guides/add-a-computer.mdx+++ b/docs/content/docs/spaces/guides/add-a-computer.mdx@@ -1,70 +1,70 @@----title: Add a computer-description: 'Connect another Mac, Windows or Linux computer 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 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.'---import { Callout } from 'fumadocs-ui/components/callout';-A computer you add runs Spaces for you. Once it is added, it shows up in+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 youcan open its desktop from anywhere, even when nobody is sitting at it. Cua-doesn't rent computers: add a Mac on your desk, a spare box in the office, or a+doesn't rent machines: add a Mac on your desk, a spare box in the office, or aVM in your own cloud account. For a walkthrough of each, see[Bring your own compute](/spaces/guides/bring-your-own-compute).-+-## Add a computer from the app+## Add a machine from the appIn Cua Spaces, open **Machines** and press **Add a machine**. You can alsofind it in the command palette. The sheet-lists the ways to add one; pick the one that suits the other computer.+lists the ways to add one; pick the one that suits the other machine.-| Way | What to do on the other computer |+| Way | What to do on the other machine ||---|---|-| **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. |+| **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. || **Run a command** | Run the command in a terminal. **macOS / Linux** and **Windows (preview)** each have their own. |-| **Enter a code** | For a computer 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 machine that already has Cua Spaces. There, open **Add a machine**, 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-computer** into an AI agent running there. It carries the same one-time code.+machine** into an AI agent running there. It carries the same one-time code.-The sheet waits for the computer and then says **Added** with its name,+The sheet waits for the machine and then says **Added** with its name,whichever way you used. The link, code, command and prompt work once andexpire 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 nextto **For** at the bottom of the sheet. See-[Team computers](/spaces/guides/teams#team-computers).+[Team machines](/spaces/guides/teams#team-machines).A `cua://add/<code>` link opens **Enter a code** with the code filled in. The-app asks before this computer joins.+app asks before this machine joins.<Callout type="warn">- Only use a code you made yourself. Joining adds the computer to the account+ Only use a code you made yourself. Joining adds the machine to the accountthat made the code, and that account can then reach it.</Callout>-A computer added from this sheet, or by signing in, provides Spaces and keeps+A machine added from this sheet, or by signing in, provides Spaces and keepsits screen private. Turn off **Let other machines create Spaces here** in**Settings** to stop it running Spaces for you, and turn on **Let othermachines control this desktop** on its page under **Machines** to see andcontrol its screen from your other machines. With both off, the machine simplyisn't shared.-## Add a computer from a terminal+## Add a machine from a terminal-If you can't use the link, set the computer up yourself:+If you can't use the link, set the machine 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 computer to+2. Sign in with the same account you use here. Signing in adds the machine tothat account. The installer does the same after it signs you in; add- `--no-host` to sign in without adding the computer.+ `--no-host` to sign in without adding the machine.-Or run this in a terminal on that computer:+Or run this in a terminal on that machine:```bash test="cli-shape" id="cua-host-setup-add"cua host setup # signs in to cua.ai for this command if needed@@ -72,30 +72,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 itjoins the cua.ai relay with an outbound connection, as your account: no port-forwarding and no token to copy. Your other devices, once-[enrolled](#reach-it-from-your-other-machines), then see the computer as+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`relay:<machine-id>` in `cua spaces ls` and in the app.-The computer keeps only its own token. If it is not signed in, setup+The machine keeps only its own token. If it is not signed in, setupsigns you in for that one command and stores no session, so a dedicated host-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 enroll devices. Running `setup` again updates the configuration+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 configurationand rotates the token.| Option | Effect ||--------|--------|-| `--remote` | When sign-in is needed, print a device code to approve in a browser on another computer (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 machine (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 computer shares: `desktop` (this desktop only), `spaces` (create Spaces for your devices 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. |+| `--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. |## What each system needs-| System | Service setup installs | Before the computer is reachable |+| System | Service setup installs | Before the machine 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. |@@ -103,7 +103,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 devices reach the+On Windows the host runs in your signed-in session, so your machines reach thedesktop only while it is signed in, unlocked and on screen:- **After a restart**, sign in once (or turn on automatic sign-in). The host@@ -120,40 +120,50 @@ A viewer or agent that connects in one of these states sees which one it is.## Reach it from your other machines-A device reaches your computers through the cua.ai relay only after it is-enrolled once with a second factor, so a stolen account session alone is not-enough. A computer that only hosts is never enrolled as a client.--- **Sign in.** Signing in on your own computer enrolls it: run- `cua devices enroll` right after `cua auth login`. A device that enrolled- before enrolls again on its own when you sign in again.-- **Approve.** A brand-new device on an account that already has an enrolled- device needs approval from one of them (or a sign-in whose token itself- proves a second factor with your identity provider). `cua devices enroll`- shows a one-time code. Approve it on an enrolled device with- `cua devices approve <code>`, or in the app, which asks for Touch ID.--Every enrolled device is notified when a new one joins, in the app's-notification feed and in `cua devices audit`, so a device you don't recognize-doesn't slip in unnoticed. Enrollment lasts 30 days. After that, a fresh-sign-in or one approval re-verifies the device. Until then, unattended agents on-an enrolled device keep working without prompts.+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+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.++- **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+ you added before checks itself again when you sign in again.+- **Approve.** A new machine on an account that already has an added machine+ 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+ 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+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+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**.```bash test="cli-shape" id="cua-devices"cua devices enrollcua devices approve K7QX-M2RPcua devices approve dev_0123456789abcdef01234567cua devices ls-cua devices audit # who opened which machine, from which device, and when+cua devices audit # who opened which machine, from which machine, and whencua devices revoke dev_0123456789abcdef01234567```-A machine that is gone: `cua machines rm <name>` removes it from your relay directory and revokes its device.+A machine 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 at the top-with **Add machine** and **Not me** (Add machine asks for Touch ID or your login password first, and-Not me refuses it), and the sidebar shows how many wait. Each machine's page has Rename, Revoke and-its recent access (who opened it, and when), and this machine's Details say how far it is trusted.+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+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.## Keep a desktop in the notch@@ -175,7 +185,7 @@ app's settings on that Mac.## Share it with your team-`--allow` at setup, or later from an enrolled device, shares the computer with+`--allow` at setup, or later from an added machine, shares the machine withsomeone in your team (id or verified email). Sharing is for teams: you need ateam, 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.@@ -193,7 +203,7 @@ cua host unshare [email protected]## Check, pause or remove-On the computer, run:+On the machine, run:```bash test="cli-shape" id="cua-host-status"cua host status # setup, service, who is connected; missing permissions@@ -204,16 +214,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 relayis unreachable. In direct mode, `cua host status` prints the URL and the path of-the env token. Add the computer elsewhere with-[`spaces.add(url, token)`](/spaces/guides/add-a-space#add-an-existing-computer-by-address).+the env token. Add the machine elsewhere with+[`spaces.add(url, token)`](/spaces/guides/add-a-space#add-an-existing-machine-by-address).Uninstalling the app turns sharing off too. On Linux, `sudo apt remove cua-spaces`-(and `purge`) removes the computer, and the Spaces it provides, from the relay,+(and `purge`) removes the machine, 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 computer (the Spaces are turned off).+Spaces and data under `~/.cua` stay on the machine (the Spaces are turned off).-An owner or admin can remove a team computer at-[app.cua.ai/machines](https://app.cua.ai/machines). Removing a computer doesn't+An owner or admin can remove a team machine at+[app.cua.ai/machines](https://app.cua.ai/machines). Removing a machine doesn'tdelete anything on it.## Use a spare Mac to host Spaces@@ -222,7 +232,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 themwith its own runtimes, Lume for macOS VMs and Docker for Linux. Its own desktop,-shell and files stay private. To share a computer's own desktop instead, use the+shell and files stay private. To share a machine's own desktop instead, use thesteps above.### Set up the spare Mac@@ -235,7 +245,7 @@ cua host setup --share spaces --name "Mac mini (spare)"`--share spaces` shares no desktop and provides Spaces. Setup joinsthe relay the way the steps above do. It signs you in for that one command and-keeps no account session, only the computer's own token.+keeps no account session, only the machine'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):@@ -243,25 +253,25 @@ 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 andnever holds the keys.-For how this computer, its device record and its Spaces fit together, see-[Computers, devices and Spaces](/spaces/concepts/computers-devices-and-spaces).+For how a machine, its shared desktop and its Spaces fit together, see+[Machines and Spaces](/spaces/concepts/machines-and-spaces).-The computer has two settings, and each works on its own:+The machine has two settings, and each works on its own:| Setting | What it does | Default | `--share spaces` ||---|---|---|---|-| Let other machines control this desktop (`--desktop`) | The computer itself is a Space: its screen, input, shell and files. | on | off |-| Let other machines create Spaces here (`--provide-spaces`) | Your trusted machines can create, list and delete Spaces on it. | on for a new setup | on |+| 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 |-A computer set up before this default keeps what it had: setting it up again-never turns **Provide Spaces** on unless you pass `--share spaces` or `--share both`. With-**Provide Spaces** on, your devices (and teammates you share the computer with+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 withas 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 Provide Spaces+macOS VMs on a Mac. Nothing runs until a Space is created. When **Let other machines create Spaces here**turns on in the Cua Spaces app, the app asks for macOS Local Network access onthat Mac (click **Allow** when macOS asks), which macOS Spaces your other-devices create there need. With **Share this-desktop** off, a relayed caller reaches only the Spaces service. Change either+machines create there need. With **Let other machines control this desktop**+off, a relayed caller reaches only the Spaces service. Change eithersetting at any time:```bash test="cli-shape" id="cua-host-config"@@ -272,8 +282,8 @@ cua host config --max-memory 32 --max-disk 200 # at most 32 GB of memory andcua host config --max-run-time 480 # a Space made here stops after 8 hours```-The app's **This computer** page has the same two switches, the Spaces the-computer provides, and every remote create and delete.+The app's **This machine** page has the same two switches, the Spaces the+machine provides, and every remote create and delete.### Over ssh or Tailscale@@ -294,14 +304,14 @@ curl -fsSL https://cua.ai/install.sh | sh -s -- -y --select spaces,host --no-onb`-y` accepts the install without the checklist, `--select spaces,host` picks theCua Spaces app and hosting, and `--no-onboarding` skips the automatic`cua auth login` (there is no browser to sign in with yet). Then set up the host-with a device code:+with a sign-in code:```bash test="cli-shape" id="cua-host-setup-spare-ssh"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 device. The sign-in is held only for+that you approve in a browser on another machine. The sign-in is held only forsetup. An existing account session is reused.<Callout type="warn">@@ -320,7 +330,7 @@ setup. An existing account session is reused.seconds and says so. Allow it once from the SSH session instead (Appledocuments 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- computers, and it needs a restart:+ machines, and it needs a restart:```sh skip="no-runner"sudo defaults write com.apple.network.local-network AllowedEthernetLocalNetworkAddresses -array 192.168.64.0/24@@ -331,8 +341,7 @@ setup. An existing account session is reused.### Create Spaces on it from your laptop-Your laptop must be [enrolled](#reach-it-from-your-other-machines) for your-account. Then ask your coding agent, through the cua MCP server:+Your laptop must be [added to your account](#reach-it-from-your-other-machines). Then ask your coding agent, through the cua MCP server:> spin up 2 macos spaces on my spare mac mini@@ -346,12 +355,12 @@ cua spaces create linux --on host:0123abcd4567ef89The SDK takes the same `on`: `spaces.create(on="host:spare mac mini", image="macos")`.-The computer is matched by its ID, its exact name, or the words of its name, so+The machine 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-computers fit equally well, the call fails with `ambiguous_host` and lists them+machines fit equally well, the call fails with `ambiguous_host` and lists themwith their IDs, so the agent can ask you which one you meant.-Each new Space joins the relay as a computer of its own and comes back as+Each new Space joins the relay as a machine of its own and comes back as`relay:<machine>`. Open it, stream it and run commands in it like any otherSpace.@@ -362,9 +371,9 @@ cua spaces lscua spaces delete relay:space-0123456789abcdef```-`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+`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, andthe Space leaves the relay.### Limits@@ -377,7 +386,7 @@ the Space leaves the relay.| 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. |-The limits count only the Spaces other machines create on this computer, not the+The limits count only the Spaces other machines create on this machine, not theones you make here yourself. They apply to everyone who asks: another machine, anagent, or a Space that overflows from a tree of Spaces. A create past a limit isrefused with "<machine> has no room for another Space", and `on="auto"` picks@@ -396,29 +405,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 device enrolled for your account.-- Accounts you share the computer with as editors (`cua host share` or+- You, from any machine added to your account.+- Accounts you share the machine with as editors (`cua host share` or`cua spaces share relay:<machine> <who> --role editor`). They see and deleteonly the Spaces they created. You see and delete all of them.-- Nobody else. The relay refuses a device that is not enrolled, and the computer+- Nobody else. The relay refuses a machine that is not added to the account, and the machinerefuses an account shared as a viewer.-Every remote create, delete and refusal is a line in the computer's hash-chained+Every remote create, delete and refusal is a line in the machine's hash-chainedaudit log (`~/.cua/host/spaces-audit.jsonl`). `cua host status` and the app showit, and warn when the log does not verify.-Agents follow [per-agent computer access](/spaces/guides/agent-memory-and-identity#access-to-your-computers): a+Agents follow [per-agent machine access](/spaces/guides/agent-memory-and-identity#access-to-your-machines): apersistent agent uses a Space on your spare Mac only after you allow it, and a-grant on the computer does not reach the Spaces it provides.+grant on the machine 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 computers+### Use all your machines [#use-all-your-computers]-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+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`cua auth login` and `cua host setup --share spaces`), then ask for `auto`:```bash test="cli-shape" id="cua-spaces-create-auto"@@ -427,33 +436,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 computer that can take the Space:- this one, or one of your computers (or one shared with you as an editor)+ **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)that provides Spaces. Modal takes it only when you[connected Modal](/cua-sdk/guides/your-cloud) and no- 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**+ 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**by the Spaces on it. Other programs keeping its CPUs busy never refuse- 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+ 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(`HostCapacity` in the SDK, exit code 8 in `cua`) that says what isreserved, not "not found". Delete a Space, ask for less (`--cpus`,- `--memory`), or add a computer.+ `--memory`), or add a machine.- `cua sb run` runs a command in a new Space `--count` times, each deletedafterwards. `cua sb runs` shows the runs and their jobs.-- A run on your computers keeps going when your laptop sleeps: one of your- computers that provides Spaces coordinates it, chosen through your+- A run on your machines keeps going when your laptop sleeps: one of your+ machines that provides Spaces coordinates it, chosen through youraccount, and another one takes over if it goes away.-- `cua spaces ls` and the app's sidebar show how loaded each computer is.- To stop new work going to a computer, turn **Provide Spaces** off on it+- `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 host config --provide-spaces off`); turn it on again to resume. Work- it had runs again on another computer.+ it had runs again on another machine.-#### Keep a Space on your computers+#### Keep a Space on your machines-A Space you want to outlive any one computer (an agent's long-running home, a-build machine) is created **durable**: when its computer goes away (powered-off, crashed, taken offline) it is created again on another of 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 machinesthat provides Spaces, with the same name.```bash test="cli-shape" id="cua-spaces-create-durable"@@ -466,45 +475,45 @@ cua spaces delete research --forceSDK, `durable: true` in the `create_space` MCP tool). Without `--name` itgets a generated one.- `cua spaces ls` (and `list_spaces`, with `durable` set to its name) shows- it like any Space, marked `(durable)`, under the computer it runs on now.+ it like any Space, marked `(durable)`, under the machine it runs on now.Use it by its name (`space="research"` in the SDK and MCP tools): the namefinds it wherever it is.- When it moves it starts fresh: the new copy is a new Space of the sameimage 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 computer would have it created again.+ one machine would have it created again.#### What is guaranteed-- **Each job has one result.** A job may run twice (a computer was cut off+- **Each job has one result.** A job may run twice (a machine was cut offand its job ran again elsewhere), but only one result is recorded andshown. Make jobs safe to repeat.-- **No job is lost** while one of your computers that can coordinate and one+- **No job is lost** while one of your machines that can coordinate and onethat can run it are up: a job either ends with its result or says why itcould not run.- **One coordinator at a time.** The relay hands out the coordinator'slease with a number that only grows and refuses writes under an old- number, so a computer that slept or lost its network cannot overwrite the+ number, so a machine that slept or lost its network cannot overwrite thecurrent one, whatever its clock says.-- **Only your computers.** Work goes only to computers you own or that were- shared with you as an editor, that have **Provide Spaces** on, and each- computer checks this itself. Every placement is recorded.+- **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.Execution is at least once; results are exactly once. How it works, and howit was checked (a model checker, simulation of the real code, and fault-injection on real computers), is in the+injection on real machines), 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 devices with-keys only your account's enrolled devices hold, and the relay stores and+environment, input, output and result are encrypted on your machines with+keys only your account's added machines hold, and the relay stores andforwards ciphertext. It reads only what it needs to keep one coordinator and-one result per job: job ids, the kind of each change, which computer an-attempt went to, and sizes. A device you revoke cannot read anything written+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 writtenafter it left. Details are in [What the relay can see](/spaces/guides/relay-security#runs-on-all-your-machines).-Computers added only by address (no relay) are pooled by the computer you run+Machines added only by address (no relay) are pooled by the machine you runfrom, and their runs pause while it sleeps.</Callout>@@ -512,7 +521,7 @@ from, and their runs pause while it sleeps.A spare Mac your laptop reaches by its [Tailscale](https://tailscale.com) (orLAN) address can host Spaces without the cua.ai relay: no sign-in on either-computer and no enrolled devices.+machine and no added machines.With `--tailnet`, your tailnet (Tailscale or Headscale) also identifies whocalls, so you and the teammates you `--allow` need no token: see@@ -546,7 +555,7 @@ The laptop keeps the token in its Spaces credential storecua spaces create macos:26 --on "spare mac mini" --count 2```-`on="host:<name>"` looks at your computers on the relay first, then at the hosts+`on="host:<name>"` looks at your machines on the relay first, then at the hostsyou added with `--host`, with the same matching rules. Each new Space runs on theMac with the same limits (four Spaces, two macOS VMs). It is not put on therelay: the Mac forwards a port on its own address to the Space's cua-spacesd, and@@ -558,7 +567,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 createsand deletes Spaces there and reaches the Mac's own shell and files, even with- **Share this desktop** off. Treat it like an SSH key and use it only over+ **Let other machines control this desktop** off. Treat it like an SSH key and use it only overTailscale or a LAN you trust. By default the Mac takes host calls, andconnections to the Spaces it forwards, only from loopback, Tailscale(`100.64.0.0/10`, `fd7a:115c:a1e0::/48`) and private LAN addresses@@ -573,11 +582,11 @@ restarts, the Mac opens the same port again.| Error | Meaning | Fix ||---|---|---|-| `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. |+| `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. |## If it doesn't work@@ -585,11 +594,11 @@ restarts, the Mac opens the same port again.|---|---|| "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 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. |+| 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. |## Next-- [Connect your agent](/spaces/guides/connect-your-agent): let an agent use the new computer.+- [Connect your agent](/spaces/guides/connect-your-agent): let an agent use the new machine.- [Create a Space](/spaces/guides/add-a-space): run a Space on it.-- [Plans and Teams](/spaces/guides/teams): share computers with your team.+- [Plans and Teams](/spaces/guides/teams): share machines with your team.diff --git a/docs/content/docs/spaces/guides/add-a-space.mdx b/docs/content/docs/spaces/guides/add-a-space.mdxindex 6730a4e960..071e9f534f 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 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.'+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.'---import { Callout } from 'fumadocs-ui/components/callout';import { Tab, Tabs } from 'fumadocs-ui/components/tabs';-A Space is one desktop on one of your computers. Ids are the sandbox refs+A Space is one desktop on one of your machines. 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 computer first, see [Add a computer](/spaces/guides/add-a-computer).+whole machine first, see [Add a machine](/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 computer by address+## Add an existing machine by address-Choose **Connect by address** in New Space, or register a computer from code.+Choose **Connect by address** in New Space, or register a machine 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 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+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(`alpine:3.20`, `node:20`): a static cua-spacesd is put into it and runsbeside 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 computer, 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 machine, 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 computers on the+Lists registered Spaces and, when you are signed in, your machines on therelay (`relay:<machine-id>`, no `add` needed). Register or forget one from ashell:@@ -241,7 +241,7 @@ cua spaces rm studioA [Tailscale](https://tailscale.com) address works here too (its IP orMagicDNS name as the host:port): `cua spaces add` reaches it like any otheraddress and the Space registers as `direct:<addr>`. That only attaches one-already-running Space. To host Spaces for `on="host:<name>"`, set the computer up+already-running Space. To host Spaces for `on="host:<name>"`, set the machine upwith [`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 bydiff --git a/docs/content/docs/spaces/guides/agent-memory-and-identity.mdx b/docs/content/docs/spaces/guides/agent-memory-and-identity.mdxindex ae2d8c7e83..5239614fd0 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 computers 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 machines 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 computers.+across its Space being deleted and created again, and across machines.```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 computer-access grants and in the audit log. Named agents-are kept by the Cua daemon of the computer you add them on.+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.## 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 computer or an added address | Only the agent pauses. | Only the agent resumes. |+| Your own machine 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 computers you allowed this agent to use. |+| `computer_list`, `computer_list_tools`, `computer_call` | Your machines 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 computers+## Access to your machines-`cua host setup` makes a computer a Space for your whole account. A named agent+`cua host setup` makes a machine a Space for your whole account. A named agentreaches it only if you allow that agent by name. Allowing asks for Touch ID oryour 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 computer (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 machine (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.mdxindex 73f945b1b0..f3dff72fff 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 slotis skipped.-- If the daemon was asleep (your computer was off), a missed schedule fires+- If the daemon was asleep (your machine was off), a missed schedule firesonce 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.mdxindex a6abd88064..7fa8c6b09e 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 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.'+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.'---Cua Spaces gives you a one-line prompt for each job you want an agent to do:-join a Space, add a computer, connect a cloud, set up S3 storage for Cua Volume.+join a Space, add a machine, 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 foreveryone, and it never says anything about your Spaces.@@ -16,25 +16,25 @@ In a Space, choose **Add an agent**, then copy the line. It looks likeonce, for one Space, and expires in an hour by default. Using it needs your Cuasign-in, so a leaked line alone gets nobody anywhere.-The agent runs `cua join <code>` on your computer, picks a name and an icon, and+The agent runs `cua join <code>` on your machine, picks a name and an icon, andjoins the thread as its own member with its owner shown next to it. It takestasks from the thread and answers there. For later sessions it can add Cua's toolsto 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 computer. It does not get the+Space only, kept in your keychain and bound to this machine. It does not get thedesktop, other Spaces, Volume or Keyvault. Remove it from the Space, or remove the-computer from your account, and its key stops at once.+machine from your account, and its key stops at once.-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.+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.## The other promptsThe pages for agents, which each agent reads from its prompt, are alsouseful to read yourself:-- [Add a computer](/agents/add-a-computer)+- [Add a machine](/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)diff --git a/docs/content/docs/spaces/guides/agents-in-a-space.mdx b/docs/content/docs/spaces/guides/agents-in-a-space.mdxindex 409bec3008..4f01ff0446 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 cheimport { Tabs, Tab } from 'fumadocs-ui/components/tabs';-An agent in a Space works on a computer of its own instead of on This Mac. You+An agent in a Space works on a machine of its own instead of on This Mac. Youadd it once, give it work, and come back later to read what it did. The Spaceis the boundary: the agent approves its own tool calls inside it, and nothing-it does reaches your computer unless you allow it.+it does reaches your machine unless you allow it.There are three ways to run one:@@ -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 computer whose+Named agents are kept by the Cua daemon on This Mac (or on the machine whosedaemon you use), and their Space can be any Space you can reach: a local one,-one on a [computer you added](/spaces/guides/add-a-computer), or one in your own+one on a [machine you added](/spaces/guides/add-a-computer), or one in your owncloud.## 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 thebox, 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 computer, so it is still there after+Which agent is kept for each Space on your machine, so it is still there aftera 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 theruns in it, including one-off tasks.-## From another device or person+## From another machine or person-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+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[team](/spaces/guides/teams), you read and post in the thread of each Space it-provides from your own device, 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+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 daemonthrough the relay, signed in as you: what you post shows your name, and theowner's roles and each agent's rights decide what you can do. Shared with youto 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 computer is online. If it runs an+thread. The thread can be reached while that machine is online. If it runs anolder 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 harnessreads, written 0600 inside the run and redacted from its log; see[Agent keys](/spaces/guides/connect-your-agent#agent-keys). Credential files on-your computer are never copied into a Space. The one exception is Claude Code's+your machine are never copied into a Space. The one exception is Claude Code'sown sign-in, which you choose to import: Cua reads it once you agree and givesClaude 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.mdxindex 787a24ecff..f401938f41 100644--- a/docs/content/docs/spaces/guides/bring-your-own-compute.mdx+++ b/docs/content/docs/spaces/guides/bring-your-own-compute.mdx@@ -1,11 +1,11 @@---title: Bring your own compute-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.'+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.'---import { Callout } from 'fumadocs-ui/components/callout';-Cua Spaces runs on hardware you bring. You don't rent a computer from Cua. You+Cua Spaces runs on hardware you bring. You don't rent a machine from Cua. Youadd one you already have, and your agents and your other machines use it fromthere. This page shows four ways to do that. Pick the one that matches what youhave.@@ -17,18 +17,18 @@ have.| A Linux machine, 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 computer shows up in **Machines** in the-app and in `cua spaces ls`. Nothing connects inward to it: the computer calls+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 callsout 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 computer.+The quickest start. Your Mac becomes your first machine.1. Install Cua Spaces and sign in. [Install](/spaces/guides/install) has thesteps, and the [quickstart](/spaces/quickstart) walks through the first run.-2. Open **This computer**, choose how to use it, and press **Set up for- access**. Your other devices can now reach this Mac.+2. Open **This machine**, choose how to use it, and press **Set up for+ access**. Your other machines can now reach this Mac.Prefer a terminal? Run:@@ -43,7 +43,7 @@ System Settings, Privacy & Security, and turn both on.## A Mac miniA Mac mini in a closet is a good place to run Spaces for your laptop and your-agents. Set it up as a spare computer: it runs Spaces for you, and its own+agents. Set it up as a spare machine: it runs Spaces for you, and its owndesktop 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 witha code instead. The first command installs. The second prints a web address and-a short code. Open the address on any other device and enter the code.+a short code. Open the address on any other machine and enter the code.```bash skip="no-runner"curl -fsSL https://cua.ai/install.sh | sh -s -- -y --select spaces,host --no-onboarding@@ -80,7 +80,7 @@ cua spaces create macos:26 --on "mac mini" --count 2Spaces on a Mac need an Apple silicon Mac. One Mac runs at most two macOSSpaces at once, because that is Apple's license limit. [Add a-computer](/spaces/guides/add-a-computer#use-a-spare-mac-to-host-spaces) has the+machine](/spaces/guides/add-a-computer#use-a-spare-mac-to-host-spaces) has therest: limits, Tailscale without the relay and fixes for common errors.## A Linux box or VPS@@ -90,7 +90,7 @@ provider. You can do it over ssh, with no screen.Before you start, make sure the machine can run Linux Spaces. They run incontainers, so **install Docker first**. Spaces on a Linux box are Linux-Spaces. A Mac or Windows Space needs a Mac or a Windows computer.+Spaces. A Mac or Windows Space needs a Mac or a Windows machine.1. Connect to the machine with ssh.2. Install Cua Spaces without questions:@@ -127,7 +127,7 @@ 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 computer](/spaces/guides/add-a-computer#add-a-computer-from-the-app).+[Add a machine](/spaces/guides/add-a-computer#add-a-machine-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 andshows **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 computer from Cua doesn't delete anything on it.+console. Removing a machine from Cua doesn't delete anything on it.-## After you add a computer+## After you add a machine- **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 computer 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 computer doesn't show up, run `cua host status` on it. It names the+If a machine doesn't show up, run `cua host status` on it. It names theproblem. [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.mdxindex 14e512c448..f952d0d83b 100644--- a/docs/content/docs/spaces/guides/connect-a-cloud.mdx+++ b/docs/content/docs/spaces/guides/connect-a-cloud.mdx@@ -1,10 +1,10 @@---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 devices, 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 machines, set a budget and a largest machine, and verify it.---Link your AWS, Google Cloud or Azure account once, with no stored key, and-Spaces can run there from every device and agent on your Cua account. This page is written for+Spaces can run there from every machine and agent on your Cua account. This page is written forthe coding agent that does it for you. The Cua Spaces app gives you a promptlike this one to paste into your agent:@@ -171,9 +171,9 @@ is.## Hetzner and ModalHetzner and Modal have no OIDC, so they use an API token. Cua seals the-token to the person's devices: the device you run on encrypts it with the-account's pool key, and only devices of the person's Cua account can open-it. Cua's servers keep only the ciphertext. Any of the person's devices then+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 thenopens it in memory when it calls the cloud. No tool returns it, not to youand not to any other agent.@@ -215,45 +215,45 @@ sealed.cua cloud status hetzner```-The line under Hetzner names the devices that can open the token ("can open+The line under Hetzner names the machines that can open the token ("can openit: ..."). At least one of them must be online for Cua to make machinesthere while the person is away.-### On the person's other devices+### On the person's other machines-They do not paste the token again. On another device of the same Cua+They do not paste the token again. On another machine of the same Cuaaccount, 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 device+### Sealed or kept on this machine-Without `--sealed` or `--no-sealed`, the token is sealed when this device has+Without `--sealed` or `--no-sealed`, the token is sealed when this machine hasthe account's pool keys (the `cua` of the Cua Spaces app, signed in) and abudget is given, or when the link is sealed already. Otherwise the Hetzner-token is kept in this device's Cua credential store, as in earlier+token is kept in this machine's Cua credential store, as in earlierversions.- `--sealed` insists on sealing. Without a token on standard input, it seals- the token this device already has (the saved one, `HCLOUD_TOKEN`, the+ the token this machine already has (the saved one, `HCLOUD_TOKEN`, thehcloud 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 movesto a sealed token.-- `--no-sealed` keeps the Hetzner token on this device only.+- `--no-sealed` keeps the Hetzner token on this machine 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 device.+ input. It is sealed and swapped in for every machine.- Revoke it: delete the token in the Hetzner Cloud console (or with`modal token`), or run `cua cloud disconnect hetzner`, which deletes thesealed token on Cua's servers.-When the person removes a device from their Cua account, the account's pool-key moves to a new generation. The next device that uses the token seals it-again under the new key, so the removed device cannot open it any more. To be+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 besure, replace the token as well.## Google Cloud@@ -365,9 +365,9 @@ cua cloud status azure## Other clouds-Hetzner and Modal link with a token sealed to the person's devices (see+Hetzner and Modal link with a token sealed to the person's machines (see[Hetzner and Modal](#hetzner-and-modal)), or with their own sign-in on this-device, and Google Cloud too if the person prefers `gcloud` on this device to+machine, and Google Cloud too if the person prefers `gcloud` on this machine toa link without a key. The budget and largest machine work the same way:```bash test="cli-shape" id="agents-connect-other"@@ -375,7 +375,7 @@ cua cloud connect gcp --project my-project --region us-central1 --budget 100 --mcua cloud connect modal --environment spaces --budget 50```-The second command links Modal with the Modal CLI's sign-in on this device+The second command links Modal with the Modal CLI's sign-in on this machine(`~/.modal.toml`) instead of a sealed token.## What to ask the person, and what not todiff --git a/docs/content/docs/spaces/guides/connect-your-agent.mdx b/docs/content/docs/spaces/guides/connect-your-agent.mdxindex e1ea0900c1..e2d9e7fb71 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 computer,+On first run, **Pick your agent** lists the agents found on this machine,most used first: Hermes, Claude Code, Codex, Cursor, then the rest. Each rownames 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 openit again. Connecting none is fine: connect agents later in **Settings,Connections**.-### Per computer+### Per machine-Everything on this screen belongs to this computer only:+Everything on this screen belongs to this machine only:- The Cua skills and MCP server go into each agent's settings on this- 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+ machine. On another machine, install Cua Spaces there and pick its agents.+- **Sign-ins and keys** stay on this machine too. Another machine keeps itsown.### Codex and ChatGPTCodex signs in with your ChatGPT account on its own, with `codex login`. WhenCodex 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 computer,-and Cua never reads or copies it. On another computer, sign in to Codex there+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(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 computer+An agent that Cua runs in a Space uses the provider keys saved on the machinethat hosts the Space: the **OpenAI key** for Codex and the **Anthropic key** forClaude Code. Add them on **Pick your agent** or in **Settings, Connections**. They stay-in this computer's Keychain (Credential Manager on Windows).+in this machine's Keychain (Credential Manager on Windows).### Claude Code and your Claude plan-If you already use Claude Code on this computer, Cua can run it in your Spaces+If you already use Claude Code on this machine, Cua can run it in your Spaceswith 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 foryou to press **Use my sign-in**:-1. Cua reads the sign-in Claude Code already keeps on this computer. On a Mac+1. Cua reads the sign-in Claude Code already keeps on this machine. On a Macthat is the Keychain item "Claude Code-credentials", and macOS asks you toallow it. On Linux and Windows, and when Claude Code keeps it in a file, itis `.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 **Needsreconnect**, with **Reconnect**: open Claude Code once, or run `claude authlogin`, then press Reconnect.-If Claude Code isn't signed in on this computer, Cua offers the ways on in this+If Claude Code isn't signed in on this machine, Cua offers the ways on in thisorder: sign in with Claude Code (`claude auth login` in Terminal, then tryagain), paste a token made with `claude setup-token` (a long-lived token forpeople 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 computer shares the same Spaces, sandboxes and streams.+this machine shares the same Spaces, sandboxes and streams.## Check that it works@@ -129,11 +129,11 @@ this computer 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 computer:+a Space on this machine:> 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 computer". When+On Windows the request says "this PC", and on Linux "this machine". Whenthat works, try a bigger task:| Ask your agent | What it does |@@ -148,7 +148,7 @@ lists the tools it gets.## What your agent can doThe cua MCP server gives an agent 33 Spaces tools plus sandbox and computer-tools. For the computer the agent runs on, use [Cua Driver](/cua-driver/quickstart)+tools. For the machine 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 computer | Sign in on this computer, and make sure the device is enrolled. See [Add a computer](/spaces/guides/add-a-computer#reach-it-from-your-other-machines). |+| 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). |## Next- [Create a Space](/spaces/guides/add-a-space): run an agent's work in a new desktop.-- [Add a computer](/spaces/guides/add-a-computer): give your agent another computer.+- [Add a machine](/spaces/guides/add-a-computer): give your agent another machine.- [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/create-a-space-with-the-sdk.mdx b/docs/content/docs/spaces/guides/create-a-space-with-the-sdk.mdxindex 6f7b604795..c18c20fbbc 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 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.+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.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 computer from code, run a command in it,+you can watch. You create one on your own machine 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 computer.+and delete the Space. Nothing leaves your machine.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 computer: the+The program passes no location, so the Space runs on this machine: thecanonical 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 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+- [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 orTailscale.- [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.mdxindex c73f247b76..ac9a102716 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 computer) | rw | rw | rw | rw | rw |+| You (app, CLI, agents on your machine) | 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 andwrites it like any folder. The guest sees only that Space's view (theSpace's row in the table above, or its agent's), and it never holds keys:-your computer serves the view over the Space's own connection and applies the+your machine serves the view over the Space's own connection and applies theaccess 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 themount path (a crash, a force-quit) before it does anything else.-- Your computer notices the connection closed, or that the new daemon reports+- Your machine notices the connection closed, or that the new daemon reportsthe volume detached, and mounts the volume again, then restarts the hotspotif one was on. It retries with a growing wait (2 s, then 4 s, up to aminute) 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 devices+## Sync across machines-Two computers using the same bucket see each other's changes within+Two machines using the same bucket see each other's changes withinseconds. Each change is also written to a small change log in the bucket-itself (`.cua-feed/`), and every computer checks it with a single listing+itself (`.cua-feed/`), and every machine checks it with a single listingrequest, twice a second while things change, backing off to every 5 secondswhen idle. No Cua service is involved; it works with your own S3, R2 orMinIO bucket.@@ -317,7 +317,7 @@ at p95 for a 1 KiB file, and shows in the other's mounted volume 2 ms to0.34 s). While nothing changes, the check backs off, so the first changeafter a quiet period can take up to 5 seconds.-When two computers change the same file, the write that reaches the bucket+When two machines change the same file, the write that reaches the bucketlast 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'shistory. 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 computer already+noncurrent versions under `.cua-feed/` after a day. Each machine alreadydeletes 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 ofSpaces (Synced, Syncing, Offline) and any conflicts, which open the Volume-page. Nothing shows while the files stay on this Mac with no other device.+page. Nothing shows while the files stay on this Mac with no other machine.**Volume page.** Status, not a file browser: Finder is. Open in Finder-shows the volume, mounting it first when it is not mounted. Devices 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+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 othercopy in Finder, Resolve clears the entry and keeps both files.-+## Storage| Backend | Where | Set up ||---------|-------|--------|-| `fs` (default) | `~/.cua/volume/data` on this computer | Nothing |+| `fs` (default) | `~/.cua/volume/data` on this machine | 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.mdxindex a20d5d4a14..a91a3607fd 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 device. Signing in-adds this computer to your account, so it shows up in Cua Spaces on your other-devices. It provides Spaces and keeps its screen private; a computer set up+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 upbefore keeps its settings. Add `--no-host` (`-NoHost`) to sign in withoutadding 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 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. |+| 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. |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 computer provides+Cua Spaces launches at login by default, so the Spaces this machine providesand your persistent agents come back after a restart. Turn it off in **Settings,General**.@@ -94,10 +94,10 @@ browser sandbox (it starts with `--no-sandbox`), and without the system'sconfirmation 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 computer, the `cua` CLI uses Docker (gVisor+For Linux Spaces created on this machine, the `cua` CLI uses Docker (gVisor`runsc`, when installed, adds isolation) or QEMU. QEMU needs read and writeaccess to `/dev/kvm` to run same-architecture guests quickly. Run-`cua runtime doctor` to see what this computer has.+`cua runtime doctor` to see what this machine has.## Updatesdiff --git a/docs/content/docs/spaces/guides/keyvault.mdx b/docs/content/docs/spaces/guides/keyvault.mdxindex 66611442e2..d7466f651c 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 computer without the app open:+Requests also show up in the CLI, for a machine without the app open:```bash test="cli-shape" id="approve-login"cua keyvault requestsdiff --git a/docs/content/docs/spaces/guides/relay-security.mdx b/docs/content/docs/spaces/guides/relay-security.mdxindex 26b82bb4a0..3fee722588 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 devices and computers, it coordinates a WireGuard®-based mesh.**+- **For Cua machines, it coordinates a WireGuard®-based mesh.**It introduces the two ends. When they can't reach each other directly, itforwards their traffic as ciphertext it can't read. This is the defaultfor 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 computers |+| Your Cua version | Connections to your machines ||---|---|| `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 device 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:+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:the Cua Spaces app first, then the `cua` CLI and SDK, then each hosted-computer (`cua host setup` again, or let the app update it).+machine (`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 device and the machine is encrypted end to end with+ traffic between your machine is encrypted end to end withWireGuard between keys that never leave the two ends. Most connections godirectly between the two networks; when they cannot, the relay forwardsthe encrypted packets. **The relay cannot read or change shell output,@@ -51,9 +51,9 @@ computer (`cua host setup` again, or let the app update it).clipboard data sent as input, and, unless sealed (below), Keyvaultpasswords 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 devices,- but everything a job is and produces is **sealed on your devices** with- keys only your enrolled devices hold. The relay sees job ids, the kind of+ 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 ofeach change, which machine 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).@@ -62,31 +62,31 @@ computer (`cua host setup` again, or let the app update it).short-lived signed assertion instead (account mode), or forwards aself-hosted relay's env token unmodified without persisting it (staticmode). 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 device+ machine, and a static relay never sees the env token at all (a machineproves it holds the token to the machine itself). See the relay README(`libs/cua-spacesd/crates/cua-relay/README.md` in the cua repository) forthe exact claims and how they are enforced in code.- **The relay is still a trusted coordinator.** In account mode, the relay- tells each device and computer which peers are yours (your devices, and- the accounts a computer is shared with) and what each peer's mesh public+ tells each machine which peers are yours (your machines, and+ the accounts a machine is shared with) and what each peer's mesh publickey 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 device of- its own as a peer, or hand your device a key of its own in place of a- computer'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 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.It can't decrypt traffic sent under keys it doesn't hold. A- static-token relay can do less: each computer accepts only the devices that+ static-token relay can do less: each machine accepts only the machines thatproved they hold its env token, and ignores any other peer the relay names.- We are working on device-signed keys, so that only your enrolled devices can+ We are working on machine-signed keys, so that only your added machines canvouch for a peer's key. Until then, if you need a coordinator you don'thave to trust, run your own relay or [use your owntailnet](/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 devices and computers,+ a log line says so. Set `CUA_MESH=require` on your machines,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 computer currently routed- through it on the **HTTPS path**: it can mint assertions the computers still+ equivalent to a compromised session for every machine currently routed+ through it on the **HTTPS path**: it can mint assertions the machines stilltrust, and read whatever crosses it meanwhile.## The mesh (on by default)@@ -95,7 +95,7 @@ computer (`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 throughthe 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, computers and devices+everything else: the browser viewer, web-hosted agents, machineswithout 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 setThese always use the relay's HTTPS path, so the relay can read them intransit, whichever Cua version you run:-- **The browser viewer**, and anything else that opens a computer through+- **The browser viewer**, and anything else that opens a machine through`https://<relay>/m/<computer>/…`: web or Cloudflare-hosted agents, and MCP- clients that connect to a computer through a relay URL.+ clients that connect to a machine through a relay URL.- **Share links** (`cua share`): a private, team or public link is servedthrough 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:-- devices and computers on [older versions](#which-path-you-are-on);+- machines 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`.@@ -132,49 +132,49 @@ And for Cua's own apps, CLI and SDK, these use the HTTPS path:| 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 device) |+| 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 device (`relay+Which path a connection took shows in the logs of the machine (`relaySpace over the mesh`, or `using the relay's HTTPS path` with the reason).-With `CUA_MESH=require`, a device never falls back to the HTTPS path.+With `CUA_MESH=require`, a machine never falls back to the HTTPS path.## Runs on all your machinesA batch run on your machines (`cua sb run --on auto`, `on="auto"` in the SDKand 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 devices+That log, its snapshots, and the requests and answers between your machinesare encrypted end to end:-- **Your devices hold the keys.** Each signed-in device has a pool key- (X25519, in the same store as its device key: the OS keychain for- Cua-signed builds). It signs the pool key with its enrolled device key and+- **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 andregisters it with the relay. The account's data key is wrapped to each- device's pool key with HPKE (RFC 9180) in authenticated mode, so a device- only accepts keys another of your devices wrapped. The relay stores the+ 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 thewraps and cannot open them.-- **Everything about a job is sealed** before it leaves the device, with+- **Everything about a job is sealed** before it leaves the machine, withXChaCha20-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 devices. Each sealed+ details, and every request and answer between your machines. Each sealedentry is bound to its position and readable fields, so the relay cannotmove it, swap it or change it unnoticed.-- **New and revoked devices.** A device you add is given the keys by any of- your devices that has them, within seconds, and can then take over runs.- At least one of those devices must be online for that: until then, a run- on your machines from the new device fails within seconds and names the- devices 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 device never makes new keys on its own while a- device that holds them is still enrolled, however long ago it was seen:+- **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:only you can tell an asleep laptop from a lost one, and the relay can't- make your devices drop the keys by hiding the others. Runs on the device+ make your machines drop the keys by hiding the others. Runs on the machineitself (`--on local`, the default for `cua run`) never need the keys.- When you revoke a device, the relay refuses anything sealed under the- keys it had until one of your devices makes new ones without it, which+ 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, whichhappens on the next write: nothing written after it left is readable byit, even with the relay's help. What it could read before stays readable to- it. If every device that held the keys is revoked, the next device starts+ it. If every machine that held the keys is revoked, the next machine startsnew keys and the log nobody can read is dropped (its runs are lost).| The relay can see | The relay cannot see |@@ -182,32 +182,32 @@ are encrypted end to end:| 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 device coordinates, its epoch, and when | Durable Spaces' names, addresses and tokens |+| 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 devices hold the keys, and the key generation | The keys |+| Which machines 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 enrolled devices, and the fencing that+wrapped by and to your account's added machines, and the fencing thatkeeps one coordinator and one result per job. How this was checked (a modelchecker, a simulation of the real code, and fault injection on realmachines) 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 devices are your account's. A relay that is- actively malicious could enroll a device of its own (as it could add a+ 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 apeer to the mesh, above) and be given the keys for what is written after- that; it could not read anything sealed before, and the device shows in- `cua devices ls`, in the app, and in `cua computers` as one the keys are+ that; it could not read anything sealed before, and the machine shows in+ `cua devices ls` and in the app as one the keys areshared with. Run your own relay if that is not acceptable. Jobs reach your- computers over the mesh (ciphertext); with the mesh off they use the HTTPS+ machines over the mesh (ciphertext); with the mesh off they use the HTTPSpath, 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 computer's own key, so+We seal teleport secrets end to end to the destination machine's own key, sothe relay forwards only ciphertext for a sealed delivery. The construction:an ephemeral X25519 key per delivery, HKDF-SHA256, XChaCha20Poly1305, boundto the Space id, a purpose string and a timestamp, with replay rejection@@ -241,34 +241,34 @@ against. The gate and sealing apply to the HTTPS path only.## Other hardening already shipped-- **Device enrollment with MFA for new devices.** Re-signing in enrolls only- your own computer (a re-key, or your account's first device). A brand-new- device on an account that already has an enrolled device needs an approval- from an enrolled device, or a sign-in whose token itself proves a second+- **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 secondfactor. A verified email alone is not enough.-- **New computers are flagged.** A computer registered without an enrolled- device's signature or MFA is marked unconfirmed until an enrolled device+- **New machines are flagged.** A machine registered without an added+ machine's signature or MFA is marked unconfirmed until an added machinevouches for it.-- **A separate origin for computer content.** Computers no longer render as+- **A separate origin for machine content.** Machines no longer render asHTML, register a Service Worker, or set cookies on the relay's ownorigin outside the one known viewer path; a fully separate registrable- domain for computer content is designed and partly implemented in code,+ domain for machine 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 computer (or one+ plus a relay-wide budget with backpressure, so one machine (or oneaccount's worth of them) with slow-reading clients cannot take down every- other computer's connection.+ other machine's connection.- **A tamper-evident, exportable audit log**, hash-chained like theKeyvault's own, with `GET /v1/audit?format=jsonl` for export to your ownSIEM or backup.- **The migration grace period (a stolen session alone reaching every- computer) is off by default**, and time-boxed to an announced rollout+ machine) is off by default**, and time-boxed to an announced rolloutwindow when it does run.- **State writes that fail loudly.** The relay appends audit events andsessions to their own logs instead of rewriting its state per event, cleans- up after an interrupted write at startup, refuses a device or machine+ up after an interrupted write at startup, refuses a machinechange it could not store (rather than acknowledging it), and keeps a- reserve of free space that pool data cannot use, so sign-ins and device+ reserve of free space that pool data cannot use, so sign-ins and machinechanges keep working when pools fill the volume. A self-hosted relayreports this on `GET /readyz` (a real write probe, free space, eachstore's last write) and `GET /metrics`; alert when `/readyz` fails, free@@ -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 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+ 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, anetwork that blocks it) Cua uses the relay's HTTPS path, as before. To turnit off, set `CUA_MESH=off` (below).</Callout>-With the mesh on, a device that opens a Space on one of your computers+With the mesh on, a machine that opens a Space on one of your machines(`relay:<machine>`) connects to it over a WireGuard®-based mesh that runsinside Cua itself, instead of through the relay's HTTPS path. The relaycoordinates the mesh but never holds a session key: shell, files, input,screen and Keyvault deliveries cross it only as ciphertext.-- **End to end.** Each device and computer makes its own key pair on first+- **End to end.** Each machine makes its own key pair on firstuse; the private half never leaves it. Traffic between two of them isencrypted 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 device you connect from and-the computer you host. Each end decides for itself with `CUA_MESH`.+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`.| `CUA_MESH` | Behavior ||---|---|@@ -318,27 +318,27 @@ the computer 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 device:** set `CUA_MESH` where `cua` runs (your shell, or the+- **On the machine:** set `CUA_MESH` where `cua` runs (your shell, or theenvironment of the cua daemon; restart the daemon with `cua daemon stop`after changing it).-- **On a hosted computer:** to turn it off there, run `cua host setup` with+- **On a hosted machine:** 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 runsetup again without it.-`cua spaces ls` lists the same computers either way. With `prefer`, a computer+`cua spaces ls` lists the same machines either way. With `prefer`, a machineor relay that does not speak the mesh is used over HTTPS, so mixing-updated and older computers works.+updated and older machines works.### Who can connectThe relay applies the rules you already manage:-- A device enrolled for your account reaches the computers your account owns+- A machine added to your account reaches the machines your account ownsand those shared with it, while their sharing is on.-- The computer sees each device with the same identity as before (account,+- The machine sees each machine with the same identity as before (account,verified email, owner, editor or viewer), and its own host policy stilldecides what that caller may do.-- Stopping sharing, removing someone from a share list, or revoking a device+- Stopping sharing, removing someone from a share list, or revoking a machinetakes it off the mesh within seconds and cuts its open connections. Thenext 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 yourplan's live sessions, the same as one over the relay's HTTPS path, and one-computer reached both ways at once counts once. Remote hours count only the+machine reached both ways at once counts once. Remote hours count only thetime a session's traffic goes through the relay: a direct connection usesnone. `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 relaysA self-hosted `cua-relay` coordinates a mesh when you turn it on with-`--mesh on` (or `CUA_RELAY_MESH=on`); without it, devices use the HTTPS-path. Give it a UDP port for STUN so devices learn their public addresses:+`--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:```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 (devices then use the HTTPS path); `--mesh-relay off` keeps the-coordinator but stops relaying packets (devices that cannot reach each other+mesh off (machines then use the HTTPS path); `--mesh-relay off` keeps the+coordinator but stops relaying packets (machines that cannot reach each otherdirectly then cannot connect over the mesh). The mesh registry persists next-to the state file (`<state>.mesh.json`), so a restart keeps every device's+to the state file (`<state>.mesh.json`), so a restart keeps every machine'skeys.-On a self-hosted relay with static tokens, a device reaches a computer only-after proving it holds that computer's env token. The computer checks the-proof itself and remembers the devices it accepted; the relay only passes the+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 theproof 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 computers' names, owners and share lists | Routing, and checking who may connect | Until you remove the computer or delete your account |-| Your enrolled devices: their public keys and sessions | Device enrollment | An enrollment ends 30 days after it was last used; removed when you revoke the device |-| Mesh registry: each device'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 device or 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 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'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 devices) 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 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 || 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): themesh in full, and [Use your tailnet](/spaces/guides/your-tailnet) to run onyour own Tailscale or Headscale network instead.-- [Add a computer](/spaces/guides/add-a-computer#reach-it-from-your-other-machines):- device enrollment in full.+- [Add a machine](/spaces/guides/add-a-computer#reach-it-from-your-other-machines):+ adding a machine to your account, in full.- [Share a Space](/spaces/guides/share-a-space): the allowlist and audit trailfor sharing.- [Keyvault](/spaces/guides/keyvault) anddiff --git a/docs/content/docs/spaces/guides/share-a-space.mdx b/docs/content/docs/spaces/guides/share-a-space.mdxindex bbb76c968e..550b502390 100644--- a/docs/content/docs/spaces/guides/share-a-space.mdx+++ b/docs/content/docs/spaces/guides/share-a-space.mdx@@ -83,14 +83,14 @@ change it, share with the team again with the other role.## How it worksSharing uses the same relay and allowlist as an-[added computer](/spaces/guides/add-a-computer#add-a-computer-from-a-terminal):+[added machine](/spaces/guides/add-a-computer#add-a-machine-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 computer for it, and the Space's own driver dials out+ account registers a machine for it, and the Space's own driver dials outover WSS, so no inbound port opens.-- The relay keeps two lists per computer: `allow` (editors) and `viewers`.-- Invitees need a verified email or account ID and an [enrolled device](/spaces/guides/add-a-computer#reach-it-from-your-other-machines).+- 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).- Removing someone, or changing their role, cuts their open streams at once.- Team membership comes from your team in your Cua account, not from therelay. 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 anleaves your team, they lose access to what you shared with them. If a teamis deleted, its shares stop.- A team share works differently. The Space goes on the team's list of- 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 device is+ 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 isapproved.```rust test="excerpt" id="rs-share-space" source="libs/cua/crates/cua-spaces/tests/share_space_e2e.rs#rs-share-space"@@ -126,7 +126,7 @@ Removing someone needs no confirmation.## Reach a Space from your other machines-To reach a Space from your phone or another computer without sharing it with+To reach a Space from your phone or another machine without sharing it withanyone, publish it on the relay:```bash test="cli-shape" id="cua-spaces-relay-register"@@ -138,7 +138,7 @@ cua spaces relay-unregister local:studiolet reg = ada.relay_register(&info.id).await.unwrap();```-Only your account's enrolled devices reach it until you share it. The MCP+Only your account's added machines reach it until you share it. The MCPtools 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 computer runs it | Its driver dials the relay. Suspending it disconnects everyone. |+| Local container or VM | yes, while this machine 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.mdxindex 55d78ad0dc..b0f1e8f3b4 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 computers, approve devices 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 machines, approve machines and manage seats.'---import { Callout } from 'fumadocs-ui/components/callout';-Cua Spaces is bring-your-own compute: you connect your own computers, and Cua+Cua Spaces is bring-your-own compute: you connect your own machines, and Cuadoes not rent them out. The plans cover the app, sharing and the hosted relay-that lets your devices reach your computers. Current prices are on+that lets your machines reach your machines. 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 devices reach your computers. 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 computer you connect and Teleport. Pro adds+Every plan includes Spaces on every machine you connect and Teleport. Pro addsmore live sessions and remote hours. Teams adds sharing a Space with your team,-team-owned computers, roles and device approval. Sharing is for teams: Free and+team-owned machines, roles and machine approval. Sharing is for teams: Free andPro accounts without a team cannot share a Space. SSO and audit export are notincluded yet.## What counts toward the limits-**Remote hours** are the time you spend using your computers from somewhere-else. Using a computer from itself is free.+**Remote hours** are the time you spend using your machines from somewhere+else. Using a machine from itself is free.-A **live session** is one person or agent holding a stream open to a computer+A **live session** is one person or agent holding a stream open to a machinethrough the relay, such as a desktop view, a terminal or an agent's processstream. Each hour with at least one live session counts as one remote hour, percalendar month (UTC).@@ -60,17 +60,17 @@ refunds.## Buy Teams-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 device must be approved-before it can reach a team computer.+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.<VideoDemosrc="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 computer for the team (29 seconds, no sound).+ Create a team, invite a teammate and add a machine 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,43 +115,43 @@ A team has one owner, and any number of admins and members.| | Owner | Admin | Member ||---|---|---|---|-| Open team computers (from an approved device) | yes | yes | yes |-| Request approval for a new device | not needed | yes | yes |+| Open team machines (from an approved machine) | yes | yes | yes |+| Request approval for a new machine | 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 computers | yes | yes | no |-| Approve or deny devices | yes | yes | no |+| Add and remove team machines | yes | yes | no |+| Approve or deny machines | 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 devices need+cancel the subscription first, then delete the team. The owner's own machines needno 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 device approvals for the team are deleted.+takes effect at once, and the person's machine approvals for the team are deleted.A member leaves with **Leave team** on the same page.-## Team computers+## Team machines-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 device 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+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 accountsyou [share it with](/spaces/guides/share-a-space) can reach it.-| | Personal computer | Team computer |+| | Personal machine | Team machine ||---|---|---|| 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 device |+| Who can open it | You, and people you share it with | Every member, as an editor, from an approved machine || Who adds or removes it | You | Owners and admins |-Team members have full use of a team computer: there are no view-only team+Team members have full use of a team machine: there are no view-only teammembers. To let someone only watch, share a Space with them as a viewer instead.-### Pair a computer to the team+### Pair a machine to the teamPairing needs Cua Spaces 0.8.0 or later. An owner or admin does this.@@ -159,61 +159,61 @@ Pairing needs Cua Spaces 0.8.0 or later. An owner or admin does this.your team next to **For** at the bottom of the sheet. Then pick **Open alink**, **Scan a QR code**, **Run a command** or **Enter a code**. Each onecarries a one-time pairing code that looks like `K7QM-4XPB-2RHD`. For 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+ 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 theapp 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 computer already has the Cua Spaces app, you don't need the command:+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**, andpaste the code or the link. The app asks before it joins.-The computer joins the team that made the code, with no sign-in on that computer.+The machine joins the team that made the code, with no sign-in on that machine.A code works once and expires after 30 minutes; while the sheet is open, itrenews by itself. Revoke an unused one from the sheet's **⋯** menu.-The computer then appears under **Machines** at+The machine then appears under **Machines** at[app.cua.ai/machines](https://app.cua.ai/machines), where an owner or admin can-remove it from the team. Removing a computer does not delete anything on it.+remove it from the team. Removing a machine does not delete anything on it.-Mac, Windows and Linux computers can all be team computers, and all join with+Mac, Windows and Linux machines can all be team machines, and all join with`cua host setup`. See [Install](/spaces/guides/install) to get the `cua` CLI.-Members open team computers from the Cua Spaces app (macOS 26 or later) or the+Members open team machines from the Cua Spaces app (macOS 26 or later) or theWindows and Linux apps on the [download page](https://cua.ai/download).-### Approve a device+### Approve a machine-A member's device can open team computers only once an owner or admin approves+A member's machine can open team machines only once an owner or admin approvesit.-1. The member opens a team computer from a new device. That asks for approval+1. The member opens a team machine from a new machine. That asks for approvalon its own (or run `cua team request <team>` to ask first).-2. The request shows under **Device approvals** at- [app.cua.ai/machines](https://app.cua.ai/machines) while it waits. The member+2. The machine shows as waiting for approval in the list at+ [app.cua.ai/machines](https://app.cua.ai/machines). The membersees that it is waiting for an admin.-3. An owner or admin chooses **Approve** or **Deny**. A denied device cannot open- team computers.+3. An owner or admin chooses **Approve** or **Deny**. A denied machine cannot open+ team machines.-Members see their own devices. Owners and admins see everyone's. Removing a+Members see their own machines. Owners and admins see everyone's. Removing amember deletes their approvals.-### Who can open a team computer+### Who can open a team machine-A person can open a team computer when all of these hold. The relay checks them+A person can open a team machine when all of these hold. The relay checks themwith 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 aremoved member loses access at once.-- The computer is on the team's list.-- Their device is approved (the owner's devices always are).+- The machine is on the team's list.+- Their machine is approved (the owner's machines always are).### Share a Space with the team-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 device+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 machinean 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 computers as its seats allow.+ own. A team can hold as many shared machines as its seats allow.- Choose **Can view** or **Can edit** for the whole team. Share again with theother 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 activeuntil 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 computers.+Free as a whole). Your Spaces and everything in them stay on your machines.Monthly plans have no refund for partial months. On a yearly plan, cancellingwithin 14 days of the first yearly charge refunds it in full, and after thatdiff --git a/docs/content/docs/spaces/guides/teleport-an-app.mdx b/docs/content/docs/spaces/guides/teleport-an-app.mdxindex 2ea33eed25..c659b89869 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 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.'+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.'---import { Callout } from 'fumadocs-ui/components/callout';import { Tab, Tabs } from 'fumadocs-ui/components/tabs';-**Teleport an app** lists every app installed on this computer and says what+**Teleport an app** lists every app installed on this machine and says whatteleport can do with each one in a Space:| Level | What happens in the Space | Moves |@@ -33,9 +33,9 @@ the entry's `sensitive_groups` and `TeleportPlanOptions.sensitive_groups`.Chrome (and Chromium) encrypts cookies and saved passwords at rest with aper-machine **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+cannot simply be copied to another machine. When **Keep me signed in** ischecked, teleport decrypts the cookies here (the OS asks you to allow that-Keychain read) and carries the decrypted values, not the source computer's+Keychain read) and carries the decrypted values, not the source machine'skey; the Space re-encrypts them under its own Safe Storage key before Chromeever reads them. The source's key never leaves this Mac.diff --git a/docs/content/docs/spaces/guides/troubleshoot.mdx b/docs/content/docs/spaces/guides/troubleshoot.mdxindex fda878f5c9..614b5966c4 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 computers 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 machines 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 computer that won't+Most problems are a Space that won't create, or an agent or machine that won'tconnect. This page covers a failed create in detail and points to the fix for therest.<Callout type="info">- If sign-in, connecting a computer or a download fails for everyone, check+ If sign-in, connecting a machine 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 tryfails too.-When a Space fails twice in a row for the same reason, on the same computer+When a Space fails twice in a row for the same reason, on the same machineand 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 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. |+| 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. || 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 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. |+| 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. || "The Cua daemon isn't running. Start Cua, or run `cua daemon start`." | Open Cua Spaces, or run `cua daemon start`. |-### Creating on another computer+### Creating on another machine-To create a Space on one of your other computers, that computer must be online,+To create a Space on one of your other machines, that machine must be online,provide Spaces, and be set up for your account. If the create fails with a namesuch 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-creatVersions 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 computer:+and system versions. Before anything leaves your machine:- 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 computer never appears, or shows **Offline** | [If it doesn't work](/spaces/guides/add-a-computer#if-it-doesnt-work) in Add a computer |+| 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 || 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 computer, 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 machine, 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 |## Nextdiff --git a/docs/content/docs/spaces/guides/uninstall.mdx b/docs/content/docs/spaces/guides/uninstall.mdxindex edf6cda0a6..aca942de3e 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-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.+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.<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 userPATH on Windows).-- The host service, after `cua host remove`, so this computer no longer shows up- as a computer in your account.+- The host service, after `cua host remove`, so this machine no longer shows up+ as a machine 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 device key: macOS Keychain items (including the old+- Your sign-in and the machine 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-device key) and the app's settings, for a later reinstall. Programs, services,+machine 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 computer, the local Cua Volume files+`--delete-spaces` deletes the Spaces on this machine, the local Cua Volume filesand 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.mdxindex a166b28e1a..94f2131320 100644--- a/docs/content/docs/spaces/guides/your-tailnet.mdx+++ b/docs/content/docs/spaces/guides/your-tailnet.mdx@@ -12,12 +12,12 @@ tailnet then does the networking and decides who is who:- **Identity.** A teammate is identified by their tailnet login (throughyour identity provider and its SSO and MFA). They need no Cua env token.-- **Access.** Your tailnet's ACLs decide which devices can reach the+- **Access.** Your tailnet's ACLs decide which machines can reach themachine at all; the machine's share list decides what each user may do.- **Rollout.** Your MDM or RMM installs the tailnet client as it alreadydoes; Cua uses it, and never installs or reconfigures it.-Nothing goes through cua.ai: no relay, no sign-in, no enrolled devices.+Nothing goes through cua.ai: no relay, no sign-in, no added machines.## Set the machine up@@ -51,9 +51,9 @@ change who may use it.## How identity worksFor each call from a tailnet address, the machine asks the local tailnet-client which user owns the calling device (`tailscale whois`, the same+client which user owns the calling machine (`tailscale whois`, the samelookup `tailscale serve` uses). It never trusts a name the caller sends. A-device tagged by ACL (`tag:ci`) belongs to no user, so it needs the env+machine tagged by ACL (`tag:ci`) belongs to no user, so it needs the envtoken. Login names match the share list case-insensitively; with Headscalethey are the Headscale user names (`bob`), with Tailscale usually emails.@@ -78,7 +78,7 @@ 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 enrolled devices |+| 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 || 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 |diff --git a/docs/content/docs/spaces/index.mdx b/docs/content/docs/spaces/index.mdxindex 117a9064f2..48b6596ece 100644--- a/docs/content/docs/spaces/index.mdx+++ b/docs/content/docs/spaces/index.mdx@@ -1,16 +1,16 @@---title: Cua Spaces-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.'+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.'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 computers to work on, and lets you-watch, step in and share them. You bring the computers: a Mac on your desk, a+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, aspare Linux box, a VM in your own cloud account. Cua does not rent them.-A **Space** is one desktop on one of those computers, set up for a task. Your+A **Space** is one desktop on one of those machines, set up for a task. Youragent runs commands in it and uses its apps and browser. You see the samescreen and take over when you want. You can share a Space with anyone who hasa 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 toClaude Code, Codex, Cursor and other agents.-3. [Add a computer](/spaces/guides/add-a-computer): connect another Mac, Linux- or Windows computer you own.+3. [Add a machine](/spaces/guides/add-a-computer): connect another Mac, Linux+ or Windows machine 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 computer I own, or reach my machines from my other machines | [Add a computer](/spaces/guides/add-a-computer) |+| Use another machine I own, or reach my machines from my other machines | [Add a machine](/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/meta.json b/docs/content/docs/spaces/meta.jsonindex 1398793c01..86e2075212 100644--- a/docs/content/docs/spaces/meta.json+++ b/docs/content/docs/spaces/meta.json@@ -5,7 +5,7 @@"index","quickstart","concepts/how-spaces-works",- "concepts/computers-devices-and-spaces",+ "concepts/machines-and-spaces","concepts/space-kinds","---Get started---","guides/install",diff --git a/docs/content/docs/spaces/quickstart.mdx b/docs/content/docs/spaces/quickstart.mdxindex 5bbc775c7f..d7320c13c2 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 computer your first Space and ask your agent to use it while you watch.+this machine your first Space and ask your agent to use it while you watch.<VideoDemosrc="https://trycua.github.io/assets/videos/cua-spaces/quickstart.mp4"@@ -22,10 +22,10 @@ this computer 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 computer from your other computers.- Everything on this computer works without one.+- A free Cua account, only to reach this machine from your other machines.+ Everything on this machine works without one.-Your computer is your first Space, so there is nothing big to download. An extra+Your machine is your first Space, so there is nothing big to download. An extraSpace is optional: a Linux Space needs a container engine such as Docker, and amacOS 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 computers, shared by your team and its agents."+Open Cua Spaces. The first screen says "Your machines, shared by your team and its agents."Press **Get started**.-**Pick your agent** lists the agents found on this computer, such as Hermes,+**Pick your agent** lists the agents found on this machine, such as Hermes,Claude Code, Codex, Cursor or OpenClaw, each with the settings file Cua addsitself to. Press **Connect** on each one you want to use. Nothing is connecteduntil 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 computer.+in a Space; these stay on this machine.No agent found? The screen offers to install one, or to use the `cua` commandin a terminal instead. If your agent was already open, close it and open itagain so it loads the new tools. See [Connect your agent](/spaces/guides/connect-your-agent).-## 3. Add your other computers (optional)+## 3. Add your other machines (optional)-**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+**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** atthe 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 computer".+Linux the request says "this PC" or "this machine".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@@ -109,7 +109,7 @@ open **Machines, This Mac**: it lists the two settings macOS asks for once.## Next-- [Add a computer](/spaces/guides/add-a-computer): use another computer you own.+- [Add a machine](/spaces/guides/add-a-computer): use another machine 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).