Use Cua Volume, the one volume every Space and agent of this user shares. Inside a Space it is mounted as a folder (/volume on Linux, ~/Cua Volume on macOS), so any program reads and writes it directly. Use it for anything that must outlive this Space - your memory and outputs in your agent home, shared reference in public/ - and to hand files to the user or to other agents. Use when the user mentions the volume, Cua Volume, shared files, your home or memory, or saving results.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
One versioned volume per user. Every write is a new version; deletes keep history. The same files appear on the user's Mac (Finder) and in every Space, within seconds.
| Where you run | Path |
|---|---|
| A Linux Space | /volume (or ~/Cua Volume when /volume is absent) |
| A macOS Space | ~/Cua Volume |
| No mount (Windows for now, or the Space has none) | use the volume_* tools below |
Check that it is mounted, not just present: mountpoint -q /volume on Linux,
ls ~/"Cua Volume" on macOS. A /volume holding only
CUA-VOLUME-UNAVAILABLE.txt (read-only) is not the volume: the file says
why (for example, a container without /dev/fuse). If it is not mounted, use
the tools; nothing written to an unmounted folder is saved.
| Folder | You (an agent in a Space) |
|---|---|
public/ | read only: shared reference from the user |
agents/<you>/ | read and write: your home (memory, outputs/, inbox/) |
spaces/<this space>/ | read and write: this Space's scratch and outputs |
| another agent's home, another Space | not visible; ask with volume_request_access |
Put results the user should see in agents/<you>/outputs/ (or this Space's
folder) and tell them the path. A refused write means the folder is not
yours: do not retry elsewhere to get around it, ask.
| Tool | Use |
|---|---|
volume_ls, volume_read, volume_write | The same files without the mount; each file's sync state |
volume_delete, volume_history, volume_restore | Where offered: delete, old versions, restore one |
volume_request_access | Ask the user for more (a folder, r or rw, and why); they approve in Cua |
volume_sync_status | Sync health, each device's last sync, your files still uploading, conflicts |
Inside a Space these tools answer from the user's machine, so they show its view of sync, not only this Space's.
volume_sync_status: feed is live (syncing),
off (storage on this machine only: nothing to wait for) or offline
(the bucket is unreachable, see last_error: say so rather than trust a
stale file). devices shows when each device last synced.volume_ls and volume_read mark a file with sync when it matters:
pending_upload (not yet stored, other devices cannot see it yet),
conflict (a write lost to a later one; kept at conflict_path),
conflict_copy, and written_by when another device wrote it last.name (conflict from <device> <date>).ext. Nothing
is lost. Do not delete a conflict copy yourself: tell the user, or merge
the two into the current file if the task asks for it.API keys, tokens, passwords and private keys belong in the user's Keyvault.
Writes to agent homes are scanned; a write with a secret is refused
(secret_detected) and logged. Do not work around the refusal: remove the
secret.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Drive a native GUI app (macOS, Windows, Linux) via the cua-driver CLI (default) or MCP server; snapshot its accessibility tree, act through snapshot-bound element tokens, native menu paths, exact window geometry, or pixel coordinates, and verify from fresh state. Use when the user asks you to operate, drive, automate, or perform a GUI task in a real application on the host, or to continue, resume, or recall recent Cua activity.
日本語の概要は準備中です。原文の説明を表示しています。
Create, use and clean up cua sandboxes (disposable Linux or macOS computers) locally or in the Cua cloud with the `cua` CLI or the cua SDK, and browse the web inside one. Use when a task needs an isolated machine to run code, test an app, drive a desktop GUI, browse or test a website, fill a web form, take a web page screenshot, or reproduce something without touching the user's own computer.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to visually interact with a GUI: test buttons, fill forms, verify visual layouts, fuzz web pages, automate user flows, take screenshots, or perform end-to-end QA on any application. Works on cloud VMs, Docker containers, local machines, and sandboxes. Needs the `cua` CLI (curl -fsSL https://cua.ai/install.sh | sh).
日本語の概要は準備中です。原文の説明を表示しています。
Build or adapt a bounded computer-use loop where Cua Driver observes and acts, TypeSafe Jev selects only from application-owned candidate IDs, and the caller validates and verifies every action. Use for the jev-use recipe or similar Jev integrations; do not use it to add model logic or credentials to Cua Driver.
日本語の概要は準備中です。原文の説明を表示しています。
Poll and rank open GitHub issues, RFCs, and pull requests for maintainer work, or start one explicitly selected item. Use when a user asks what to work on, requests backlog priorities, says "poll work," wants actionable issues or pull requests, or says "start
日本語の概要は準備中です。原文の説明を表示しています。