Capture continuously
A supervised, event-driven stream follows complete local transcript appends. Durable byte cursors resume without rescanning settled history.
Local-first agent memory
Transcript Lake turns conversations from Claude Code, Codex, OMP, Droid, Kimi, and Tama hooks into one privacy-masked local archive—while they happen.
Why Transcript Lake
A supervised, event-driven stream follows complete local transcript appends. Durable byte cursors resume without rescanning settled history.
Credential-shaped and high-entropy text is replaced before an event reaches the canonical partition or any downstream projection.
Provider-neutral events make sessions, tools, tokens, hook decisions, labels, and cross-runtime signals available through DuckDB.
Vendor stores remain read-only. NDJSON stays authoritative. Parquet and Oko projections are explicit, rebuildable derived state.
A narrow trust boundary
Transcript Lake gives every downstream consumer the same normalized evidence without making each one handle raw vendor files, secrets, or incompatible schemas.
Read the masking guarantees$ transcript-lake stream stream start roots=6 adapter runtime=claude complete_lines=7 mask assignments=2 tokens=1 entropy=1 commit files=1 failures=0 ms=50 cursor durable offset=14592
Documentation
Explore 42 complete guides, references, concepts, and executable examples covering the full development-channel contract.
Browse all documentation