Agweb: A macOS Browser Optimized for Coding Agents

Overview

Agweb is a macOS-native browser built specifically for coding agents that require a persistent, non-intrusive environment. Unlike standard browser automation tools like Playwright, which often rely on Chrome instances that steal window focus and consume significant system resources, Agweb operates as a background-friendly WebKit engine that allows developers to monitor multiple agents simultaneously without interruption.

Key Features for Agent Workflows

Agweb addresses several pain points common in automated browser testing and agentic workflows:

  • Focus Management: The application never steals focus or triggers pop-ups. It is designed to run in the background while agents interact with pages via shell commands.
  • Resource Efficiency: By throttling and suspending idle tabs, Agweb significantly reduces CPU and memory usage compared to headless Chrome. In testing, five idle pages in Agweb consumed approximately 590 MB of memory, compared to 1.6 GB for equivalent Playwright-managed Chrome instances.
  • Unified Monitoring: The dashboard (accessible via ⌘D) provides a live view of every tab across all active agents, including the last command executed by each.
  • Agent-Specific Commands: Agweb uses a command set similar to playwright-cli, making it familiar to existing agents. It improves upon standard protocols by returning delta-based reports (e.g., elements added or removed) rather than requiring a full page snapshot after every action, which reduces token usage.
  • Security and Privacy: It includes built-in support for secret management via --secret-cmd, ensuring sensitive credentials like passwords do not appear in agent transcripts. It also integrates uBlock Origin’s blocklists to filter ads and trackers by default.

Operational Capabilities

Agweb is designed to act like a human user, utilizing native macOS events for clicks and key presses. This allows it to interact with hover menus and drag-and-drop elements that often fail in purely headless environments.

For complex authentication scenarios, the ask command allows a human to take control of a specific tab to solve CAPTCHAs or enter MFA codes without disrupting other running agents. Additionally, the browser supports named profiles, allowing multiple agents to share login sessions, which simplifies workflows that require authenticated access to web services.

Limitations and Considerations

As a WebKit-based tool, Agweb has specific constraints:

  • Engine Compatibility: It does not support the Chrome DevTools Protocol (CDP), meaning Chrome-specific extensions and standard Playwright/Chrome-based automation scripts will not attach to it.
  • Ad Blocking: While it uses uBlock Origin lists, it does not execute the full uBlock script engine, meaning some sophisticated ad-block detection walls may still be triggered.
  • Profile Isolation: Users should be aware that shared profiles mean actions taken by one agent—such as logging out or triggering rate limits—will affect all other agents using that same profile.

Community Feedback

Early adopters have noted the utility of the shared profile system, though some have raised questions regarding state isolation. When asked about potential cross-agent interference, developer paul_nameless emphasized the balance between shared state for convenience and the ability to use distinct workspaces. Others in the community have noted the browser's effectiveness as a replacement for Chrome in verification flows, particularly praising the decision to leave consent dialogs intact while blocking trackers.

Sources