rea.run

← Showcase

demo 2026-10-10 demobrowsercdpui

Browser UI reconstruction demo with REA + CDP

REA’s browser tools shine when you **observe** a page you may study — not when you scrape secrets. This demo wires Chrome’s remote-debugging port to REA and asks an agent to reconstruct a SaaS-style pricing layout.

Source meta

4 GitHub stars (snapshot)

Language: HTML

License: —

Updated: 2026-10-09

GitHub source ↗

rea.run rating

3/5 — Useful CDP demo — watch the tone

Quality. Shows REA browser tools + Chrome debug port for layout reconstruction.

Evidence. YouTube walkthrough + prompt templates; public marketing pages as inspiration.

Limits. Marketing “clone any UI” language; no license file; not a security audit.

For. Front-end builders practicing passive page observation with agents.

What it is. A small HTML/demo repo plus YouTube video: launch Chrome with --remote-debugging-port=9222, connect REA (list-browser-targets / inspect-web-page), and prompt an agent to emit a cleaned pricing page.

Relation to REA. Uses MCP/CLI browser observation over CDP. Setup prompts install rea-agents and run setup for the author’s agent host.

Healthy use. Stick to public marketing pages, strip tracking noise, and treat the output as a design study. Prefer rebuilding on your own stack over shipping lookalikes of proprietary dashboards.

Evaluation. Good onboarding for CDP + REA; tone is promotional. Pair with our legal-boundary FAQ and the Discussion #1406 own-app audit for a stronger ethics contrast.

Compliance

Frame as passive inspection of public pages and UI study you are allowed to observe — not credential theft, not cloning behind logins, not DRM bypass.

Takeaways

  • Passive CDP ≠ account takeover.
  • Public layout study ≠ credential harvest.
  • Rewrite on your stack; respect brand/ToS.

Related on rea.run

More on-site cases