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.
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.
Review the instructions the agent will receive before you install.
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.
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.
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.
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.