Build from source with Cargo
Install the single Rust binary locally on Linux, macOS, or WSL2:
git clone https://github.com/smota/dendro.git
cd dendro
cargo install --path crates/dendro-cliGet started
Inspect your existing AI sessions in two minutes.
Dendro reads the local session logs your coding agents have already written. You don't need to configure a server, create an account, or re-run your workflows to see your first report.
Sync your local logs and explore
Ingest your existing agent transcripts and launch the interactive terminal cockpit:
# Ingest local session logs
dendro sync
# Launch the interactive TUI
dendro tuiShare a report or ask in plain English
Generate a self-contained browser report or query your session history directly:
# Export an offline HTML report
dendro loops handoffs --html report.html
# Ask a question in plain English
dendro ask "top cost by model this week"Frequently asked questions
Common questions before you adopt.
Does Dendro send any of my prompts, code, or session logs to the cloud?
No. Everything runs locally on your machine against an embedded analytical database. Even when you export an HTML report for colleagues, Dendro strips prompts, file paths, and secrets and aliases seat names to Seat 1, Seat 2, and so on.
Do I need to install hooks before my agents run to get value?
No. Dendro reads the historical transcript files that Claude Code, Codex, Gemini/AGY, Grok, Pi, and OpenRig already save on your disk. You immediately get visibility over past sessions from the moment you run dendro sync.
When should I use Dendro versus agent-otel-bridge?
Use agent-otel-bridge when you want live OpenTelemetry traces and alerts streaming into Grafana, Datadog, or Honeycomb while agents are running. Use Dendro when you want deep retrospective analysis of where time, handoffs, rework, and budget went across completed sessions.