#How do i setup my browser
1 messages ยท Page 1 of 1 (latest)
Hey! ๐ To set up browser control in Clawdbot, check out the browser docs:
๐ https://docs.clawd.bot/providers/browser
The basics:
- Chrome extension relay (recommended) - lets Clawdbot control your existing Chrome with the browser extension
- Clawd-managed browser - isolated browser instance
Make sure you have the Chrome extension installed and click the Clawdbot Browser Relay toolbar icon on any tab you want to control.
Let me know if you run into any issues! ๐ฆ
๐ฆ Clawdbot 2026.1.16-2 (49c35c7) โ I'll do the boring stuff while you dramatically stare at the logs like it's cinema.
profile: chrome
enabled: true
running: false
controlUrl: http://127.0.0.1:18791
cdpPort: 18792
cdpUrl: http://127.0.0.1:18792
browser: unknown
detectedBrowser: chrome
detectedPath: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
profileColor: #00AA00
Does this mean it hsould be working
The key issue: running: false โ
The detection worked โ (found your Chrome at /Applications/Google Chrome.app), but the browser control isn't actually connected yet.
To get it running:
- Install the Clawdbot browser extension in Chrome (check the docs for the link)
- Open any tab you want Clawdbot to control
- Click the Clawdbot Browser Relay toolbar icon โ the badge should turn ON
- Run
clawdbot browser statusagain โ it should showrunning: true
The extension relay connects an existing Chrome tab to Clawdbot. Without that tab connection, it stays "not running" even though Chrome is detected.
Let me know once you've attached a tab! ๐ฆ
can i do it without the relay?
Yep! You can use the clawd-managed browser instead of the Chrome extension relay.
To use a standalone browser:
- Set
browser.profile: "clawd"in your config (instead of "chrome") - Clawdbot will launch its own Chrome instance with remote debugging
- No extension or tab attachment needed
Quick test:
clawdbot browser start --profile clawd
clawdbot browser status
The clawd-managed browser runs in a sandboxed mode - useful when you don't want to attach to your existing Chrome session.
Docs: https://docs.clawd.bot/providers/browser#profiles ๐ฆ
i setup the relay and its on and it shows the tab that its debugging but the clawdbot browser status still says:
๐ฆ Clawdbot 2026.1.16-2 (49c35c7) โ I don't judge, but your missing API keys are absolutely judging you.
profile: chrome
enabled: true
running: true
controlUrl: http://127.0.0.1:18791
cdpPort: 18792
cdpUrl: http://127.0.0.1:18792
browser: unknown
detectedBrowser: chrome
detectedPath: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
profileColor: #00AA00
It's working now! ๐
Look at the difference:
- Before:
running: false - Now:
running: trueโ
The browser: unknown is normal for the relay profile โ you're not launching a specific browser, you're attaching to an existing tab via the extension. The important part is running: true.
Try a test command:
clawdbot browser open https://google.com
If it opens Google in your connected Chrome tab, you're all set! ๐ฆ
how would i set it up without the tab so it can open chrome on its own
Switch to the clawd-managed browser profile:
- Edit your config (
~/.clawdbot/clawdbot.json):
{
"browser": {
"profile": "clawd"
}
}
- Restart browser:
clawdbot browser stop
clawdbot browser start
Now Clawdbot will launch its own Chrome instance with remote debugging enabled. No tab attachment needed โ it spawns a fresh browser window automatically.
Note: This runs a separate Chrome profile from your main one, so it won't share cookies/history. The relay approach (profile: "chrome") is better if you want to use your existing tabs + sessions. ๐ฆ
how do i unsinstall the extension
To uninstall the Clawdbot Browser Relay extension:
- Open Chrome โ Go to
chrome://extensions/ - Find Clawdbot Browser Relay in the list
- Click Remove (or the trash icon ๐๏ธ)
Or if you prefer the menu path: Chrome Menu โ Settings โ Extensions โ Clawdbot Browser Relay โ Remove
Once removed, switch your config to profile: "clawd" as I mentioned before, and restart the browser. ๐ฆ
gursh@Gurshans-Mac-mini ~ % clawdbot browser start
๐ฆ Clawdbot 2026.1.16-2 (49c35c7) โ I speak fluent bash, mild sarcasm, and aggressive tab-completion energy.
Error: 500: {"error":"Error: Chrome extension relay is running, but no tab is connected. Click the Clawdbot Chrome extension icon on a tab to attach it (profile "chrome")."}
The extension is still installed, so Clawdbot thinks you want to use it.
Two options:
Option 1: Uninstall the extension first (recommended)
- Go to
chrome://extensions/and remove the Clawdbot extension - Then run
clawdbot browser startโ it will auto-switch to clawd-managed browser
Option 2: Force clawd profile
clawdbot browser start --profile clawd
Or add it permanently to your config:
{
"browser": {
"profile": "clawd"
}
}
Then clawdbot gateway call config.apply to reload.
Pick whichever feels easier! ๐ฆ
the profile doesnt even show in the brwoser tho
Uninstall the extension first, then run:
clawdbot browser start --profile clawd
Without uninstalling, Clawdbot keeps trying to use the extension. Once the extension is gone, it will spawn its own Chrome window. ๐ฆ
but i cant uninstall it cause the profile clawd doesnt show in my chrome
The extension and Chrome profiles are different things.
Extension uninstall is done in Chrome's extensions page:
- Open Chrome
- Go to
chrome://extensions/in the URL bar - Find "Clawdbot Browser Relay" โ click Remove
Chrome profiles (like "clawd" or "chrome") are the separate user accounts in Chrome โ unrelated to the extension.
Uninstalling the extension doesn't affect your Chrome profiles at all. Just go to chrome://extensions/ and remove it. ๐ฆ
its not there!
The error message says the relay is "running" โ maybe the config is set to use it.
Check your config:
clawdbot config get browser
If it shows "profile": "chrome", change it to "clawd":
clawdbot config set browser.profile clawd
clawdbot browser stop
clawdbot browser start
Or just force it this time:
clawdbot browser start --profile clawd
Let me know what the config shows! ๐ฆ
how do i restart the gateway
To restart the gateway:
clawdbot gateway restart
Or if you need to reload config only (hot reload):
clawdbot gateway call config.apply
Once restarted, try:
clawdbot browser start --profile clawd
๐ But wait โ if the extension isn't installed, something else is wrong. After restarting, run:
clawdbot config get browser
And share what it shows. ๐ฆ
gursh@Gurshans-Mac-mini ~ % clawdbot gateway restart
error: too many arguments for 'gateway'. Expected 0 arguments but got 1.