← Back to Channels and integrationsOpenClaw browser
Browser profiles explained
Choose the browser profile based on repeatability and login state, not habit. Most weird browser behavior is a profile-choice problem before it is an action problem.
Profile ruleUse managed openclaw for repeatable clean automation, user for real signed-in state, and remote CDP only when it is intentional infrastructure.
Profile choice
Which profile should you use?
Managed openclawBest for clean, repeatable automation where state carryover would be a bug.
Existing-session userBest when the task depends on real signed-in browser state.
Remote CDPBest only when the external endpoint is an intentional advanced setup, not a default shortcut.
Examples
Examples of correct profile decisions
Public site QAUse managed openclaw so repeatability is high and stale state does not leak in.
Search Console or logged-in admin taskUse the user profile if the real signed-in state is the whole point of the task.
Remote hosted browser farmUse remote CDP only if you deliberately built that architecture.
Open deeper reference links for this page