Is the installation permanent?

The installation and patches are session-local. If the Claude.ai container resets, you will need to re-run the setup and patching steps.

Why do I need this skill for webctl in Claude.ai?

Claude.ai containers use an authenticated proxy that Chromium cannot natively handle for HTTPS tunnels. This skill provides a patch and a local proxy to fix connection failures.

Does this support all websites?

Access is restricted to the domains allowed in your Claude.ai environment's network configuration. Check your system prompt for the specific allow-list.

How do I fix ERR_TUNNEL_CONNECTION_FAILED?

Ensure the auth_proxy.py is deployed to the webctl daemon directory and the session_manager.py is patched as described in the setup procedure.

What is the primary command for this skill?

The skill uses the 'webctl' CLI, allowing you to start browser sessions, navigate to URLs, and interact with page elements via the command line.

Webctl Browser Automation

Name: Webctl Browser Automation
Author: oaustegard

byoaustegard

•

119

•

Browser Automation

Enables reliable browser automation and web scraping in Claude.ai containers by handling authenticated proxy connections.

The Webctl Browser Automation skill provides a robust solution for running Playwright-based browser tasks within Claude.ai's egress-controlled environments. It solves the common 'ERR_TUNNEL_CONNECTION_FAILED' error by implementing a local forwarding proxy that manages JWT-based proxy authentication for Chromium. This allows developers to navigate HTTPS websites, interact with web elements, and capture DOM snapshots or screenshots directly from the CLI, streamlining workflows for data collection, automated testing, and web analysis.

Key Features

01Robust element interaction using ARIA roles and partial name matching

02Headless session management with status and error tracking

03119 GitHub stars

04High-level CLI for Playwright browser control and navigation

05Intelligent DOM snapshotting with interactive-only element filtering

06Automatic handling of authenticated egress proxies for HTTPS traffic

Use Cases

01Web scraping and data extraction from sites requiring authenticated proxy tunnels

02Capturing structured DOM snapshots for LLM context optimization

03Automated UI testing and verification of web applications in-container

Key Features

01Robust element interaction using ARIA roles and partial name matching

02Headless session management with status and error tracking

03119 GitHub stars

04High-level CLI for Playwright browser control and navigation

05Intelligent DOM snapshotting with interactive-only element filtering

06Automatic handling of authenticated egress proxies for HTTPS traffic

Use Cases

01Web scraping and data extraction from sites requiring authenticated proxy tunnels

02Capturing structured DOM snapshots for LLM context optimization

03Automated UI testing and verification of web applications in-container