DevToolsAIBrowserDebugging

Step-level debugger for browser agents

See exactly what your browser agent clicked and why it failed

Problem
When running browser agents, cost and speed are top pain points, and once a step misclicks or stalls it is hard to reproduce and diagnose. Most approaches rely on screenshots for the model to read, making element recognition flaky and debugging opaque.
Solution
A lightweight local debug panel that captures each step's element list, chosen action and latency, records failing steps with single-step replay, and lets developers compare how different models or strategies decide at the same step to find selector or prompt issues fast.
Users
Developers and small teams using browser agents for test automation, scraping or workflow automation
MVP
Browser extension or local proxy recording elements and actions per step; timeline view; single-step replay of failures; exportable debug snapshots
Revenue
Free local version plus cloud subscription billed by debug sessions or saved snapshots
Why now
Browser agents are moving from demos to production while debugging tooling is nearly absent, and element-list (non-screenshot) approaches are cheap to build locally

Source discussions · 3

  1. Hacker NewsShow HN: Fastbrowse, Browser agent that picks clicks with a System One model3↑ 2
  2. Hacker NewsShow HN: SkillWire, a searchable catalog for coding-agent skills3↑ 0
  3. Hacker NewsShow HN: SiteSpin – Build and update business websites through chat2↑ 0
← Back to list