sessions

My coding history is spread across tools and does not stay around forever. I built Sessions to keep a local copy that I can search and inspect later.

Sessions reads provider history without changing it, normalizes each session into a local SQLite library, and keeps the retained copy even if the source later changes or disappears.

Check the code on GitHub

What it does

• Keep. sessions index --source codex copies normalized Codex history into a durable local library. Indexing is explicit, incremental, and safe to run again.
• Find. list, search, entries, and show provide filters, bounded context, and provenance. Search keeps copied or forked text from looking like separate evidence.
• Export. Any retained session can be exported as JSON or JSONL without reopening the provider files.
• Analyze. The packaged Sessions skill uses the CLI for context recovery, retrospectives, workflow and verification audits, handoff checks, and finding repeated work worth turning into a reusable tool.

Local by default

Core commands use no network or telemetry. Provider histories stay read-only, and transcripts remain on the machine. forget, repair, compaction, and clear commands only change Sessions-owned data.