OpenClaw Browser Not Working

First determine whether the browser plugin, CLI, profile, browser process, or individual page action is failing.

Run browser diagnostics

openclaw browser --browser-profile openclaw doctor
openclaw browser --browser-profile openclaw doctor --deep
openclaw browser --browser-profile openclaw status

If the command is unknown, inspect plugin installation and plugins.allow. If the CLI works but the agent lacks the tool, inspect tools.profile and agent-specific rules.

Check launch conditions

Confirm that a supported Chromium-family binary exists. On Linux without DISPLAY or WAYLAND_DISPLAY, use the documented headless behavior instead of forcing a headed browser. For remote CDP, verify that both the HTTP discovery URL and advertised WebSocket address are reachable from the Gateway.

For an existing-session profile, approve the local attach prompt or ensure the extension relay is connected. Do not expect the isolated openclaw profile to contain personal logins.

Refresh page references

After navigation or a major DOM change, take a new snapshot. Element references from the previous document can become stale. Retry once with a fresh snapshot instead of repeatedly clicking the old reference.

Expected result

• Doctor finds the intended profile and browser backend.
• Status reports a reachable browser.
• A test URL opens and snapshots successfully.
• Fresh references work after navigation.
• The browser tool remains restricted to intended agents.