Dendro mark DendroThe Flight Recorder · v0.7.0
The Flight Recorder for AI Workflows · MIT Open Source

Read the growth rings of your AI workflows.

Six open agent terminals look productive—even when four are waiting on a handoff and two are trapped in a rework loop. Dendro reads your existing local session logs afterward to show where time, handoffs, and budget actually went.

Claude Code OpenAI Codex Gemini / AGY Grok CLI Pi OpenRig Fleets
Why care

Activity is easy to fake. Flow is what ships software.

When you run coding agents across multiple terminals, worktrees, or team roles, you get megabytes of raw logs and very little clarity on what actually moved the work forward.

Without Dendro · The Illusion of Busyness

Terminals scroll fast while work quietly stalls

  • Hidden handoff bottlenecks: An agent finishes a task and sits idle for 45 minutes waiting for a review or human prompt, looking identical to a completed job.
  • Ping-pong rework loops: Two roles pass the same task back and forth four times, burning token budget and context windows without converging.
  • Unattributed spend: Cloud invoices show total token spend, but never which workflow, model choice, or context reset drove the cost.
With Dendro · Retrospective Clarity

Every session read like the rings of a tree

  • Complete time accounting: Every second of an agent's session is separated into active work, waiting on a human, waiting on a peer handoff, stalled with work in queue, or cleanly parked.
  • First-pass vs. rework visibility: See immediately which tasks delivered cleanly on the first pass and where handoffs bounced backward.
  • Local, private, zero-setup: Point Dendro at the session logs already on your disk. Nothing leaves your machine.
What it brings to the table

Three ideas that replace guesswork with evidence.

Dendro is built for engineering leaders, platform architects, and developers who want honest operational feedback rather than AI hype.

01 Busy vs. Productive

Account for every second of the workflow

Instead of counting raw turns or lines of code, Dendro reconstructs the true timeline of every seat—separating active model and tool work from human wait times, peer handoff delays, and stalled queues.

02 The Cost of Rework

Spot ping-pong loops and context resets

When an agent's context window fills up and compacts, or when a reviewer rejects a change three times in a row, costs spike. Dendro highlights exactly where context drops and rework loops happen.

03 Honest Boundaries

Only what local evidence can prove

Dendro never invents "developer hours saved" or subjective code-quality scores. Every chart—in the terminal cockpit, the offline browser explorer, or plain-English queries—is backed by local log facts.

See Dendro in action: explore session timelines, handoff flows, and cost breakdowns in the terminal cockpit or try the interactive Fleet Explorer in your browser →

Built by Samuel Mota · Move the Needle

Why Dendro exists

Open source · MIT · v0.7.0

Value

See where time, handoffs, rework, and budget actually go across your AI coding sessions—using verifiable local evidence instead of vanity productivity claims.

Strategy

Six open terminals look busy even when four agents are stalled on a handoff. Dendro turns raw session history into honest evidence of where time, budget, and rework actually go.

Technical frontier

Reads local session transcripts across six AI coding tools to separate productive work from waiting, handoff delays, and multi-pass rework—in an interactive terminal cockpit or browser report.