Computers
Give a bot its own browser, a separate desktop, a cloud computer, or careful use of your own computer.
Choose where a bot works
Step 1
Open the computer button
Open the bot's chat and choose the computer button at the top.
You're done when: you see Computer destination.
Step 2
Pick a destination
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.
You're done when: the bot shows the destination you picked.
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, Windows and Linux)
Each bot can have its own browser inside Murage. You watch it browse live and can take over at any time.
Step 1
Check the workspace switch
The switch is on by default. To check it, open SettingsDevicesBuilt-in browser.
You're done when: the Built-in browser switch is on.
Step 2
Switch it on for the bot
Bots start with the browser off. Switch it on in the bot's settings.
You're done when: the bot's browser is on.
Step 3
Open the Browser tab
Open the Browser tab in the bot's computer panel.
You're done when: you see the bot browse live.
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.
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.
Step 1
Connect Chrome
- In Chrome, open
chrome://inspect/#remote-debuggingand turn on remote debugging. - Keep Chrome open.
- Chrome asks you to allow each connection.
You're done when: Chrome asks you to allow the connection, and you allow it.
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.
Step 1
Install and start Docker or Podman
Install and start Docker or Podman. On Windows, Podman is preferred.
You're done when: Docker or Podman is running.
Step 2
Prepare the desktop
Open SettingsLocal VM, prepare the desktop (a one-time download), and choose Per bot.
You're done when: the desktop is prepared and Per bot is chosen.
Step 3
Set how many desktops
Set Maximum per-bot desktops if you want more than one.
You're done when: the number is set.
Step 4
Pick Local VM for a bot
Pick Local VM in a bot's computer panel.
You're done when: the bot's computer panel shows Local VM.
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.
Step 1
Get an API key
Create an account and an API key at ascii.dev.
You're done when: you have an API key from ascii.dev.
Step 2
Paste it into Murage
Paste it in SettingsTools & ConnectionsBox API key.
You're done when: the key is saved.
Step 3
Pick Cloud for a bot
Pick Cloud in a bot's computer panel.
You're done when: the bot's computer panel shows Cloud.
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.
Step 1
Add the SSH alias
Add the SSH alias in SettingsTools & Connections.
You're done when: the alias is saved.
Step 2
Choose the cloud backend
In the bot's computer panel, choose Cloud, then Self-hosted VPS as the cloud backend.
You're done when: the bot's computer panel shows Self-hosted VPS.
Step 3
Let Auto start it (optional)
Turn on Start VPS automatically if Auto may start it for you.
You're done when: the switch is on, if you want it.
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.