Cua Spaces: a separate desktop for AI agents

By AiCoN | Published 7 October 2026 | Sources checked 7 October 2026

Cua Spaces gives AI agents a desktop you can watch. A Space can run locally, on another team machine or in your cloud. Separate desktops can limit exposure, but do not make every agent action safe.

Official publisher artwork hosted by its publisher. Official source. Independent guide, not affiliated or sponsored. Artwork and trademarks belong to their owners.

What is a Space?

The documentation describes a container or virtual machine with a screen that streams to you and accepts input. You can register a machine, send files and move supported apps into a Space. The Mac app puts Spaces in the menu bar and notch.

The SDK is available for Python, TypeScript, Swift and Rust. It is developer-oriented, not a ready-to-use everyday assistant. Cloud machine setup and agent/model access are separate parts of the work.

Licence and costs

Cua Spaces is source-available under FSL-1.1-MIT. The official licence overview says use, modification and self-hosting are allowed except competing commercial products or services. Each release becomes available under MIT after two years. Other parts of the repository have different licences; do not call the entire Spaces product unrestricted MIT software.

Current official pricing: Free is $0 with up to 2 live relay sessions and 20 remote hours a month. Pro is $18 monthly or $180 billed yearly ($15/month equivalent). Teams is $30 per seat monthly or $300 per seat billed yearly ($25/month equivalent), for 1-100 seats. Each Teams seat adds 5 live sessions and 200 remote hours to a shared pool. Your own computer, cloud VM, models and other services are separate costs. These are USD prices as checked, not an INR quote or a checkout total including any applicable tax.

Pro includes up to 5 live sessions and 200 remote hours monthly. Direct/local connections do not use relay allowance. The pricing FAQ says exceeding the remote-hours allowance shows an upgrade notice rather than cutting access off. There is no paid-plan trial. Plans renew until cancelled; the current terms describe a full refund within 14 days of the first yearly charge, but no partial-month refund. No purchase or cancellation was tested.

Teams is no longer described here as only a waitlist: the official docs now describe buying it. SSO and audit export are not included yet; expiring share links and Pro audit history are marked coming soon. The pricing page says named-person sharing is included in Free, but the Plans and Teams docs say sharing is Teams-only and within the team. This is an unresolved official-source conflict. Verify the exact sharing workflow before relying on a Free or Pro plan.

Install docs now cover macOS 26 or later, Windows x64/Arm in preview, and supported Ubuntu 24.04 x64/arm64 packages. A macOS guest Space needs Apple silicon; Linux Space runtimes have separate Docker/QEMU requirements. Read the installation guide for your exact host. We did not install or benchmark any platform.

How to begin cautiously

1. Read the Spaces overview and the official repository licence table.
2. Choose a local test machine or a cloud account with a budget limit. Check current system requirements.
3. Use the official create/add-Space guide for the chosen environment.
4. Start with a test folder and an account that contains no private client data.
5. Send only the files and app access the task needs. Treat signed-in apps as access to real accounts, not just a picture of the app.
6. Watch a simple task on screen and check its result before giving it broader actions.
7. Review Settings, General, Launch Cua Spaces at login. The docs say it is on after setup unless unticked.
8. Remove test files and credentials, stop unused machines and check any cloud bill.

Why the boundary matters

A separate desktop can keep an agent away from the rest of your computer. But copied files and signed-in apps can still reveal information or permit real actions. An agent can make a wrong click inside a sandbox too. Keep backups and review deletes, messages and spending.

For an Indian developer, also consider where a cloud machine runs and whether work data may leave the organisation. No India-specific privacy or hosting claim was confirmed.

What changed since the original post?

The original review clarified FSL restrictions and automatic-login startup. This scoped recheck adds the current Free/Pro/Teams plans, platform requirements and the conflicting sharing descriptions. No Space was installed, account created, payment made or app teleported.

Frequently asked questions

Is every component MIT licensed?

No. Spaces-specific components use FSL-1.1-MIT; the official licence table separates them from MIT parts.

Is a sandbox a guarantee?

No. Access inside it still needs careful limits and review.

Is there a confirmed free plan?

Yes. The pricing page now lists Free, Pro and Teams with relay limits. Free is not free cloud compute; see the costs and unresolved sharing conflict above.

Sources: Cua Spaces docs · Official licence overview · Actual Spaces component licence. Checked 7 October 2026. · Current pricing · Plans and Teams · Install requirements

Scoped recheck 24 October 2026: official pricing, plan docs, installation docs and licence files checked. Original publication date retained. Sharing scope differs between the official pricing page and Teams docs; no account, purchase, install, security or live agent task tested.