Skip to main content
Trace connects your AI Agent (Cursor, Claude, Windsurf) directly to your application’s runtime, giving it the ability to see, interact, and fix bugs without human intervention.
“AI builds at the speed of thought. Trace ensures it doesn’t break things.”

​
Why Trace?

In the “Vibe Coding” era, code is generated faster than you can read it. Static analysis isn’t enough—you need to know what’s happening right now in the browser or server. Trace solves the “Black Box” problem by giving your Agent:
  • Observability: Access to Console Logs, Network Traffic, and DOM Snapshots.
  • Interaction: Tools to Click, Type, and Simulate user behavior.
  • Verification: Automated checks to ensure the “fix” actually worked.

​
The Architecture

Trace sits between your Agent and your Runtime.

​
Core Components

​
1. The SDK (@probebrowser/sdk)

The heart of the system. A lightweight drop-in for Next.js, React, or Node.js apps.
  • Auto-Instrumentation: Captures errors and state automatically.
  • Universal: Works in Chrome, Edge, and Headless environments.

​
2. The MCP Server (Bridge)

The translation layer that exposes 90+ debugging tools to your Agent.
  • Standard Protocol: Built on the Model Context Protocol.
  • Plug & Play: Works instantly with Cursor and Claude Desktop.

​
3. The CLI (trace-cli)

Your command center for continuous debugging.
  • trace doctor: Verify your setup.
  • trace listen: Watch for runtime exceptions in real-time.

​
Philosophy: Runtime is Truth

We believe that code is only as good as its execution. Trace doesn’t guess based on text files; it reports the cold, hard truth of what actually happened in the DOM or the Network tab.