Looks logged out
Wrong profile
The task likely needed `user` instead of isolated `openclaw`.
Wrong repeatability model
The task likely needed managed `openclaw` instead of `user`.
OpenClaw browser
Session, profile, and login-state troubleshooting
Use this page when the browser opens successfully but the page behaves like the wrong session is being used.
Core idea
A logged-out-looking page often means wrong browser context, not broken browser control.
First split
If the page opens, ask the session question first
A healthy browser can still show the wrong behavior because the workflow used the wrong browser profile or inherited the wrong state expectations.
Typical fixes
The safest recovery moves are usually small
- switch from isolated `openclaw` to `user` when real signed-in state matters
- switch from `user` to managed `openclaw` when repeatability matters more than inherited state
- inspect cookies and storage before clearing them
- treat profile switching as a normal correction, not a hack
Common symptom map
What these failures usually mean
State leaks between runs
Behavior is wrong but structure is fine
Stored state issue
Inspect cookies and storage before escalating.
Next route
Useful follow-on pages
State inspection
State, cookies, storage, and emulation
Inspect what the browser actually inherited.
Broader recovery
Browser troubleshooting
Use the wider browser repair map if the issue is not purely session-state.