Local VM
A separate Linux desktop in Docker or Podman on your own machine, shared or one per bot.
When to use it
Use it when a bot needs a full desktop, such as a browser plus downloads or a Linux app, and you don't want it anywhere near your own screen. It's also the way to give a bot a desktop on Windows, where This computer isn't available.
What you need
- A container runtime: Docker Desktop, Docker Engine, or Podman. Colima also works. Podman and Colima are free. Docker Desktop may need a paid license for larger companies and government use.
- On Windows, Podman is preferred.
- Enough memory and disk for the desktop image and each running desktop.
- An engine that can use it. Otherwise Murage says "This model engine cannot use the Local VM. Choose Claude or an ACP engine."
Set it up
Open SettingsLocal VM. The Setup card walks you through four steps.
Step 1
Install a container runtime
Murage shows the install command for your system, or a link to Open the Podman installation guide.
You're done when: a runtime such as Docker or Podman is installed.
Step 2
Start the container runtime
Open it and start its engine, then choose Re-check.
You're done when: you chose Re-check and the card moves on.
Step 3
Prepare the Cua desktop
This is a one-time download and build. Choose Prepare Cua desktop.
You're done when: the one-time download and build has finished.
Step 4
Create and start the Local VM
Choose to create and start the Local VM. In per-bot mode, use Create a private desktop from each bot's Computer panel instead.
You're done when: the card at the top says Ready or Ready for per-bot desktops.
Shared or per bot
The Isolation card has two modes:
- Shared: one desktop that bots use one at a time, backed by one workspace.
- Per bot: each bot gets its own container, workspace, viewer, lease and idle timer. Different bots can work at the same time.
Maximum per-bot desktops sets how many can exist, from 1 to 4. Per-bot mode needs Docker or Podman. Apple's own container tool only works in shared mode.
Give a bot the Local VM
Step 1
Open the bot's computer
Open the bot's chat and choose Bot's computer at the top.
You're done when: the computer panel is open.
Step 2
Choose Local VM
- Under Runs on, choose Local VM.
- In per-bot mode, choose Create name's VM.
You're done when: Runs on shows Local VM.
Step 3
Watch, or take over
The panel shows a watch-only preview. From there:
- Open live desktop opens the desktop inside Murage.
- Take control pauses the bot's hands and opens the live desktop for you to drive.
- Open two desktops shows two Local VM bots side by side without pausing either. Only one pane holds control at a time. Choose a bot for the second pane from Choose a Local VM bot.
- Delete this bot's VM removes its desktop. Its private workspace stays. Stop the bot's turn first.
You're done when: you see a watch-only preview of the desktop.
Limits and storage
- Memory and CPU. Each running desktop can use up to 4 GB of memory, 2 CPUs and 512 processes.
- Idle timer. An idle desktop stops after 8 hours without activity.
- Workspace. Each bot's workspace is a private folder on your computer, mounted in the desktop at
/home/cua/workspace. Files and browser sign-ins there survive when the desktop is replaced. Everything else inside the desktop is disposable. - Viewer. The viewer is only reachable from this computer. The desktop itself can still reach the internet.
Troubleshooting
The status line names the next thing to fix.
You see
Install a supported container runtime firstDo this
Also shown as "Start Docker first". Finish setup steps 1 and 2, then choose Re-check.
You see
Prepare the Cua desktop image...Do this
Run step 3.
You see
Per-bot mode requires Docker or PodmanDo this
Switch from Apple's container tool to Docker or Podman, or use Shared.
You see
The existing Local VM uses an older desktop or Cua Driver; recreate itDo this
This is any message ending "recreate it". Choose Delete and recreate in Settings, or Replace name's VM in the bot's panel. The workspace folder is kept.
You see
The Local VM started, but Cua Driver is not ready yetDo this
Wait a moment and check again.
You see
Murage could not inspect the container runtime.Do this
Choose Re-check, or look at the app logs.
You see
This VM is already controlled in another viewer. Hand it back there first.Do this
Release control in the other pane.
You see
Two desktops are slow on WindowsDo this
Both share the same Podman machine's CPU, memory and disk. Give that machine more resources in Podman Desktop.