BrowserTrack πŸ”

Local browser diagnostics shared with AI coding agents through Model Context Protocol (MCP).

BrowserTrack is a lightweight, framework-agnostic local development daemon and MCP bridge. It continuously captures browser runtime errors, unhandled promise rejections, console logs, network failures (4xx/5xx), user interaction breadcrumbs, live DOM snapshots, and visual design annotationsβ€”making them instantly accessible to AI coding assistants (Antigravity, Cursor, Claude Code, Windsurf) for autonomous debugging and closed-loop verification.


⚑ Why BrowserTrack? #

Traditional browser debugging with AI coding agents relies on manual copy-pasting of truncated error messages or sending cropped screenshots. BrowserTrack removes the human in the middle:

  • πŸš€ Real-time Diagnostics Pipeline: Your browser communicates with the local daemon via WebSockets.
  • 🎯 Visual Annotations & Notes: Hold Alt and click any element (or drag a region) to leave notes with DOM context and screenshots directly for coding agents.
  • πŸ“Œ Persistent On-Screen Markers: Visual note pins appear directly on your web pages and can be inspected or resolved with a single click.
  • πŸ€– Closed-Loop Verification: After an agent edits your code, it automatically reloads the browser, executes verification probes, checks for regressions, and captures before/after screenshots.
  • πŸ›‘οΈ Zero-Leak Security: Integrated with @visulima/redact to automatically sanitize passwords, auth tokens, cookies, credit cards, and secret query parameters.

πŸ—οΈ Architecture Overview #

Mermaid Diagram
View diagram source
graph TD
    A[Browser Client<br>Vanilla / React / Vue / Vite] <-->|WebSocket ws://127.0.0.1:7331| B[Local Daemon<br>SQLite Storage + Verification Engine]
    B <-->|Model Context Protocol / stdio| C[AI Coding Agents<br>Antigravity / Cursor / Claude Code]
    B -->|Static Docs & Web UI| D[Local Dashboard / Dev Server]

πŸš€ Quick Navigation #

2 min read Β· Created Β· Updated