# Browser Troubleshooting Documentation

## Overview

This documentation addresses Chrome DevTools Protocol (CDP) launch failures on Linux systems, particularly Ubuntu, where snap-packaged Chromium creates AppArmor confinement issues preventing OpenClaw from properly spawning browser processes.

## Key Problem

The default Ubuntu Chromium installation is a snap wrapper rather than a native binary. As the docs note, `apt install chromium` provides a stub package that redirects to snap rather than an actual browser executable.

## Recommended Solutions

**Primary approach:** Install the official Google Chrome `.deb` package from Google's repositories, which bypasses snap sandboxing entirely. Configuration requires setting the `executablePath` to `/usr/bin/google-chrome-stable` in `~/.openclaw/openclaw.json`.

**Alternative approach:** Configure OpenClaw's `attachOnly` mode to connect to a manually-launched Chromium instance running on port 18800, bypassing automatic browser startup. A systemd user service can automate this manual launch process.

## Configuration Reference

The documentation provides a configuration table with four key browser options:
- `browser.enabled` (default: true)
- `browser.executablePath` (auto-detected)
- `browser.headless` (default: false)
- `browser.noSandbox` (default: false)

## Verification

Users can verify functionality via curl commands checking the browser status endpoint and testing tab functionality at `http://127.0.0.1:18791/`.
