Work in a local or remote computer environment whose screen you can watch. Run commands, transfer files, launch coding agents, move signed-in app sessions, and share the host computer’s network when needed.
Work inside cua Spaces through the cua MCP server. A Space is a remote or local computer the user can watch; you can run commands in it, move files in and out, show its desktop or a single window on the user's screen, start coding agents inside it, teleport a signed-in app session into it, and share the host's network with it. Use when the user mentions Spaces, asks you to do work "in a Space", or wants a task isolated but visible.
Review the instructions the agent will receive before you install.
Spaces are exposed as MCP tools by the cua MCP server (cua mcp). If the
tools below are missing, ask the user to run cua agents setup or
cua auth login.
| Tool | Use |
|---|---|
list_spaces | See the Spaces you can use. Start here. |
create_space | A new Space: on = local (free, the user's machine), cloud (metered), or host:<name> (one of the user's machines set up with cua host setup); reuse: true returns a reachable one first. |
add_space / remove_space | Register an existing machine by URL and token, or forget one without deleting it. |
delete_space | Delete a Space's sandbox and stop metering. |
stop_space / start_space | Turn a local Space (or one your machines provide) off and back on: suspended or stopped, as power in list_spaces says. |
Prefer an existing Space. A cloud Space costs money: delete the ones you created when the task ends.
| Tool | Use |
|---|---|
space_bash | Run a shell command (space, command, optional timeout). |
space_write | Write text to a file. |
upload / download | Copy files or folders in and out. |
send_file | Drop a host file into the Space's Downloads (sha256 verified). |
list_tools / call_tool | Reach MCP services running inside the Space. |
| Tool | Use |
|---|---|
open_space_viewer | Open the full desktop viewer. |
show_space_pip / hide_space_pip | Picture-in-picture on the user's screen. |
list_space_windows / stream_space_window | Show one window from the Space. |
stream_endpoint | Get a ticketed media URL for the desktop or a window. |
| Tool | Use |
|---|---|
agent_capabilities | Which agent harnesses the Space supports. |
agent_start | Start an agent run (space, agent, prompt). |
agent_status / agent_message / agent_stop / agent_list | Follow, steer and stop runs. |
teleport_manifest | Preview what moving an app session would copy. |
teleport_app | Move a signed-in app session (tabs, profile) into the Space. |
hotspot_start / hotspot_status / hotspot_stop | Share the host's network with a Space. |
To host Spaces on a machine you reach only over ssh (a spare Mac mini on the user's Tailscale, or the LAN):
curl -fsSL https://cua.ai/install.sh | sh -s -- -y --select spaces,host --no-onboarding.cua auth login --remote prints a device code and a
URL. Show both to the user and have them approve it (on another signed-in
device or at the URL).cua host setup --profile spare --name "<name>" hosts Spaces only (no
desktop sharing), through the cua.ai relay.create_space(on="host:<name>", count=2), or
cua spaces create macos:26 --on "<name>" --count 2.host:<name> only resolves machines set up with cua host setup (they
register with the relay). direct:<addr> attaches one Space that is already
running at that address (add_space) and cannot host new ones.
teleport_manifest and tell the user what will move before
teleport_app; sensitive items need their explicit acknowledgement.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Operate native apps on macOS, Windows, and Linux using identified controls, menu paths, or screen coordinates. Target a specific window, verify the result after each action, and consult available recent activity when resuming work.
Create disposable Linux or macOS computers for running code, testing apps, operating desktop interfaces, and browsing websites. Use isolated environments locally or in the Cua cloud, then delete them when the work is complete.
Save agent memory and outputs in Cua Volume, shared storage that persists beyond a Space, the working environment. Hand files to the user, read shared references, and check synchronization, version history, and conflicting edits.
Operate apps and websites by inspecting screenshots, clicking controls, typing, and dragging. Use it to fill forms, check layouts, and test complete user flows, with recorded actions available for replay and review.
Build a computer-control loop where Cua Driver observes and acts, while TypeSafe Jev chooses from predefined actions. Validate each choice, execute one action at a time, and verify the result before continuing.
Review open GitHub issues, proposals, and pull requests to identify useful maintainer work. Get ranked candidates with evidence, dependencies, and validation needs, then begin work only on an item you explicitly select.