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.
This computer lets a bot see your screen and use your mouse and keyboard, the way you would. Murage drives the desktop through its bundled Cua Driver, so the operating system sees Murage as the app asking for control.
It's the most powerful computer option and the one that needs the most care. Control is off until you set it up, and Murage asks before a bot first touches your screen.
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
- 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.
- 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.
- Under Runs on, choose This computer, or leave the bot on Auto (see below).
Set it up on Ubuntu
Ubuntu's default session is Wayland, and Murage won't control a Wayland desktop.
- Sign out. On the sign-in screen, choose Ubuntu on Xorg, then sign in again.
- 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.
- When the card says Ready, choose This computer under Runs on for the bot you want.
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 run anything without asking, except reading your keys and passwords.
Each warning ends "Continue only if you are watching." Choose OK or Cancel.
Watch and stop
- 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.
- 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.
Troubleshooting
- "No frames yet; the preview needs Screen Recording permission. After granting, relaunch the app." Grant Screen Recording, then quit and reopen Murage.
- "Unavailable on Wayland" or "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.
- "Enable the local control beta and complete the Cua Driver checks first." Choose Enable local control (Beta), then Try again if the card says Needs attention.
- "CUA Driver is not ready for local computer control." On a Mac, check both permissions and choose Retry.
- "Local computer control requires the desktop app." You're in Murage through a browser. Use the desktop app on the computer itself.
- "The selected provider cannot request approvals for local computer actions." Switch the bot to an engine that can, such as Claude or an ACP engine.