March 11, 2026
Freeze! Step away from the spinner
Show HN: Open-source browser for AI agents
Freeze-frame AI browser lands; devs hype, skeptics probe the benchmarks
TLDR: A new open-source browser (ABP) pauses pages between actions so AI can browse in clean steps, boasting strong test scores. HN is split: fans say this could replace clunky control tools and even dodge CAPTCHAs, while skeptics demand fair benchmarks and wonder if it truly fixes Chrome’s RAM bloat
HN lit up as “Agent Browser Protocol” (ABP) dropped an open-source browser that literally freezes web pages between actions so AI agents don’t trip over spinning loaders. The pitch: simple HTTP calls, screenshots on every step, and a boastful 90.5% on the Online Mind2Web test using a specific AI model (“Opus 4.6”). Cue the applause… and the side-eye.
The hype crowd loved the vibe of “no WebSocket, no DevTools dance—just clicks and pics.” One fan basically asked if this kills the old browser control protocol in one swoop. Another wondered if freezing tabs could finally tame Chrome’s legendary RAM gobbling, dropping a meme-ready line about instances that “basically consume all available RAM.” The dev behind ABP, theredsix, jumped in with receipts: fewer CAPTCHAs than stealth tools, resolution controls, and paused “virtual time” so pages can’t tell the clock is weird—unless they phone home.
But skeptics pounced on the benchmark flex. If ABP scores 90.5% with Opus, what does Opus score with a “regular” setup? Fair question, spicy tone. Meanwhile, the demo clips show spinners frozen mid-twirl while the AI thinks—equal parts eerie and satisfying. Bottom line: half the thread is crowning ABP the freeze-frame browser for robots, the other half wants apples-to-apples numbers before popping champagne. Either way, the comment section is a chef’s kiss of delight, doubt, and memes
Key Points
- •ABP is a custom Chromium build that converts web browsing into discrete, step-based interactions for AI agents.
- •Each action returns a settled page state (screenshot + event log) and pauses JavaScript and virtual time to prevent race conditions.
- •ABP communicates over HTTP with MCP and REST interfaces, avoiding WebSockets and CDP session management.
- •Reported overhead is ~100ms per action, attributing performance limits primarily to the LLM.
- •Quick-start guides are provided for Claude Code, Codex CLI, Opencode, and REST; a demo shows tasks on DoorDash and Google Maps, and ABP reports 90.53% on Online Mind2Web.