← Back to Skills Marketplace
frisky1985

Browser Hosting

by Stefan Ming · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
43
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install browser-hosting
Description
OpenClaw browser hosting and automation capabilities for web interaction, scraping, and UI testing. Provides isolated browser profiles, snapshot-based automa...
README (SKILL.md)

Browser Hosting Skill

This skill provides comprehensive browser automation capabilities through OpenClaw's managed browser system. It enables safe, isolated web interaction with deterministic UI control.

When to Use This Skill

  • Web scraping - Extract structured data from websites
  • UI automation - Automate form filling, clicks, navigation
  • Web testing - Verify page behavior and functionality
  • Content extraction - Get text, screenshots, or PDFs from web pages
  • Browser isolation - Perform web operations without affecting personal browsing
  • Remote browser control - Control browsers on other machines via nodes

Quick Start

Basic Workflow

# 1. Open a page
openclaw browser --browser-profile openclaw open https://example.com

# 2. Take a snapshot to see interactive elements
openclaw browser --browser-profile openclaw snapshot --interactive

# 3. Perform actions using references from snapshot
openclaw browser --browser-profile openclaw click e12
openclaw browser --browser-profile openclaw type i23 "search term" --submit

Profile Selection

  • openclaw: Isolated managed browser (recommended for automation)
  • chrome: Chrome extension relay (for controlling existing Chrome tabs)

Core Capabilities

Browser Profiles

  • Isolated instances: Each profile has separate user data directory
  • Multiple profiles: Run openclaw, work, remote simultaneously
  • Remote CDP: Connect to browsers on other machines
  • Browserless integration: Use hosted Chromium services

Snapshot System

Two approaches for reliable UI interaction:

  1. AI Snapshots (--format ai): Numeric references like [1], [2]

    • Best for simple, one-off interactions
    • Uses Playwright's aria-ref internally
  2. Role Snapshots (--interactive): Semantic references like [ref=e12]

    • Recommended for automation - more stable and descriptive
    • Role-based naming: e=button, b=link, i=input, s=select
    • Supports iframe scoping with --frame

Automation Actions

  • Navigation: open, navigate, close
  • Interaction: click, type, press, hover, drag, select
  • Input: fill (structured form data), file upload
  • Waiting: Intelligent waits for elements, URLs, network idle, JS conditions
  • Debugging: highlight, trace, errors, requests

Content Extraction

  • Text: Structured snapshots with references
  • Screenshots: Full page or element-specific
  • PDF: Generate PDFs from web pages
  • Network: Monitor API calls and responses

Configuration

Browser settings are managed in ~/.openclaw/openclaw.json. Key options:

{
  "browser": {
    "enabled": true,
    "defaultProfile": "openclaw",
    "profiles": {
      "openclaw": { "cdpPort": 18800 },
      "work": { "cdpPort": 18801 },
      "remote": { "cdpUrl": "http://10.0.0.42:9222" }
    }
  }
}

See configuration.md for complete configuration guide.

Usage Patterns

Simple Web Scraping

# Get page content
openclaw browser --browser-profile openclaw open https://news-site.com
openclaw browser --browser-profile openclaw snapshot --interactive --compact

Form Automation

# Fill out a form
openclaw browser --browser-profile openclaw open https://form-site.com
openclaw browser --browser-profile openclaw snapshot --interactive
openclaw browser --browser-profile openclaw type i1 "John Doe"
openclaw browser --browser-profile openclaw type i2 "[email protected]" 
openclaw browser --browser-profile openclaw click e5  # Submit button

Multi-step Workflows

# Navigate through multiple pages
openclaw browser --browser-profile openclaw open https://shop.com
openclaw browser --browser-profile openclaw wait --load networkidle
openclaw browser --browser-profile openclaw snapshot --interactive
openclaw browser --browser-profile openclaw click b12  # Product link
openclaw browser --browser-profile openclaw wait --load networkidle
openclaw browser --browser-profile openclaw click e8   # Add to cart

Advanced Features

Remote Browser Control

Connect to browsers on other machines:

"profiles": {
  "remote-workstation": {
    "cdpUrl": "http://192.168.1.100:9222",
    "color": "#00AA00"
  }
}

Browserless Integration

Use hosted Chromium:

