An open-source project called Agweb is proposing a different browser setup for developers who run several coding agents at the same time. The macOS application places agent-controlled pages in one visible WebKit window and is designed not to take keyboard focus while automation is running.
The developer says the project grew out of two practical problems. Automated Chrome windows controlled through Playwright could interrupt typing by moving focus, while fully headless browsers made it difficult to see what an agent was doing and could be rejected by some websites. Agweb keeps the interaction visible without asking the developer to manage a separate browser window for every agent.
Agents operate the application from the shell through an `agweb` command whose interface is modeled on Playwright-style browser automation. The repository says command responses include the result of an action, reducing the need to request another page snapshot after every click. A help command lists supported operations, and when Agweb lacks an exact Playwright command name it suggests its own equivalent.
The application uses WebKit, the engine behind Safari, rather than bundling Chromium. It also suspends idle tabs to limit resource use. The project's author reports that five open pages showed no CPU usage while idle on the developer's Mac, contrasting that observation with a Chrome GPU process that consumed several cores in the same personal setup. That is a developer-reported comparison, not an independent benchmark, and performance will depend on the pages and machine involved.
Agweb's interface includes a dashboard for viewing tabs together, configurable column layout and text size, CPU and memory readouts, and an ad-blocking switch. It bundles the MIT-licensed Defuddle library for extracting text. Developers can launch a second isolated instance by assigning a separate data directory, which can keep test activity away from the primary browser state.
The repository provides a disk image through its releases page and instructions for building from source. The current requirements specify macOS 26 or later, with Xcode 26 or later needed for a local build. The project includes a shell self-test that exercises commands against a local page and a Swift unit-test suite.
Agweb is narrowly aimed at coding-agent workflows rather than general browsing. Its value proposition is operational: a developer can observe several automated sessions in one place, preserve control of the keyboard and reduce idle browser overhead. Whether it fits a team will depend on its macOS requirement and on how closely existing automation relies on Chrome-specific behavior.
