browser-setup
Install and configure headless Chrome for OpenClaw browser tool in environments without root/sudo access (cloud containers, VPS, sandboxed hosts). Use when: (1) browser tool fails with No supported browser found, (2) Chrome crashes with Page crashed or missing library errors, (3) setting up browser automation on a fresh server or container, (4) user asks to install or fix the browser for OpenClaw. NOT for macOS/Windows desktops with Chrome already installed, or Chrome extension relay setup.
Why use this skill?
Easily install and configure headless Chrome for OpenClaw on cloud containers, VPS, and Linux servers without root access using this browser-setup skill.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/huangdawei/browser-setupWhat This Skill Does
The browser-setup skill provides a robust, user-space mechanism for installing and configuring headless Google Chrome in environments where root access is restricted, such as cloud containers, VPS, or sandboxed Linux hosts. By automating the download, extraction, and wrapper creation for Chrome and its required shared libraries, this skill bridges the gap between OpenClaw's automation capabilities and restrictive hosting environments. It creates a localized, executable environment that avoids common library dependency errors and permission conflicts that plague standard installation methods in non-interactive server environments.
Installation
To install, run the designated setup script within your environment:
bash scripts/install-browser.sh
This script handles the heavy lifting by installing necessary Liberation fonts and the required ~40 shared libraries. Once installed, integrate it into your OpenClaw environment by setting the browser.executablePath to $HOME/local-libs/chrome-wrapper.sh and ensuring browser.noSandbox and browser.attachOnly are set to true in your configuration files.
Use Cases
This skill is specifically designed for:
- Cloud-based automation: Running browser-dependent agents on AWS, GCP, or Azure containers where root permissions are unavailable.
- Troubleshooting: Resolving "No supported browser found" errors that frequently occur when the host environment lacks the specific dependencies needed for modern Chrome versions.
- Stability: Fixing "Page crashed" issues caused by missing Linux shared libraries or memory management conflicts common in bare-bones container images.
- Sandbox environments: Facilitating web interaction in isolated environments where system-wide software installation is disallowed or impossible.
Example Prompts
- "OpenClaw, my browser tool is failing with a 'No supported browser found' error. Can you set up the browser-setup skill for me?"
- "I am running OpenClaw on a VPS and the browser keeps crashing with page load errors. Please help me configure the headless Chrome wrapper."
- "Can you optimize my browser configuration for a headless environment using the browser-setup skill to ensure I don't run into port conflicts?"
Tips & Limitations
Always set attachOnly to true. When using a wrapper script, attempting to let OpenClaw manage the process lifecycle manually often leads to PortInUseError because Playwright may attempt to re-initialize a process that is already actively listening on the CDP port. Treat this as a manual-start-first system: launch your wrapper in the background first, then trigger the OpenClaw browser tool. If you encounter shared library issues after a system update, check the libXXX.so logs to determine which specific dependencies need refreshing in your local-libs directory.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-huangdawei-browser-setup": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read, code-execution