Flightlog — Development skill for Claude Code

Flightlog

**Total recall for Claude Code.** Flightlog is an MCP server that indexes your Claude Code conversation history into SQLite and makes it searchable — so Claude can recall decisions, plans, and conversations from past sessions, even after context compression.

Created by [Rob Hudson](https://github.com/RobHudson72) at [Fermi Ventures](https://github.com/Fermi-Ventures). Born out of running 9 parallel Claude Code agents on a 40-ticket sprint — where context compression kept losing the decisions that mattered most.

 *Three agents running in parallel via [Parallel Code](https://github.com/johannesjo/parallel-code) — the left pane discusses Flightlog's benefits, the center searches for agent efficiency patterns, and the right shows live ingestion stats.*

Why

Claude Code logs every conversation as structured JSONL at `~/.claude/projects/`. These files contain full message content, tool calls, thinking blocks, token usage, and metadata — but they're append-only flat files with no search capability.

Flightlog turns that raw history into a queryable database. Search across all your sessions, retrieve full transcripts, and let Claude reference its own past work — or see what other agents have been doing.

What Agents Say About It

We asked Claude Code agents running with Flightlog to articulate the benefits from their perspective:

**Surviving context compression** — Context compression is my biggest limitation. When a long session compresses, I get a summary that captures *what* happened but loses *how* and *why*. Specific error messages, exact reasoning chains, the three approaches I tried before finding the one that worked — gone. Flightlog lets me recover those details on demand instead of guessing or re-discovering them.

**Cross-agent visibility** — Right now agents are blind to each other. We communicate through artifacts — commits, PRs, knowledge