What is agweb?
agweb is a browser built for coding agents rather than people. Agents drive it with the agweb command, which copies playwright-cli's verbs, and each agent gets its own workspace and tabs, grouped by agent in the sidebar. The window stays visible but never comes to the front, and a dashboard (Cmd-D) shows every agent's tabs live with each one's last command. Snapshots give elements refs that last while they are on the page, and every action replies with what it changed.
It is built on WebKit, the engine behind Safari, with no Chrome DevTools Protocol, and needs macOS 26 or later. It is MIT-licensed Swift from one maintainer, Paul Nameless, who wrote 168 of the repository's commits. The repository was created on 11 November 2026, had about 243 GitHub stars five days later, and shipped v0.3.0 on 14 November 2026.
Is agweb worth it?
agweb exists because running several coding agents with Playwright on one Mac is miserable: each Chrome window grabs focus mid-sentence, and headless browsers get blocked or fail invisibly. agweb answers with one real WebKit window that agents drive over a CLI and that never activates, with clicks and keys sent as native macOS events straight to the page. The author's own figures for five idle pages are 590 MB, against 730 MB for headless Chrome and 1.6 GB for Playwright's Chrome, because idle tabs are throttled and then suspended.
The agent-facing design is thoughtful. Commands match playwright-cli where they can, so agents that know Playwright already know most of them. Each reply lists what the action changed, including fetches, added and removed elements, dialogs and console errors, so the agent rarely needs another snapshot. Actions wait for the fetches they caused, and ask hands a tab to you for MFA or a CAPTCHA without taking focus.
The security posture needs reading before you point it at real accounts. There is no network port: the CLI talks to the app over a Unix socket in ~/Library/Application Support/agweb, created with owner-only permissions. Any program running as your user can still drive it, and the README describes no site allowlist, so an agent can open any URL, including localhost and LAN addresses. Agents can run JavaScript in the page with eval, and read, set and export cookies and localStorage as Playwright storage-state JSON. A fresh profile lives in memory only. A named profile keeps its logins on disk and is shared by every agent using it at once, so one agent logging out or tripping a rate limit affects them all, a point Hacker News commenters raised and the maintainer confirmed has no fork option yet. fill --secret-cmd keeps passwords out of the transcript, which is a good default to adopt.
The catch: WebKit only. Without the Chrome DevTools Protocol, Playwright, Chrome extensions and CDP-based tools cannot attach, Chrome-only sites may misbehave, and the ad blocker cannot run uBlock's scripts. It needs macOS 26, which rules out older Macs and every Linux CI runner. And it is one maintainer's project with three releases in four days, so commands are still settling. BrowserOS neo covers similar ground in Chromium with an agent dashboard, at the cost of a full browser fork.
Our take: for a Mac developer running two or three agents that test local web apps, agweb removes a daily irritation, and running it on throwaway profiles keeps the shared-login risk small. Anything that needs CDP, Linux or a hardened sandbox should stay on Playwright for now.
Where it earns its place
A solo full-stack developer running Claude Code and Codex side by side on a Mac
Let both agents check the local app in a browser while I keep typing
Install the DMG, then the CLI and agent skill from the Help menu; each agent opens its own workspace on localhost and the dashboard shows both. Free; the saving is not having a Chrome window jump to the front mid-sentence.
A front-end engineer at a small agency
Have an agent record a short demo video of a fixed bug for the client
The agent reproduces the flow and uses video-start and video-stop to record the tab to MP4 with the pointer and clicks drawn in, with idle time between commands cut to 1.5 seconds by default.
A developer testing a staging site behind a login
Keep test credentials out of the agent's transcript
Create a dedicated named profile for staging, have the agent fill the password with --secret-cmd from pass, 1Password or Bitwarden CLI, and use ask for the MFA step. Keep that profile away from personal accounts, since every agent on it shares the session.
Before you commit
- Setup
- Download Agweb.dmg from the releases page, drag it to Applications and open it, then Help > Install Command Line Tool and Help > Install Agent Skill (for Claude Code and Codex). Needs macOS 26 or later; building from source needs Xcode 26.
- Integrations
- The agweb CLI with playwright-cli-style commands; an agent skill for Claude Code and Codex; secrets through pass, 1Password or Bitwarden CLIs; Playwright storage-state JSON import and export. No CDP, so no Playwright or Puppeteer attach.
- Data and privacy
- Runs locally. The CLI talks to the app over a Unix socket created with owner-only permissions; no network port. Fresh profiles are in memory; named profiles keep WebKit data and session cookies on disk, with cookie and URL files at 0600. Outbound calls beyond your agents' browsing: uBlock Origin list downloads every 4 days and update checks only when you ask; it never updates itself.
- Cost at scale
- Free. The cost is your agents' model tokens, which the change-reporting replies are meant to cut.
- Limits
- WebKit only; route mocks fetch and XHR only; YouTube ads and some anti-ad-blocker walls get through; no site allowlist; agents on one named profile share logins and can affect each other's sessions.
What’s good
- Never takes focus; one visible window for every agent
- Replies report what each action changed, saving snapshots and tokens
- Idle tabs suspended; 590 MB for five idle pages by the author's measure
- Unix socket with owner-only permissions, no network port
What’s not
- macOS 26 or later only; no Linux or Windows
- WebKit only: no CDP, so Playwright and Chrome extensions cannot attach
- Named profiles share logins across all agents at once
- Five days old, one maintainer, commands still changing
Best for
Mac developers on macOS 26 who run several coding agents against web apps and want to watch them without losing their keyboard.
agweb alternatives
agweb: common questions
- Is agweb worth it?
- agweb solves a narrow, real annoyance well, browser windows stealing your keyboard while agents work, but it is five days old, macOS 26 only and shares logins across agents by design. We rate it 3.7 out of 5.
- How much does agweb cost?
- Free and open source under the MIT licence.
- What are the downsides of agweb?
- macOS 26 or later only; no Linux or Windows; webKit only: no CDP, so Playwright and Chrome extensions cannot attach; named profiles share logins across all agents at once; five days old, one maintainer, commands still changing.
- Who is agweb best for?
- Mac developers on macOS 26 who run several coding agents against web apps and want to watch them without losing their keyboard.
- How much does agweb cost for a team or in production?
- Free. The cost is your agents' model tokens, which the change-reporting replies are meant to cut.
- Is agweb safe for company data?
- Runs locally. The CLI talks to the app over a Unix socket created with owner-only permissions; no network port. Fresh profiles are in memory; named profiles keep WebKit data and session cookies on disk, with cookie and URL files at 0600. Outbound calls beyond your agents' browsing: uBlock Origin list downloads every 4 days and update checks only when you ask; it never updates itself.
- What are the best agweb alternatives?
- The closest alternatives we have reviewed are BrowserOS, Browser Use, Stagehand and Steel.
Answers checked Nov 16, 2026.