Computers

A bot can work without a computer, browse the web in its own browser, work in a separate desktop, or use your screen and apps. You choose per bot.

Choose where a bot works#

Open the bot's chat and choose the computer button at the top. Under Computer destination, pick one:

• Auto: use a computer that's already set up.
• Cloud: a hosted desktop (Box, or your own server).
• Local VM: a separate desktop on your own machine.
• This computer: your screen and apps.
• Browser: web pages only.
• Off: no desktop access.

Watching a screen doesn't give a bot control of it. Control is always a separate choice.

Not every engine can use every option. Murage tells you when you need a different one, for example "Choose Claude or an ACP engine".

The bot's own browser (Mac and Linux)#

Each bot can have its own browser inside Murage. You watch it browse live and can take over at any time.

1. Switch it on for the workspace: Settings → Experimental → Built-in browser.
2. Switch it on for the bot. Bots start with the browser off.
3. Open the Browser tab in the bot's computer panel.

While it browses, choose Take control, or just click into the page. The bot pauses while you drive. Choose Return to bot when you're done.

Under Profile, pick where its logins live: the bot's own private profile, a shared profile you name (such as "Work"), or Guest, which forgets everything.

When a page has a password field, the bot never sees what's in it. You type the password yourself.

The built-in browser is not available on Windows yet.

Use my Chrome#

For one bot you trust, Murage can use your own signed-in Google Chrome instead. Choose Use my Chrome under Profile. You need Chrome 144 or later:

1. In Chrome, open chrome://inspect/#remote-debugging and turn on remote debugging.
2. Keep Chrome open.
3. Chrome asks you to allow each connection.

This computer (macOS, and Ubuntu on Xorg)#

A bot can use your own screen, mouse and keyboard.

• Mac: Murage needs Accessibility and Screen Recording permission. After you grant either one, restart the control session when Murage asks.
• Ubuntu: works on an "Ubuntu on Xorg" session only. Ubuntu's default session is Wayland, so sign out and choose "Ubuntu on Xorg" on the sign-in screen first.
• Windows: not available. Use a Local VM or a cloud computer instead.

Control is off by default. A bot on Auto asks once before it first uses your screen: choose Allow for this bot or Don't allow. Choose Ask again in its computer panel to change your answer. Choosing This computer for a bot counts as your yes. Set a bot to Off if it should never touch your screen.

Local VM

A separate Linux desktop that runs on your own machine in Docker or Podman, one per bot.

1. Install and start Docker or Podman. On Windows, Podman is preferred.
2. Open Settings → Local VM, prepare the desktop (a one-time download), and choose Per bot.
3. Set Maximum per-bot desktops if you want more than one.
4. Pick Local VM in a bot's computer panel.

Each running desktop can use up to 4 GB of memory and 2 CPUs. Files and browser sign-ins in its workspace survive when the desktop is recreated. You can watch two Local VM desktops side by side.

Cloud computer (Box)

Box is a hosted Linux desktop with Chrome and a terminal, from ascii.dev. Each bot gets one that sleeps and wakes, and its disk is kept.

1. Create an account and an API key at ascii.dev.
2. Paste it in Settings → Tools & Connections → Box API key.
3. Pick Cloud in a bot's computer panel.

Box is a paid service after its trial, billed by ascii.dev on your own account. By default a box stops after 8 hours (2 hours on a trial). The bot itself, its schedule and your data stay on your computer; only the desktop is remote, so Murage must still be running.

Your own server

Instead of Box, you can use your own x86_64 Linux server with Docker, reached through an SSH alias.

1. Add the SSH alias in Settings → Tools & Connections.
2. In the bot's computer panel, choose Cloud, then Self-hosted VPS as the cloud backend.
3. Turn on Start VPS automatically if Auto may start it for you.

The container publishes no ports. Take control opens its desktop in Murage through a temporary SSH tunnel. Treat its files as disposable and move results out before you delete it.