Skip to main content
OpenClaw can run a dedicated Chrome/Brave/Edge/Chromium profile that the agent controls. It runs through a small local control service inside the Gateway (loopback only) and is isolated from your personal browser.
  • Think of it as a separate, agent-only browser. The openclaw profile never touches your personal browser profile.
  • The agent opens tabs, reads pages, clicks, and types in this isolated lane.
  • The built-in user profile attaches to your real signed-in Chrome session instead, via Chrome DevTools MCP.
This page is an index. The browser documentation is split across nine pages, one per reader job. Open the page that matches your task.

​
What you get

  • A separate browser profile named openclaw (orange accent by default).
  • Deterministic tab control (list/open/focus/close).
  • Agent actions (click/type/drag/select), snapshots, screenshots, PDFs.
  • Question answering over readable page text without returning a full snapshot.
  • Playwright-backed profiles save direct attachment navigations under the managed downloads directory and return { url, suggestedFilename, path } metadata after final-URL policy validation.
  • Playwright-backed agent actions return a downloads array with the same managed metadata when the action immediately starts one or more downloads.
  • A bundled browser-automation skill that teaches agents the snapshot, stable-tab, stale-ref, and manual-blocker recovery loop when the browser plugin is enabled.
  • Optional multi-profile support (openclaw, work, remote, …).
This browser is not your daily driver. It is a safe, isolated surface for agent automation and verification. On macOS, you can explicitly copy cookies from a Chrome-family system profile into a separate managed profile. The managed browser still uses its own user data directory. Only the selected cookies are copied, and local storage and IndexedDB stay behind. See Profiles or the openclaw browser CLI reference for import commands and limitations.

​
Where each section moved

Every section heading from the previous single-page version keeps its anchor here, so an existing link such as /tools/browser#custom-chrome-mcp-launch still resolves. Each entry points at the page that now holds the content.
  • Tools Overview - all available agent tools
  • Sandboxing - browser control in sandboxed environments
  • Security - browser control risks and hardening
  • Web fetch - retrieve a page without driving a browser
  • Diffs - read-only diff viewer and file renderer for agents
  • Browser login - signing a profile into a site before automating it