Docs
CLI reference
`moltbot browser`

`moltbot browser`

Scope

Use this page when:

  • You use moltbot browser and want examples for common tasks
  • You want to control a remote browser via browser.controlUrl
  • You want to use the Chrome extension relay (attach/detach via toolbar button)

Manage Moltbot’s browser control server and run browser actions (tabs, snapshots, screenshots, navigation, clicks, typing).

Related:

Common flags

  • --url <controlUrl>: override browser.controlUrl for this command invocation.
  • --browser-profile <name>: choose a browser profile (default comes from config).
  • --json: machine-readable output (where supported).

Quick start (local) 

moltbot browser --browser-profile chrome tabs
moltbot browser --browser-profile clawd start
moltbot browser --browser-profile clawd open https://example.com
moltbot browser --browser-profile clawd snapshot

Profiles

Profiles are named browser routing configs. In practice:

  • clawd: launches/attaches to a dedicated Moltbot-managed Chrome instance (isolated user data dir).
  • chrome: controls your existing Chrome tab(s) via the Chrome extension relay.
moltbot browser profiles
moltbot browser create-profile --name work --color "#FF5A36"
moltbot browser delete-profile --name work

Use a specific profile:

moltbot browser --browser-profile work tabs

Tabs 

moltbot browser tabs
moltbot browser open https://docs.clawd.bot
moltbot browser focus <targetId>
moltbot browser close <targetId>

Snapshot / screenshot / actions

Snapshot:

moltbot browser snapshot

Screenshot:

moltbot browser screenshot

Navigate/click/type (ref-based UI automation):

moltbot browser navigate https://example.com
moltbot browser click <ref>
moltbot browser type <ref> "hello"

Chrome extension relay (attach via toolbar button)

This mode lets the agent control an existing Chrome tab that you attach manually (it does not auto-attach).

Install the unpacked extension to a stable path:

moltbot browser extension install
moltbot browser extension path

Then Chrome → chrome://extensions → enable “Developer mode” → “Load unpacked” → select the printed folder.

Full guide: Chrome extension

Remote browser control (moltbot browser serve)

If the Gateway runs on a different machine than the browser, run a standalone browser control server on the machine that runs Chrome:

moltbot browser serve --bind 127.0.0.1 --port 18791 --token <token>

Then point the Gateway at it using browser.controlUrl + browser.controlToken (or MOLTBOT_BROWSER_CONTROL_TOKEN).

Security + TLS best-practices: Browser tool, Tailscale, Security

`moltbot approvals``moltbot channels`