Computer use and the browser
Fix a bot that can't see or control your screen, a built-in browser that won't open, Use my Chrome that won't connect, and Local VM, Box or VPS computers that won't start.
What works where
- This computer (your own screen). Mac, and Ubuntu on an Xorg session. Not Windows.
- Built-in browser. Mac, Windows and Linux.
- Local VM, Box and VPS. Every system.
Your own screen
You see
A bot can't control my MacDo this
- Open System SettingsPrivacy & Security.
- Under Accessibility, switch Murage on.
- Under Screen Recording, switch Murage on.
- Restart the control session in Murage after granting either one. macOS only applies these permissions to a fresh session.
If you chose Don't allow when the bot first asked to touch your screen, choose Ask again to reset it.
Watching the screen never grants control. Every action still goes through approvals.
You see
A bot can't control my Ubuntu desktopDo this
- Screen control works only on Ubuntu on Xorg. On the default Wayland session it's switched off. Sign out, choose the gear icon on the sign-in screen, pick Ubuntu on Xorg, and sign in again.
- You need both the global Enable local control switch and This computer chosen for the bot.
- Screen preview working doesn't mean control is on. Preview works on Wayland. Control doesn't.
You see
Not available on this platformDo this
On Windows, This computer isn't available yet. Use a Local VM desktop instead, which includes a browser.
The built-in browser
You see
The built-in browser won't appearDo this
- Check the app switch, which is on by default: SettingsDevicesBuilt-in browser.
- Then turn it on for the bot. Imported bots and bots your Chief creates start with the browser off.
- Open the bot's Computer panel and choose the Browser tab.
You see
The browser won't let the bot see a pageDo this
When a page has a password or secret field, Murage doesn't pass that page's contents to the bot. After you type into such a field yourself, the session stays protected until you reopen it. That's deliberate. Sign in yourself, then reopen the page or move to a page without a password field.
The browser also refuses downloads, site permission prompts, and local or internal addresses. Only normal web pages open.
You see
Logins keep disappearingDo this
Check which profile the bot uses. Guest forgets everything when you switch away. The bot's own profile keeps its logins private to that bot. A named shared profile can be used by several bots.
You see
Use my Chrome won't connectDo this
- It needs Google Chrome 144 or later.
- Switch on remote debugging at
chrome://inspect/#remote-debuggingin Chrome. - Chrome must stay open, and it asks you to allow each connection. Allow it.
- Only one opted-in bot can use your Chrome.
You see
Taking over from the botDo this
Choose Take control, or just click into the page. The bot pauses while you drive. Choose Return to bot when you're done.
Other computers
You see
Local VM won't startDo this
- Install Docker or Podman and make sure it's running. On Windows, Podman is recommended.
- Check you have enough free memory and disk.
- Two desktops can run side by side by default. Stop one if you hit the limit.
You see
Box cloud computer won't startDo this
- Check your Box key in SettingsTools & Connections.
- Box is a paid service from ascii.dev after its trial. An error about a plan comes from ascii.dev, so check your account there.
- A stopped box takes a few seconds to resume. Its disk is kept, but its address changes.
You see
Your own VPS won't connectDo this
- The server must be x86_64 Linux with Docker, reachable through an SSH alias on your computer.
- Test the alias yourself with
ssh <alias>first. - Files inside the VPS container are disposable. Keep important work somewhere durable.
You see
Android phone control doesn't connectDo this
The phone must be connected by USB with USB debugging switched on in its developer options, and you must allow the computer on the phone when it asks.
See also: Computers.