Logpile
local-first · Claude Code + Codex

Agents do the work. Logpile keeps the record.

Every session your coding agents run is work product — and it's sitting in JSONL files you'll never open. Logpile indexes all of it into a searchable local archive: transcripts you can read, filter by what they did, and publish with secret scanning.

$ git clone https://github.com/MaxGhenis/logpile && cd logpile $ ./logpile.sh sync && ./logpile.sh serve

Local-first. Nothing leaves your machine unless you publish it. MIT-licensed.

25,686 sessions · 1.01B output tokens · 917 repo checkouts — the author's index, as of Jul 11, 2026.

The record — 14 dayslive index · Jul 11, 2026
2026-07-11 40M out 557 sessions
2026-07-10 40M out 766 sessions
2026-07-09 11M out 404 sessions
2026-07-08 15M out 395 sessions
2026-07-07 15M out 238 sessions
2026-07-06 13M out 333 sessions
2026-07-05 17M out 444 sessions
2026-07-04 6M out 175 sessions
2026-07-03 5M out 81 sessions
2026-07-02 8M out 155 sessions
2026-07-01 6M out 159 sessions
2026-06-30 4M out 61 sessions
2026-06-29 2M out 54 sessions
2026-06-28 2M out 48 sessions

01 · keepEvery session, indexed

One command turns the session files Claude Code and Codex leave on disk into a SQLite archive — with token accounting that dedups Codex fork replays and cross-file resumes, so the numbers are right.

02 · readTranscripts, not log soup

Sessions render as readable transcripts you can search and filter by what they actually did — wrote files, ran tests, committed — and by origin: your work vs. delegated agents vs. pipelines.

03 · publishProof, when you choose

A review queue scans every transcript for secrets and PII before it can go public. Published sessions build an operator profile: the receipts for how you actually work with agents.