"profiles": {
  "browserless": {
    "cdpUrl": "https://production-sfo.browserless.io?token=YOUR_TOKEN",
    "color": "#00AA00"
  }
}

Node Proxy

Automatic routing to nodes with browser capability:

  • No extra config needed if node has browser
  • Gateway automatically proxies browser commands
  • Use target="node" to force specific node

Security & Isolation

  • Complete isolation: Managed browsers never access personal profiles
  • Loopback only: Browser control restricted to localhost
  • Authentication required: All access requires Gateway auth
  • No persistent sessions: Clean state between runs (unless configured otherwise)
  • JavaScript execution: Can be disabled via browser.evaluateEnabled=false

Troubleshooting

Common Issues

  • References not working: Always snapshot after navigation - refs change
  • Element not found: Use --interactive snapshots for better reliability
  • Browser won't start: Check executablePath and permissions
  • Playwright errors: Install full Playwright package, not just core

Debugging Workflow

  1. snapshot --interactive to get current state
  2. highlight \x3Cref> to verify target location
  3. errors --clear to check JavaScript errors
  4. requests --filter api --clear to monitor network
  5. trace start → reproduce issue → trace stop for deep debugging

Bundled Resources

Scripts

References

Assets

Best Practices

  1. Always use role snapshots (--interactive) for automation
  2. Snapshot before every action - references aren't stable across navigation
  3. Use wait conditions before snapshotting dynamic content
  4. Prefer isolated profiles over extension relay for automation
  5. Validate executable paths on new systems
  6. Use environment variables for sensitive configuration (tokens, passwords)

This skill transforms OpenClaw into a powerful web automation platform while maintaining security and reliability through its snapshot-based, reference-driven approach.

Usage Guidance
Install only if you are comfortable giving the agent browser-control authority. Prefer the isolated openclaw profile, avoid using the chrome profile unless you intentionally want the agent to access your live logged-in browser session, and use remote CDP or Browserless only with trusted endpoints, TLS, short-lived tokens, and redacted logs/configuration.
Capability Tags
requires-sensitive-credentials
Capability Assessment
Purpose & Capability
The core browser automation, scraping, screenshots, PDFs, network inspection, and UI testing capabilities match the stated purpose, but the artifacts also include unrelated skill initialization and packaging scripts that are not clearly described as part of the browser-hosting purpose.
Instruction Scope
The instructions disclose remote CDP, Browserless, and Chrome extension relay modes, but the main security wording still claims complete isolation and localhost-only control, which does not apply to those modes.
Install Mechanism
No malicious install behavior was found; VirusTotal and static scan are clean. The package includes executable helper scripts, including packaging and initialization helpers, but they require explicit invocation.
Credentials
Browser automation is proportionate for this skill, but controlling an existing Chrome profile or remote browser can expose cookies, authenticated pages, page contents, screenshots, PDFs, and API traffic beyond the isolated managed-browser model.
Persistence & Privilege
The skill writes browser configuration under ~/.openclaw/openclaw.json and supports credential-bearing remote CDP URLs; persistence is expected for configuration, but the documentation does not sufficiently warn about storing or leaking secrets in URLs and config files.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install browser-hosting
  3. After installation, invoke the skill by name or use /browser-hosting
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release providing OpenClaw browser hosting and comprehensive web automation capabilities - Supports isolated browser profiles for safe, deterministic UI control and content extraction - Includes snapshot-based automation using both AI and semantic (role-based) references - Enables remote browser control, browserless.io integration, and node routing for distributed automation - Offers automation actions, advanced content extraction (text, screenshots, PDF), and robust configuration options - Emphasizes browser isolation, security, and best practices for reliable web interaction
Metadata
Slug browser-hosting
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Browser Hosting?

OpenClaw browser hosting and automation capabilities for web interaction, scraping, and UI testing. Provides isolated browser profiles, snapshot-based automa... It is an AI Agent Skill for Claude Code / OpenClaw, with 43 downloads so far.

How do I install Browser Hosting?

Run "/install browser-hosting" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Browser Hosting free?

Yes, Browser Hosting is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Browser Hosting support?

Browser Hosting is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Browser Hosting?

It is built and maintained by Stefan Ming (@frisky1985); the current version is v1.0.0.

💬 Comments