This computer
Let a bot use your own screen, mouse and keyboard on macOS or Ubuntu on Xorg, and how Murage asks before it does.
When to use it
Use it when the work has to happen in an app on your machine: a desktop program with no web version, a file you have open, or a site you're already signed in to in your everyday browser.
For anything else, pick something lighter:
- Web pages only: the built-in browser.
- A desktop that isn't yours: a Local VM, a cloud computer or your own VPS.
Where it works
- macOS: yes.
- Ubuntu: yes, on an Ubuntu on Xorg session only. It's switched off on a Wayland session.
- Windows: not available yet. Use a Local VM, a cloud computer or your own VPS instead.
Not every engine can do it. If the engine can't, the option is greyed out and Murage says "This model engine cannot control this computer. Choose Claude or an ACP engine."
Set it up on a Mac
Step 1
Open the computer panel
Open the bot's chat and choose Bot's computer at the top to open its computer panel.
If Murage doesn't have permission yet, you'll see Allow control of this computer. It says Murage needs Accessibility and Screen Recording in System Settings.
You're done when: you see the bot's computer panel.
Step 2
Give Murage permission
Choose Open System Settings and turn on Murage under both Accessibility and Screen Recording.
Come back to Murage and choose Retry. macOS may still ask you to relaunch the app before the new permission takes effect.
You're done when: Murage is switched on under both Accessibility and Screen Recording.
Step 3
Pick This computer
Under Runs on, choose This computer, or leave the bot on Auto (see below).
You're done when: Runs on shows This computer, or the bot is on Auto.
Set it up on Ubuntu
Ubuntu's default session is Wayland, and Murage won't control a Wayland desktop.
Step 1
Switch to Xorg
Sign out. On the sign-in screen, choose Ubuntu on Xorg, then sign in again.
You're done when: you are signed in to an Ubuntu on Xorg session.
Step 2
Turn on local control
- Open the bot's computer panel. Find the Local control card, marked Beta.
- Choose Enable local control (Beta). Murage checks the driver and your desktop session.
You're done when: the card says Ready.
Step 3
Choose This computer for the bot
When the card says Ready, choose This computer under Runs on for the bot you want.
You're done when: Runs on shows This computer for that bot.
On Linux, a bot only gets your screen when you choose This computer for it. Auto on Linux uses a cloud box when one is set up; otherwise computer use stays off. Every local action on Linux asks you first. Bot actions use a private cursor, so your own pointer stays under your control.
To turn it off again, choose Disable local control in the same card.
How Murage asks before using your screen
There are three cases:
- You chose This computer for the bot. Murage doesn't ask separately. Choosing it is your answer.
- The bot is on Auto (Mac). Auto uses a cloud box if one exists, otherwise this computer. The first time the bot would act on your screen, a card appears in the chat: "Let @name use this computer?" Choose Allow for this bot and Murage remembers it for that bot. Choose Don't allow and Auto keeps that bot off your screen. It's asked once for each bot on Auto.
- The bot is Off. It never touches your screen.
If you don't answer the card within 15 minutes, it closes and nothing is remembered. The next time the bot tries, it asks again.
To change your answer, open the bot's computer panel. Under Using this computer on Auto you'll see Allowed for this bot. or Not allowed. Auto keeps this bot off your screen. Choose Ask again to reset it.
Bots that already used this computer before this check existed keep working without the question.
Approval levels on this computer
The first-use question is separate from the bot's approval level. Ordinary actions still follow permissions and the stop line.
When you put a bot that uses this computer on a higher level, Murage warns you first:
- Allow Auto mode on this computer? The bot can click, type and run tools without asking first. Destructive and sensitive actions still stop.
- Allow Full access on this computer? It still asks before deleting outside its folder, paying, messaging someone new, and reading your keys.
- Allow No limits on this computer? It can click, type and run anything without asking first, except reading the keys and sign-ins you have given Murage, commands Murage recognizes as able to wipe your computer, and commands Murage cannot read in full.
Watch and stop
Step 1
Preview the screen
Start preview in the computer panel shows a private, view-only preview of your screen. Choose Stop preview when you're done. On Ubuntu you pick the screen with Choose a screen.
You're done when: you see a private, view-only preview of your screen.
Step 2
Take the screen back
While a bot is using your screen, a red card says "name is using this computer". Choose Stop using this computer to stop it and take the screen back. An action already underway can still finish, so check the screen afterwards.
Switching the bot to Off while it's working on your screen also stops it.
You're done when: the red card is gone and the bot has stopped.
Troubleshooting
You see
No frames yet; the preview needs Screen Recording permission. After granting, relaunch the app.Do this
Grant Screen Recording, then quit and reopen Murage.
You see
Unavailable on WaylandDo this
Also shown as "Local computer control is not available on Wayland yet. Sign out and choose Ubuntu on Xorg to use This computer." Switch to an Ubuntu on Xorg session.
You see
Enable the local control beta and complete the Cua Driver checks first.Do this
Choose Enable local control (Beta), then Try again if the card says Needs attention.
You see
CUA Driver is not ready for local computer control.Do this
On a Mac, check both permissions and choose Retry.
You see
Local computer control requires the desktop app.Do this
You're in Murage through a browser. Use the desktop app on the computer itself.
You see
The selected provider cannot request approvals for local computer actions.Do this
Switch the bot to an engine that can, such as Claude or an ACP engine.