Agweb launches a focus‑free browser built for AI coding agents on macOS

What is Agweb and why does it matter?

Agweb is a macOS browser built on WebKit that is intended to be driven by autonomous coding agents rather than by human users. The project’s README describes it as “a browser for coding agents…no focus stealing, a tiny footprint, all tabs in one view.” By keeping the browser window in the background and presenting every agent’s tab on a single dashboard, Agweb lets developers run several agents simultaneously without the constant interruptions that Chrome‑based Playwright windows cause. For creators and researchers who rely on agents to scrape sites, test UI flows, or automate repetitive web tasks, a non‑intrusive, low‑overhead browser can dramatically improve productivity and reduce debugging friction.

How does Agweb differ from traditional browsers and Playwright?

Traditional browsers allocate a separate process per tab and aggressively use GPU resources; the README notes that five idle Chrome tabs can keep five to seven cores busy, while the same five pages in Agweb sit at 0 % CPU and use only 590 MB of memory. Playwright’s headless mode avoids UI rendering but still hides the page from the user, making it hard to tell whether a site is blocking the agent. Agweb solves both problems by staying a real window (so sites that block headless browsers behave normally) and by suspending idle tabs after a brief throttle period. In addition, Agweb’s command‑line interface mirrors Playwright commands where possible, but adds richer replies that describe exactly what changed on the page—fetches started, elements added, dialogs opened—so agents can skip the extra snapshot step and save token budget.

What are the key features for AI agents?

• Single‑window dashboard (⌘D) – Shows every open tab across all agents, each with the last command executed, allowing a developer to monitor progress at a glance.
• Workspace isolation – Agents run in named workspaces (e.g., agweb -w task) that keep their tabs, cookies, and logins separate but still share a common profile when needed.
• Native macOS events – Clicks, key presses, and pointer movements are generated as real system events, enabling hover menus, drag‑and‑drop, and other interactions that headless browsers cannot perform.
• Snapshot references – Each DOM element receives a persistent reference ([ref=eN]) that survives while the element remains on the page, simplifying diff operations (snapshot --diff).
• Secure secret handling – Commands such as fill --secret-cmd 'pass show site' let agents inject passwords without ever exposing the secret in the transcript; 1Password and Bitwarden CLIs are supported.
• Built‑in ad‑blocking – uBlock Origin filter lists are downloaded automatically every four days, and agents can toggle the blocker per workspace (agweb -w task adblock off).
• Video recording – video-start captures a tab to MP4 with cursor movements drawn in, useful for generating demos or debugging UI flows.
• Lightweight installation – A simple DMG install, followed by a one‑click setup for the command‑line tool and agent “skill” (pre‑packaged scripts for Claude Code and Codex), gets developers up and running quickly.

What are the current limitations?

While Agweb’s WebKit foundation gives it speed and low memory usage, the README calls out several constraints:

• No Chrome DevTools Protocol – Extensions, Chrome‑only APIs, and certain debugging features are unavailable, which may cause compatibility issues on sites that rely on Chrome‑specific behavior.
• Limited request mocking – Only fetch and XHR requests can be intercepted; static assets like images, scripts, and styles are listed by URL only (--static).
• Partial ad‑blocking – uBlock’s script‑based filters cannot run, so some video ads (e.g., on YouTube) and “please turn off your ad blocker” walls may still appear.
• macOS‑only – The binary requires macOS 26 or later, limiting the audience to Apple users. Developers needing full Chrome compatibility can fall back to Playwright for those edge cases, as the README suggests.

How to explore Agweb‑style automation with Grafy

Grafy does not yet ship a WebKit‑based agent browser, but the workflow that Agweb enables can be reproduced with existing Grafy tools. The Grafy Code studio lets you write and run automation scripts against web pages using the built‑in Operator agent, which performs browsing tasks with a headless Chrome instance. You can emulate Agweb’s “dashboard” concept by visualising each script’s output in a Grafy Graph where nodes represent pages, actions, and snapshots, making it easy to track state changes across multiple agents. For secure secret handling, Grafy Chat can be paired with your password manager via shell commands, mirroring Agweb’s fill --secret-cmd pattern. While Grafy’s Operator currently relies on Chrome, you can still benefit from Agweb’s ideas: keep agents isolated in separate workspaces, record video of interactions with Video Edit, and use the ad‑blocking filter lists that Operator downloads automatically. Developers interested in a native macOS WebKit agent can watch the Agweb demo videos (linked in the repository) and consider contributing a Grafy skill that wraps the agweb CLI, bringing the best of both worlds into a single multimodal workspace.

Frequently asked questions

How does Agweb keep idle tabs from using CPU?

Agweb throttles idle tabs after a short period and then suspends them entirely, which reduces CPU usage to near zero. The README cites a comparison where five idle Chrome tabs keep several cores busy, while the same five pages in Agweb use 0 % CPU.

Can Agweb handle sites that block headless browsers?

Yes. Because Agweb runs as a real macOS window using WebKit, it presents the same fingerprint as a regular Safari browser. This prevents the site‑level blocks that affect Playwright’s headless mode.

Is Agweb compatible with Chrome extensions?

No. The WebKit engine does not expose the Chrome DevTools Protocol, so Chrome‑only extensions and APIs cannot be attached. For tasks that require those features, the README recommends falling back to Playwright.

---

Source: Hacker News — front page — Show HN: Agweb – a browser for agents that stays out of your way