What I built

Biblio is a local-first context system for long-running Codex projects. It keeps the important decisions, source evidence, and unresolved questions from getting lost when a conversation gets large, gets handed off, or is compacted.

I built it because a summary is not always enough. When a project spans many sessions, I want to be able to ask “why did we choose this?” and get the answer together with the original evidence, not just a confident-sounding rewrite.

How it works

Biblio has three parts:

  • A local bridge and Codex skill for snapshot, retrieval, handoff, compaction recovery, provenance, import/export, and verification.
  • A shared schema and deterministic context engine that stores append-only rollout segments and derives source-linked memories.
  • An Obsidian plugin that makes the data readable and reviewable through timeline, decision graph, context, provenance, contradiction, confidence, budget, and integrity views.

The system is local-first and redacts common secrets before they reach derived memories or exports. Every derived memory keeps links back to its source segments and checksums. The retrieval output is token-budgeted and explains why each item was selected.

What is demonstrated

The included synthetic demo starts with a recent-window context failure, then recovers the missing decision from historical rollout evidence. The repository also includes a clean-install proof, isolated installation smoke tests, a full test suite, and a live Obsidian runtime report with screenshots.

How I used Codex and GPT-5.6

I used Codex throughout the build for architecture research, implementation, integration, documentation, test design, and validation. Codex helped me work across the TypeScript engine, CLI bridge, Codex skill, shared schemas, and Obsidian plugin while keeping the pieces consistent.

GPT-5.6 and Codex were used to iterate on the design, make engineering decisions, find edge cases, and turn the initial idea into a working end-to-end project. The dated development log in the repository records the major decisions, fixes, and validation evidence.

Try it

The source code and step-by-step testing instructions are available here:

https://github.com/so-nerdyy/Biblio

The repository includes sample data and a prebuilt plugin bundle. It also explains the Node.js, npm, Obsidian, and Codex requirements, along with the limitations of the current local-only implementation.

Limitations

Biblio is intentionally local-first. It does not provide remote sync, multi-user conflict resolution, or a hosted service, and automatic capture requires the user to review and enable the supplied Codex hooks.

Built With

Share this project:

Updates