Claude Code sessions are not flat transcripts. Power Claude’s Session Flow Explorer maps agents, tools, and turns — with Mermaid export — so you see what ran, not a wall of JSONL.
TL;DR: Session Explorer → Graph/Lifetime maps agents, tools, and turns. Export Mermaid for docs. CLI: pc tree --format mermaid. Different from the static Harness Flow Graph.
Product feature · Related: cross-session messaging.
The problem
JSONL stores a session; it does not map it. Operators need a graph of sub-agents, tools, durations, and evidence — and a Mermaid export for postmortems.
What Session Flow Explorer is
- Real sessions (production-aligned data paths)
- Agent fan-out as first-class nodes
- Evidence I/O on tool turns
- Mermaid export +
pc tree --format mermaid - Fail-hard validation (no ghost agents)
Session Flow vs Harness Flow
| Surface | Answers |
|---|---|
| Session Flow Explorer | What did this session do? |
| Harness Flow Graph | What will the edit pipeline run? |
How to use
- Session Explorer → open a session → Graph / Lifetime
- Click nodes for Evidence I/O
- Copy Mermaid for docs
- CLI:
pc tree --format mermaid
Frequently asked questions
Is this Claude Code history?
No. Transcripts store; Flow Explorer projects structure and Mermaid.
Does export leave my machine?
No. Local graphs only.
Related
Independent third-party software. Not affiliated with Anthropic.