← Back to Browser
OpenClaw browser

Browser profiles explained

Use this page when the browser task depends on isolation, real login state, or an external browser endpoint.

Core idea Many browser problems are really wrong-profile problems.
Profile model

A profile is the route OpenClaw uses to control a browser

In OpenClaw, a browser profile decides what browser context exists, what state is available there, and whether OpenClaw owns the browser process or only attaches to it.

Main routes

Choose the right browser model first

Default route

Managed `openclaw`

Best for clean, repeatable, stateless automation.

Login-sensitive route

Existing-session `user`

Best when real signed-in browser state matters.

Advanced route

Remote CDP

Best when the external endpoint is an intentional infrastructure choice.

Fast corrections

The wrong profile creates convincing fake bugs

  • page opens but looks logged out: move from isolated `openclaw` to `user` if real session state is required
  • task should be repeatable but state leaks between runs: move from `user` to managed `openclaw`
  • lifecycle behavior feels odd: check whether the route is remote or attach-only
Next route

Where to go next