Name: Agent Browser Core
Author: codedao12

What breaks without openclaw agent browser core

Conflicting browser instances. Memory spikes. Brittle skill-to-skill browser sharing.

→

Shared stable headless browser runtime × 155-star foundation skill ÷ 10–20 minutes ÷ no duplicate Chromium overhead = browser automation that scales cleanly.

openclaw agent browser core — what it actually does

Provides a shared headless browser runtime for all browser-automation skills.

Supports concurrent sessions with configurable BROWSER_POOL_SIZE.

Acts as an importable dependency for building custom browser skills.

Requires Playwright and 512MB RAM per instance for reliable operation.

Security check — openclaw agent browser core

Privacy score: 7/10 — accesses connected platform APIs only. Lock it: review OAuth scopes before install, confirm macOS, Linux; OpenClaw ≥1.0; Playwright; 512MB RAM per instance compatibility.

Quick start — openclaw agent browser core in 10–20 minutes

Setup time: 10–20 minutes

You need:

OpenClaw core
Chromium
Playwright

Install the package:

# Install via ClawhHub
clawhub install codedao12/agent-browser-core

Install Playwright: npx playwright install chromium

Install the skill

Set BROWSER_POOL_SIZE=2 in .env for concurrent sessions

Use as a dependency in your own skill with import agent-browser-core

Troubleshooting openclaw agent browser core

1. Requires 512MB+ RAM per browser instance — monitor memory on constrained servers

2. Update Chromium separately from the skill for security patches

Compatibility & status

Works with: macOS, Linux; OpenClaw ≥1.0; Playwright; 512MB RAM per instance intermediate Last updated: Nov 2025 ★ 155 on GitHub MIT

Official docs →

View on GitHub →

Related — more like openclaw agent browser core

More by codedao12

Facebook

Integrations

Stack more browser skills without the core and watch memory crash. Install the foundation now before adding any automation skills.

Get it on GitHub →