deadreckon
observability · 13

Watching it work

Attach from any terminal for a live TUI, a rolling narration, and a flight recorder that lets you rewind to any checkpoint.

maps to as-built §18§27§32§33

never a black box · watch it, narrate it, rewind it
Three ways to see a run while it runs At the center, a running run writes durable append-only streams: events, spend, traces, flight-events, narrative snapshots, and per-turn checkpoints. Three surfaces read them. attach is the live TUI you open from any terminal, showing header, spend, context, and acceptance meters while tailing the streams. The live narrator turns the run into one rolling plain-English story, written live and shown in the foreground, headless, or inside attach. The flight recorder takes a checkpoint around every turn, so rewind can roll the working tree back to any turn or checkpoint. A RUNNING RUN writes durable streams: events · spend · traces flight-events · snapshots checkpoints/ append-only · always-on attach: the live TUI header · spend · context · acceptancetails the streams from any terminal live narrator: one rolling story plain-English beats, written liveforeground · headless · in attach flight recorder + rewind a checkpoint around every turnrewind --to-turn / --to-checkpoint
The render path never blocks on a model: it only tails files the run already wrote. Observation is free and always-on.

A run you can't see is a run you can't trust. deadreckon writes durable, append-only streams as it works (events, spend, traces, flight events, narrative snapshots, and per-turn checkpoints), and three surfaces read them.

attach: the live TUI

deadreckon attach opens a terminal UI from any shell, on any machine that shares the state directory. It shows header, spend, context, and acceptance meters and a streaming activity pane. The render path is strict: it only tails files, never calls a model, so it stays responsive.

the live narrator: one rolling story

Instead of raw tool lines, the live narrator keeps one plain-English story, updated turn by turn, at a capped cost. It shows in the foreground while you watch a run, prints as plain text lines when the run is unattended, or appears inside attach --view narrative. With no AI provider configured it falls back to a simple built-in summary, so narration always works.

the flight recorder & rewind

For CLI providers, the flight recorder captures a checkpoint around every turn into flight-events.jsonl and checkpoints/. deadreckon rewind --to-turn N (or --to-checkpoint) shows a preview first, then rolls back only the files that turn changed and leaves your own edits alone: undo at the level of a single turn.

source