Wirebrowser
Wirebrowser
Runtime Object Control for modern debugging
Wirebrowser introduces Breakpoint-Driven Heap Search (BDHS) combined with Live Object Search to find the code that creates an object, locate its live reference in memory, inspect it, and patch it at runtime — integrated with network interception, automation, and API collections.
Built directly on Chrome DevTools Protocol (CDP). Not a DevTools replacement — a new debugging capability.
Wirebrowser is built around a new debugging workflow focused on origin tracing and runtime memory, not logs or manual breakpoints.
1 — Origin Trace (BDHS)
Step execution, capture full heap snapshots, and search them to pinpoint the exact user-land function where an object first appears.
2 — Live Object Search
Search real runtime objects by value, structure, or prototype and get an actual reference — not a serialized copy.
3 — Runtime patching
Modify the object directly in memory and immediately observe how the application reacts.
Traditional debugging starts from code and requires guessing where to place breakpoints.
Origin Trace (build on top of Breakpoint-Driven Heap Search) reverses the process:
you start from a value and Wirebrowser discovers where it is created in user code.
With Origin Trace, you can:
▶ start from a runtime value or object
▶ trace the exact function where it is created
▶ identify the precise execution point where it appears
This makes it possible to answer "where did this value come from?" without guesswork.
Heap snapshots let you observe objects.
Live Object Search lets you interact with them.
Instead of searching frozen snapshots, Wirebrowser searches live runtime memory, giving you access to
actual
object references.
This means you can:
▶ search objects by key, value or object similarity
▶ inspect them while they are in use
▶ patch them at runtime
Something that is fundamentally impossible with snapshots.
Both Object Search and Origin Trace rely on object
similarity, not just exact matches.
Instead of looking only for identical values, Wirebrowser can identify structurally similar objects across
runtime memory and execution steps.
Intercept, modify, and replay HTTP requests and responses directly inside the debugging workflow.
▶ inspect and rewrite requests and responses in real time
▶ replay captured traffic with modified parameters
▶ correlate network data with live objects in memory
This makes it possible to move seamlessly from network data → runtime state → code origin.
API Collections let you organize, edit, and replay HTTP requests in multiple formats.
Unlike standalone API clients, collections in Wirebrowser are:
▶ built from intercepted traffic
▶ reusable across debugging sessions
▶ directly connected to automation and memory inspection
They are meant to extend debugging flows, not replace Postman-like tools.
Wirebrowser brings together origin tracing, live runtime inspection,
network interception, and API workflows into a single, coherent debugging experience.
If you need to understand where data comes from, how it flows, and how it behaves at runtime,
Wirebrowser gives you the tools to do it — without context switching.