webctl is a local browser automation CLI for developers and AI agents that need to read websites and interact with pages. It runs Chromium through Playwright on macOS, Windows and Linux, and supports container deployment. Its main distinction is control over how much page information reaches an agent's context: you can filter results before the agent reads them.
Page output includes structured metadata such as prices, ratings and authors, plus readable Markdown and accessibility snapshots. Filters can focus on interactive elements or a specific page region, while landmark-aware snapshots reduce navigation, footer and sidebar content. Human-readable and JSON output also fit shell scripts and tools such as jq.
For interaction, webctl can click elements by their text or accessibility role, fill forms, handle dropdowns and capture screenshots. It can return the updated page state alongside an action or batch several actions together. Automatic retries handle overlays, cookie prompts and elements that need scrolling into view. Load detection ignores ongoing media streams and WebSocket connections.
The browser can stay visible for human intervention or run headless for unattended work. Sessions persist across commands, cookies stay on disk, and named profiles keep cookies separate. Agent integrations include Claude Code, Codex, Cursor and Gemini CLI. Domain policies restrict the sites the browser can visit, and operating-system credential checks prevent other users from controlling your browser session.
Claim this page and we'll verify you by hand. webctl gets the verified badge, and you can upgrade the listing to be featured on localhosted. Proud to be listed? Put our badge on your site.
Want more people to find webctl?Promote it
Something wrong or outdated on this page?
11.3KUpdated 1 day agoMIT
macOS · Windows · Linux · Docker#Browser automation#Multi-user access#PII redaction
CamoFox Browser is a self-hosted browser server for developers whose AI agents need to browse sites that block ordinary automation. It builds on Camoufox, a Firefox fork that changes browser fingerprints inside the engine rather than through JavaScript patches. This approach targets detection systems such as Cloudflare and Google's bot checks.
2.7KUpdated 1 day agoApache-2.0
macOS · Windows · Linux#Agent Skills#Browser automation#Code execution
6.2KUpdated 4 months agoMIT
macOS · Docker#Agent Skills#Browser automation#Code execution
28.2KUpdated 1 day agoApache-2.0
Linux · Docker#Browser automation#Code execution#MCP
7.7KUpdated 3 days agoApache-2.0
macOS · Docker · Web#Browser automation
Steel is a browser API for developers building AI agents that interact with websites. It runs Chrome sessions locally or on a self-hosted server through Docker, so you can keep browser infrastructure on hardware you control. The code uses the Apache 2.0 license. Steel also offers a hosted service where browser sessions run in its cloud.
701Updated 2 days ago
#Browser automation#Human approval#MCP
Fortress is a Chromium fork for developers whose scrapers and AI agents encounter browser fingerprint checks. It runs as a local browser binary and changes the fingerprint inside Chromium's C++ code, rather than applying JavaScript overrides that pages can inspect.
Moli is a headless browser you run on your own machine or server for AI agents, web scraping and retrieval pipelines. It can read pages and execute JavaScript without spending resources on visual rendering for every request. Layout and rendering run only when a task needs them, such as capturing a screenshot or clicking at specific coordinates.
bb-browser lets AI agents work through your local Chrome browser using the website accounts you're already signed into. It's for people building agents that need to research across websites or interact with authenticated pages without a separate API integration for each service. The project is open source under the MIT license.
Obscura is a headless browser engine for developers building AI agents and web scraping systems that need many independent browser sessions. Each session starts with fresh state, so cookies, logins, and cached data don't carry between tasks. It's written in Rust and runs without Chromium, with a smaller memory footprint intended to support more concurrent sessions per machine.