Getting started, and answers to common questions.

macOS workspaces (macOS 13 or later): shared folders mount automatically — open Finder and look under /Volumes/My Shared Files. No command needed.

Linux workspaces: each shared folder gets its own mount command, shown right in the app under the workspace's Shared Files tab. It looks like this, using that folder's own tag:

mkdir -p /mnt/my_folder
sudo mount -t virtiofs <folder-tag-shown-in-app> /mnt/my_folder

Use the exact tag shown in the app — it's unique per folder, so copying a command from somewhere else won't work.

Clipboard sharing on Linux depends on an agent running inside the guest. Work through these in order:

1. In the workspace's Resources tab, confirm Clipboard Sharing is turned on.
2. Inside the guest, make sure spice-vdagent is installed:

   sudo apt install spice-vdagent

3. Confirm the agent is actually running:

   systemctl status spice-vdagentd

   If it's inactive, start it with sudo systemctl start spice-vdagentd and, if you're on a graphical desktop, log out and back in so the desktop session picks it up.
4. Some minimal or headless desktop environments don't launch spice-vdagent automatically — check your desktop environment's autostart settings if it still doesn't work after the agent is installed and running.

Clipboard sharing currently works for Linux workspaces only.

Debian uses the same apt and update-binfmts tooling as Ubuntu. Turn on Rosetta for the workspace in its Resources tab, start the workspace, then run this once inside the guest:

sudo mkdir -p /media/rosetta
sudo mount -t virtiofs rosetta /media/rosetta

sudo apt-get update
sudo apt-get install -y binfmt-support

sudo /usr/sbin/update-binfmts --install rosetta /media/rosetta/rosetta \
  --magic "\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x3e\x00" \
  --mask "\xff\xff\xff\xff\xff\xfe\xfe\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff" \
  --credentials yes --preserve yes --fix-binary yes

Fedora doesn't ship Debian's update-binfmts tool, but it does ship systemd-binfmt, which reads the exact same kernel binfmt_misc registration from a config file. Turn on Rosetta for the workspace in its Resources tab, start the workspace, then run this once inside the guest:

sudo mkdir -p /media/rosetta
sudo mount -t virtiofs rosetta /media/rosetta

sudo mkdir -p /etc/binfmt.d
sudo tee /etc/binfmt.d/rosetta.conf > /dev/null <<'EOF'
:rosetta:M::\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x3e\x00:\xff\xff\xff\xff\xff\xfe\xfe\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/media/rosetta/rosetta:CF
EOF

sudo systemctl restart systemd-binfmt

The rosetta.conf file persists across reboots, so this is a one-time setup per workspace.

1. Install and run Ollama on your Mac, outside the workspace.
2. Enable AI Bridge for the workspace (on by default in the AI Sandbox profile, or turn it on yourself in the workspace's Integrations or Resources settings).
3. Start the workspace, then open its AI Bridge tab — it shows the local endpoint address and, for a Linux guest, the exact commands to forward the connection.
4. Inside the workspace, point your tooling at that address the same way you'd point it at any local OpenAI-compatible server.

It's deleted automatically the moment you close it, including its disk. There's nothing to recover afterward — don't use a disposable workspace for anything you need to keep.

Stop the workspace, then choose Save as Base Image from the banner shown on a stopped workspace. Saving the same workspace again later creates a new, independent base image rather than overwriting the previous one — manage and delete base images you no longer need from Preferences → Base Images.

Workspace disks and base images live under ~/Library/Application Support/VeloWorkspaces on your Mac. Delete workspaces you no longer need from the library, and unused base images from Preferences → Base Images, to free up space.

Not in this release. Velo Workspaces currently supports Linux and macOS guests.

CPU, memory, storage, shared folders, and a few other settings are part of the virtual machine's configuration and can't be changed while it's running (Apple's Virtualization framework doesn't support hot-plugging them). Stop the workspace, make the change, and start it again.

macOS guests require an Apple silicon Mac as the host. On an Intel Mac, Linux guests are still fully supported.