Show HN: Rever-browser – AI-agent browser for reverse-engineering

Aug 5, 2026 · 5:51 AM UTC ·3 min read · 0 reactions · 0 comments · 3 views

#show #rever-browser #ai-agent #browser #reverse-engineering

TL;DR · WeSearch summary

You browse a target site in an embedded <webview>; the app captures every network request via the Chrome DevTools Protocol, and the agent can read that traffic, analyze the site's JavaScript bundles, and drive the tab itself through an in-process MCP tool server. The goal is to go from "what requests does this site make?" to "here is how to reproduce its API" without leaving the app. Features Live traffic capture — All Network.* events from the browsed tab are recorded into a ring buffer.

Key facts

▪You browse a target site in an embedded <webview>; the app captures every network request via the Chrome DevTools Protocol, and the agent can read that traffic, analyze the site's JavaScript bundles, and drive the tab itself through an in-p
▪The goal is to go from "what requests does this site make?" to "here is how to reproduce its API" without leaving the app.
▪Features Live traffic capture — All Network.* events from the browsed tab are recorded into a ring buffer.

About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 3,626 of its stories.

All Hacker News (AI / LLM) coverage →

Original article

GitHub

Read full at GitHub →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	GitHub
Canonical URL	https://github.com/greekr4/rever-browser
Publication time	Wed, 05 Aug 2026 05:51:59 +0000
Retrieval time	2026-08-05T06:05:44.630Z
Last seen	2026-08-05T06:05:44.630Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	myg5pSa7qU9S · 1 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

rever-browser The AI browser for API reverse engineering. 🌐 Website Demo · What is it? · Features · Getting started · Architecture Demo Ask in plain English — the agent drives a real browser, finds API flaws, proves them live, and turns it into a one-click macro. ▶ Watch the full demo What is rever-browser? rever-browser is an Electron app that pairs a real Chromium tab with an ACP-based coding agent. You browse a target site in an embedded <webview>; the app captures every network request via the Chrome DevTools Protocol, and the agent can read that traffic, analyze the site's JavaScript bundles, and drive the tab itself through an in-process MCP tool server. The goal is to go from "what requests does this site make?" to "here is how to reproduce its API" without leaving the app.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed

Discussion

0 comments