The Agweb dashboard (⌘D) displays every active tab and the last command from each coding agent.
*A new macOS browser built on WebKit lets automation agents run without stealing focus. It promises a tiny footprint, live dashboards and native macOS events, aiming to replace Playwright Chrome and headless browsers for developers.*
A new open‑source browser called Agweb has hit GitHub, targeting developers who run multiple coding agents on macOS. Built on WebKit, the same engine behind Safari, Agweb promises a window that never steals focus, letting agents operate from the command line while the user continues working uninterrupted. The author, frustrated by Playwright Chrome windows hijacking the keyboard and headless browsers being blocked by sites, created a single‑window solution that stays visible, reports live actions and suspends idle tabs.
The browser’s resource profile is striking: five idle pages sit at 0% CPU and consume just 590 MB of RAM, far below the 730 MB used by Headless Chrome and the 1.6 GB by Playwright Chrome. Agweb bundles uBlock Origin lists for ad and tracker blocking, updates them every four days, and offers a dashboard that aggregates every agent’s tabs, commands and CPU/memory readouts. Native macOS events generate real clicks and key presses, ensuring hover menus and drag‑and‑drop work without triggering headless detection.
Agweb runs in a single window that never takes focus, letting agents drive it from the shell while the user works elsewhere. Idle tabs are throttled then suspended, so five open pages sit at 0% CPU on the author's Mac. Memory use stays at 590 MB, compared with 730 MB for Headless Chrome and 1.6 GB for Playwright Chrome. The dashboard (⌘D) shows every tab of every agent live, with each agent's last command. Native macOS events generate real clicks and key presses, so hover menus and drag‑and‑drop work without headless detection. Snapshots give each element a persistent ref, and the CLI reports only what changed, cutting token usage.
The author measured five idle pages consuming virtually no CPU and only 590 MB of RAM. By contrast, Headless Chrome used 730 MB and Playwright Chrome consumed 1.6 GB. Agweb’s tiny footprint stems from WebKit’s efficient engine and aggressive tab suspension. The app downloads uBlock Origin lists every four days, blocking ads and trackers without extra processes. CPU and memory readouts appear in Settings (⌘,). The lightweight design lets multiple agents run concurrently without the GPU process that keeps five to seven cores busy in Chrome.
Each agent works in its own workspace, grouped by agent in the sidebar. A named profile (e.g., -p work) shares logins across agents, allowing simultaneous access to the same accounts. The CLI mirrors Playwright commands, so agents can open URLs, take snapshots, click elements and receive detailed replies. The dashboard aggregates every tab, showing live activity and the last command per agent. Agents can request a tab for login, MFA or CAPTCHA without stealing focus. Secret commands (fill --secret‑cmd) let agents type passwords from external password stores without exposing them in transcripts.
Agweb runs on WebKit only, so it cannot use the Chrome DevTools Protocol or attach Chrome extensions. Sites that rely on Chrome‑only features may misbehave. The built‑in ad blocker uses uBlock Origin lists but cannot execute uBlock scripts, allowing YouTube ads and some "turn off your ad blocker" walls to slip through. Route mocks handle only fetch and XHR requests; static request listings expose only URLs for images, scripts and styles. For capabilities missing in WebKit, the author recommends falling back to Playwright.
Agweb is a macOS browser built on WebKit for coding agents. It was created because Playwright Chrome windows stole keyboard focus and headless browsers were blocked by some sites, leaving developers guessing what went wrong.
Five idle pages in Agweb use 0% CPU and 590 MB of RAM, while Headless Chrome uses 730 MB and Playwright Chrome uses 1.6 GB, showing Agweb's significantly lower footprint.
No. Agweb runs on WebKit only, so it cannot use the Chrome DevTools Protocol or attach Chrome extensions, and Chrome‑only sites may misbehave.
Agweb delivers a lean, focus‑free browsing environment that could reshape how developers orchestrate automation agents on macOS. By slashing CPU load, trimming memory use and exposing a live dashboard, it addresses the pain points that have long plagued Playwright and headless setups. While WebKit‑only constraints limit some advanced Chrome features, the open‑source nature invites rapid iteration. If the community embraces its CLI and profiling tools, Agweb may become the default browser layer for large‑scale agent fleets.
Sources: Hacker News (Show HN: Agweb – a browser for agents that stays out of your way), GitHub repository https://github.com/paul-nameless/agweb