Use my Chrome
Let one trusted bot work inside your own signed-in Google Chrome, in a tab of its own.
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 carries less risk. It keeps the bot's logins apart from yours.
What you need
- The built-in browser switched on in SettingsDevicesBuilt-in browser (it is on by default), 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
Step 1
Turn on remote debugging in Chrome
In Chrome, open chrome://inspect/#remote-debugging and turn on remote debugging. Keep Chrome open.
You're done when: remote debugging is on and Chrome is still open.
Step 2
Open the bot's Browser tab
In Murage, open the bot's chat, choose Bot's computer at the top, and open the Browser tab.
You're done when: you see the Profile menu under the page.
Step 3
Choose Use my Chrome
In the Profile menu, choose Use my Chrome.
You're done when: Murage shows its explanation card.
Step 4
Confirm in Murage
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.
You're done when: you chose Use my Chrome on the card.
Step 5
Allow it in Chrome
The first time the bot connects, Chrome asks you to allow the connection. Choose Allow in Chrome.
You're done when: the panel 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
You see
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.Do this
Remote debugging is off or Chrome is closed. Turn it on and keep Chrome running.
You see
Your Chrome isn't reachable, so this turn ran without a browser.Do this
The bot carried on without a browser for that turn. Open Chrome, turn on remote debugging, and send the next message.
You see
name is already using your Chrome. Only one bot can use it at a time; switch name back to its own browser first.Do this
Move the other bot to its own profile, then try again.
You see
stop this bot's turn before changing its browserDo this
Also shown as "Return browser control before changing browsers". Stop the turn, or hand control back, then change it.
You see
Chrome never asks to allow the connectionDo this
Check you're using Google Chrome 144 or later, and that you turned on remote debugging in the same Chrome you use every day.