Startup
Launch health
The browser itself is not reaching a healthy control state.
Reachability
Browser control is healthy, but the target page cannot be opened cleanly.
OpenClaw browser
Browser troubleshooting
Use this page when browser automation is failing and you need to classify the problem before you reach for the wrong fix.
Core idea
The fastest browser recovery usually starts by classifying the failure, not by trying another random command.
Failure split
Do not debug every browser problem the same way
Navigation
Session
Wrong context
The page opens, but it is the wrong browser context for the task.
Interaction
Page-level uncertainty
The page is open, but the next step is unclear or brittle.
Inspection ladder
Use the lightest tool that answers the question
- snapshot for interactive structure
- labeled screenshot for visible state plus refs
- console and network inspection for behind-the-UI behavior
- trace capture only after simpler lanes fail to explain the issue
Config reality
Some browser failures are really config failures
Preview access, executable path, attach-only behavior, hostname allow rules, and lifecycle drift can all be rooted in browser config rather than the page itself.
Next route
Jump into the right repair lane
Login-state issues
Session, profile, and login-state troubleshooting
Separate auth-looking failures from browser-health failures.
Preview/routing issues
Local preview, remote routing, and node-host control
Fix reachability and machine-topology assumptions.