Use my Chrome
Let one trusted bot work inside your own signed-in Google Chrome, in a tab of its own.
Use my Chrome connects one bot to the Google Chrome you already use, signed in as you. The bot works in a tab of its own, but it acts as you on every site you're signed in to, and it can see your open tabs.
It's a choice in the built-in browser's Profile menu, so it needs the built-in browser switched on first. That means it's experimental and works on Mac and Linux.
When to use it
Use it for one bot you trust, when the work needs your real logins and setting up a separate profile isn't practical. For example, a bot that works in a web app where you're already signed in with two-factor authentication.
For everything else, a bot's own private profile is safer. It keeps the bot's logins apart from yours.
What you need
- The built-in browser switched on in Settings → Experimental, and the bot's own Browser switch on under Access in its settings.
- Google Chrome 144 or later, open and running.
- Remote debugging switched on in Chrome (step 1 below). Chrome doesn't restart and your windows stay open.
Only one bot can use your Chrome at a time.
Set it up
- In Chrome, open
chrome://inspect/#remote-debuggingand turn on remote debugging. Keep Chrome open. - In Murage, open the bot's chat, choose Bot's computer at the top, and open the Browser tab.
- In the Profile menu, choose Use my Chrome.
- Murage explains what this means: the bot "will act inside your own Chrome, signed in as you, and can see your open tabs." Choose Use my Chrome to confirm, or Cancel.
- The first time the bot connects, Chrome asks you to allow the connection. Choose Allow in Chrome.
The panel then says "Using your Chrome, signed in as you." You can watch and take over the bot's tab the same way as any built-in browser tab.
The connection stays on your own computer. Murage only connects to Chrome on this machine.
Switch it off
In the bot's Profile menu, choose name's own, a named profile, or Guest. Murage disconnects from your Chrome. You can also turn off remote debugging in Chrome.
You can't switch while the bot is mid-turn or while you hold control of its browser. Stop the turn or choose Return to bot first.
Troubleshooting
- "Your Chrome is not ready for this bot yet. Open chrome://inspect/#remote-debugging in Google Chrome and turn on remote debugging, keep Chrome open, then try again. Chrome will ask you to allow the connection." Remote debugging is off or Chrome is closed. Turn it on and keep Chrome running.
- "Your Chrome isn't reachable, so this turn ran without a browser." The bot carried on without a browser for that turn. Open Chrome, turn on remote debugging, and send the next message.
- "name is already using your Chrome. Only one bot can use it at a time; switch name back to its own browser first." Move the other bot to its own profile, then try again.
- "stop this bot's turn before changing its browser" or "Return browser control before changing browsers". Stop the turn, or hand control back, then change it.
- Chrome never asks to allow the connection. Check you're using Google Chrome 144 or later, and that you turned on remote debugging in the same Chrome you use every day.