Use Grok Bot, Dots and pi with Spaces

Set up Cua Spaces from Grok Bot or Dots, or use a Space as your pi workspace.

Use Cua Spaces from your agent's Linux computer or as a workspace for pi.

You want	Use
Your agent to set up a controllable Linux VM	Grok Bot or Dots
Your local pi session to work on a Space	pi with pi-cua

Grok Bot and Dots#

Both agents have their own Linux computer. Paste this prompt into either agent:

set up cua spaces on your computer as a controllable linux vm (not a container), giving yourself kvm access if needed. once you've set it up, walk me through what cua spaces can do, and how to make the most of it.

The agent sets up a controllable Linux VM, not a container. You only need to paste the prompt. Here is a short example of what it runs.

Install the CLI:

curl -fsSL https://cua.ai/install.sh | sh -s -- --cli-only --yes

Check the runtime, create a VM, and list Spaces:

cua runtime doctor
cua sb create linux --kind vm --name dev-vm
cua spaces ls

QEMU needs read and write access to /dev/kvm. The agent can check access and grant it if needed. See Install Cua and Connect your agent.

pi#

Use the public pi-cua extension with local Spaces or computers you add.

Install the extension:

pi install git:github.com/injaneity/pi-cua

Open pi and run /space. If pi was already open, run /reload first.

Command	Action
`/space`	List Spaces and open the picker.
`/space <name>`	Enter a Space.
`/space local`	Bring work back into your checkout and run locally.
`/space create [name]`	Create a Space, after confirmation. Requires a supported local runtime.
`/space delete <name>`	Delete a Space, after confirmation.
`/space auth`	Check the GitHub CLI on the Space without showing credentials.

The Space needs Node.js 22+ and Git. pi is not installed on the Space. Local Spaces need no Cua account.

pi stays on your computer with your extensions, skills, settings and model keys. On a chosen Space, workspace tools (read, write, edit, bash, find, grep and !) run there. When you return with /space local, Git changes come back to your checkout and workspace tools run locally again.

Credentials stay on their own machine

No tokens, SSH keys or credential files are copied.

Linux and macOS Spaces are supported. Windows is experimental and not runtime-tested; it uses Git for Windows Bash. Submodules are not transferred. Transfers are limited to 200 MiB. Sessions on one Space share its user, files and logins.