IDE Plugin That Logs and Visualizes Your Debugging Session Flow

The Debugging Time Machine

Every developer knows the frustration: you hit a breakpoint, inspect a variable, step forward — and then the bug slips away. You restart, re-navigate, re-inspect. The context you built evaporates. A new VS Code extension, quietly released in late May 2025, aims to make that cognitive overhead a thing of the past.

The plugin, built by a small team of ex-observability engineers, records every breakpoint hit, variable inspection, and stack trace during a live debugging session. Instead of relying on manual notes or screenshots, it serializes the entire execution flow into an interactive timeline. Developers can replay the session frame-by-frame, scrub through breakpoint hits, and inspect the state of variables at each moment — all without re-running the application.

How It Works

The extension hooks into VS Code's debugging protocol at a low level, intercepting events without adding noticeable latency. Each breakpoint hit is tagged with the call stack, local variables, and the exact line of code. Developers can annotate events with notes — 'this is where I expected the discount to be applied' — which become part of the shared recording.

Recordings are stored locally as JSON files, typically 200–500 KB for a 30-minute session. They can be exported as a single file and imported by any teammate with the extension installed. The plugin also supports a lightweight cloud sharing feature: generate a unique link that opens the timeline in a read-only web viewer, no VS Code install required.

An industry analyst who evaluated the tool described it as 'a debugger DVR.' The timeline view color-codes events by type: blue for breakpoints, green for variable inspections, red for exceptions. Clicking any event jumps the editor to the relevant file and line, restoring the full context from the moment the event was recorded.

Real-World Impact

Early metrics from the beta program paint a compelling picture. Across 847 recorded sessions, developers averaged 47 breakpoint hits and 142 variable inspections per 30-minute debugging session. The tool's search and filter capabilities let users jump directly to exceptions or specific variable names, cutting through the noise.

One engineering team at a logistics company used the plugin to debug a race condition that had eluded them for three weeks. By replaying a session recorded by a developer in Berlin, a colleague in San Francisco spotted a timing assumption that was incorrect. The fix was deployed within hours. 'We would have never caught that in a screenshare,' the team lead said.