Open-source browser for AI agents

Hi HN, I forked chromium and built agent-browser-protocol (ABP) after noticing that most browser-agent failures aren’t really about the model misunderstanding the page. Instead, the problem is that the model is reasoning from a stale state.ABP is designed to keep the acting agent synchronized with the browser at every step. After each action (click, type, etc), it freezes JavaScript execution and rendering, then captures the resulting state. It also compiles the notable events that occurred during that action loop, such as navigation, file pickers, permission prompts, alerts, and downloads, and sends that along with a screenshot of the frozen page state back to the agent.The result is that browser interaction starts to feel more like a multimodal chat loop. The agent takes an action, gets back a fresh visual state and a structured summary of what happened, then decides what to do next from there. That fits much better with how LLMs already work.A few common browser-use failures ABP helps eliminate: * A modal appears after the last Playwright screenshot and blocks the input the agent was about to use * Dynamic filters cause the page to reflow between steps * An autocomplete dropdown opens and covers the element the agent intended to click * alert() / confirm() interrupts the flow * Downloads are triggered, but the agent has no reliable way to know when they’ve completedAs proof, ABP with opus 4.6 as the driver scores 90.5% on the Online Mind2Web benchmark. I think modern LLMs already understand websites, they just need a better tool to interact with them. Happy to answer questions about the architecture, forking chrome or anything else in the comments below.Try it out: `claude mcp add browser -- npx -y agent-browser-protocol --mcp` (Codex/OpenCode instructions in the docs)Demo video: https://www.loom.com/share/387f6349196f417d8b4b16a5452c3369

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

76

out of 100

Verdict

BUILD

high confidence

Competition

12

competitors found, emerging market, funded players

Trend

8 community mentions

An open-source browser protocol that solves AI agent reliability issues by synchronizing browser state, backed by strong benchmark performance, but faces a crowded market and high build complexity for a solo builder.

The pain

AI agents frequently fail when interacting with dynamic web pages because they reason from stale browser states, missing crucial updates like modals, reflows, or alerts. This leads to brittle automation and significant debugging overhead.

The gap

Current browser automation tools don't explicitly address the 'stale state' problem at the architectural level by freezing JS and capturing detailed events after each action. ABP's unique approach creates a technical gap in robust state synchronization, despite a crowded market for general AI browser agents.

Build angle

Develop a hosted API service or premium version of the ABP, offering reliable, scalable browser sessions for AI agents, targeting developers who prioritize agent reliability and performance over cost. Offer advanced features like specific event filters or custom environment controls.

Strengths

  • Addresses a real, severe, and specific technical pain point for AI agent developers.
  • Solution is validated by a high benchmark score (90.5% on Mind2Web), demonstrating effectiveness.
  • Clear, defensible technical innovation with a novel approach to browser-agent synchronization.
  • Target market (AI agent developers) is growing rapidly and has purchasing power.
  • Open-source nature provides excellent distribution and community potential.

Risks

  • High technical complexity and ongoing maintenance burden for a solo builder due to forking Chromium.
  • Crowded market with several funded competitors, making differentiation and market penetration challenging.
  • Monetization strategy for an open-source protocol requires careful validation beyond the initial technical offering.
  • Risk of being commoditized or integrated by larger platforms if not swiftly productized.

Next steps

  1. Conduct in-depth interviews with current users of browser automation tools for AI agents (Playwright, Puppeteer) to confirm specific pain points and willingness to pay for a hosted, more reliable solution.
  2. Explore potential business models beyond pure open source (e.g., hosted API, enterprise support, premium features) and validate pricing structures.
  3. Gather user testimonials and case studies from early adopters to build social proof and articulate clear ROI.
  4. Assess the effort required to maintain and update the Chromium fork, considering future browser updates and security patches.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Open-source browser for AI agents”.

Open FlyBot