Trace
Domain: trace
Time-travel debugging domain that records CDP events into SQLite for SQL-based querying and heap snapshot comparison.
Profiles
- workflow
- full
Typical scenarios
- Record browser events
- Query trace data with SQL
- Diff heap snapshots
Common combinations
- trace + debugger + browser
Representative tools
start_trace_recording— Start recording CDP events, debugger state, and memory writes into a SQLite trace database.stop_trace_recording— Stop the active trace recording and finalize the SQLite database.query_trace_sql— Execute a read-only SQL query against a trace database.seek_to_timestamp— Reconstruct application state at a specific timestamp from a recorded trace.diff_heap_snapshots— Compare two heap snapshots from a trace and return the differences.export_trace— Export a trace database to Chrome Trace Event JSON format.summarize_trace— Generate a compact, LLM-friendly summary of a trace database.
Full tool list (7)
| Tool | Description |
|---|---|
start_trace_recording | Start recording CDP events, debugger state, and memory writes into a SQLite trace database. |
stop_trace_recording | Stop the active trace recording and finalize the SQLite database. |
query_trace_sql | Execute a read-only SQL query against a trace database. |
seek_to_timestamp | Reconstruct application state at a specific timestamp from a recorded trace. |
diff_heap_snapshots | Compare two heap snapshots from a trace and return the differences. |
export_trace | Export a trace database to Chrome Trace Event JSON format. |
summarize_trace | Generate a compact, LLM-friendly summary of a trace database. |