Skill

Win11 Visible Browser

Control, diagnose, or repair a visible Windows 11 Edge/Chrome browser from OpenClaw running in WSL2 via CDP. Use when browser automation should share the use...

Verified: 2026-05-15 (clawhub-ingest-2026-05-15+enrich-capability-skill)

When to use Win11 Visible Browser

Choose if

You're running OpenClaw inside WSL2 and need to drive the user's real visible Edge or Chrome on Windows 11 — keeping their cookies, logged-in accounts, extensions, and 2FA prompts intact. Picks over headless Playwright when sites detect or block headless, when human approval is required for sensitive actions, or when visual step-by-step verification matters.

Avoid if

You don't actually need a shared user session — prefer cheaper paths first (local CLI, public APIs, web_fetch on public pages, evaluate on already-open tabs). Also avoid for unattended high-throughput scraping: the README caps memory, target counts, and tab parallelism, and mandates human confirmation before state-changing actions.

Risk Flags

  • MEDIUM security README explicitly forbids using the skill to bypass site protections, automate prohibited activity, or hide automation from the user. CDP firewall rules must be restricted to WSL/Hyper-V CIDR — never exposed to LAN or Internet.
  • MEDIUM scope Resource budget caps documented — keep ≥1 GB free system memory, stop if targets exceed 30 or pages exceed 10, avoid opening many tabs in parallel. Not for high-throughput scraping.
  • LOW scope Requires human-in-the-loop confirmation before any state-changing action (form submissions, account changes, firewall modifications, Scheduled Tasks) per README safety section. Unsuitable for fully unattended runs.

Cost

Type: Unknown

Dependencies

Minimum runtime: openclaw, curl, and ip binaries on the WSL2 host (README "Dependencies" section)

Distribution

ClawHub
win11-visible-browser
License
MIT-0