HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
theredsix
agent-browser-protocol
C++2026–2026
theredsix / agent-browser-protocol

agent-browser-protocol

Deterministic browser automation. Works out of the box with Claude/Codex/OpenCode

AI & Machine LearningWeb DevelopmentAutomation & Workflows
Explore on GitHubRead Hacker News discussions
2Distinct people
4Mentions
0Explicit recommenders
491GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Deterministic browser automation. Works out of the box with Claude/Codex/OpenCode

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval4 dated mentions

Observed mentions: 2026-03-06 15:12:06 UTC to 2026-03-11 20:57:54 UTC.

0122026-03-06 12:00:00 UTC to 2026-03-06 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 6, 12:002026-03-06 18:00:00 UTC to 2026-03-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-07 00:00:00 UTC to 2026-03-07 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-07 06:00:00 UTC to 2026-03-07 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-07 12:00:00 UTC to 2026-03-07 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-07 18:00:00 UTC to 2026-03-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-08 00:00:00 UTC to 2026-03-08 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-08 06:00:00 UTC to 2026-03-08 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-08 12:00:00 UTC to 2026-03-08 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-08 18:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 00:00:00 UTC to 2026-03-09 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 9, 00:002026-03-09 06:00:00 UTC to 2026-03-09 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 12:00:00 UTC to 2026-03-09 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 18:00:00 UTC to 2026-03-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 00:00:00 UTC to 2026-03-10 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 06:00:00 UTC to 2026-03-10 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 12:00:00 UTC to 2026-03-10 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 18:00:00 UTC to 2026-03-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-11 00:00:00 UTC to 2026-03-11 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-11 06:00:00 UTC to 2026-03-11 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-11 12:00:00 UTC to 2026-03-11 18:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-03-11 18:00:00 UTC to 2026-03-12 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 11, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 6, 12:002026-03-06 12:00:00 UTC2026-03-06 18:00:00 UTC110
Mar 6, 18:002026-03-06 18:00:00 UTC2026-03-07 00:00:00 UTC000
Mar 7, 00:002026-03-07 00:00:00 UTC2026-03-07 06:00:00 UTC000
Mar 7, 06:002026-03-07 06:00:00 UTC2026-03-07 12:00:00 UTC000
Mar 7, 12:002026-03-07 12:00:00 UTC2026-03-07 18:00:00 UTC000
Mar 7, 18:002026-03-07 18:00:00 UTC2026-03-08 00:00:00 UTC000
Mar 8, 00:002026-03-08 00:00:00 UTC2026-03-08 06:00:00 UTC000
Mar 8, 06:002026-03-08 06:00:00 UTC2026-03-08 12:00:00 UTC000
Mar 8, 12:002026-03-08 12:00:00 UTC2026-03-08 18:00:00 UTC000
Mar 8, 18:002026-03-08 18:00:00 UTC2026-03-09 00:00:00 UTC000
Mar 9, 00:002026-03-09 00:00:00 UTC2026-03-09 06:00:00 UTC000
Mar 9, 06:002026-03-09 06:00:00 UTC2026-03-09 12:00:00 UTC000
Mar 9, 12:002026-03-09 12:00:00 UTC2026-03-09 18:00:00 UTC000
Mar 9, 18:002026-03-09 18:00:00 UTC2026-03-10 00:00:00 UTC000
Mar 10, 00:002026-03-10 00:00:00 UTC2026-03-10 06:00:00 UTC000
Mar 10, 06:002026-03-10 06:00:00 UTC2026-03-10 12:00:00 UTC000
Mar 10, 12:002026-03-10 12:00:00 UTC2026-03-10 18:00:00 UTC000
Mar 10, 18:002026-03-10 18:00:00 UTC2026-03-11 00:00:00 UTC000
Mar 11, 00:002026-03-11 00:00:00 UTC2026-03-11 06:00:00 UTC000
Mar 11, 06:002026-03-11 06:00:00 UTC2026-03-11 12:00:00 UTC000
Mar 11, 12:002026-03-11 12:00:00 UTC2026-03-11 18:00:00 UTC211
Mar 11, 18:002026-03-11 18:00:00 UTC2026-03-12 00:00:00 UTC101

What Hacker News says

4 sources
theredsix·Mar 11, 2026Submission

Show HN: 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 summa
Read the rest
ry 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 completed As 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
155 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.