Hacker News front pageJul 22, 2026, 01:12 UTC+8

CodeAlmanac turns your Claude Code chats into a queryable, auto-updating codebase wiki

Show HN: CodeAlmanac – Karpathy-style codebase wiki from your conversations

CodeAlmanac keeps an almanac/ folder in your repo with Markdown pages for decisions and context that code alone doesn't capture. Every five hours it pulls new CC/Codex conversations and updates the relevant pages, then indexes them in SQLite for CLI queries. Each teammate's agent searches the wiki before coding, so you stop re-explaining design intent. It's open-source, local, and free; the post doesn't disclose token costs or latency figures.

Why it matters: Auto-maintained codebase wiki from CC/Codex conversations, pulling design intent every 5h into Markdown that agents query before acting. Concrete mechanism, real pain point, but brand-new with no usage data — lands at 72, right at the featured threshold.

Read the original ↗Export Markdown

Take

This caught my eye because it nails a specific pain point: you hash out design decisions with Claude Code, your teammate's agent has no clue, and you end up re-explaining everything. CodeAlmanac keeps an almanac/ folder in your repo, pulls new conversations every five hours, updates relevant Markdown pages, and indexes them in SQLite for CLI queries. Teammates' agents search the wiki before they start coding.

It's open-source, runs locally, and uses your existing Codex or Claude Code subscription. The five-hour trigger instead of per-commit is a practical call to keep token costs down—I respect that.

Only 6 HN points and 3 comments so far, and the post doesn't disclose token consumption or latency. I'd treat this as a proof-of-concept for team context management, not a turnkey cost-saver. If you're already manually maintaining AGENTS.md or CLAUDE.md, the direction is worth watching, but you'll need to run it yourself to see actual usage costs.

Source: Hacker News front page · github.com
Published: Jul 22, 2026, 01:12 UTC+8 · Jul 22, 2026