Now available for Claude Code

AI reads your code.
Not the story behind it.

A living wiki for your codebase, maintained by AI agents. Decisions, flows, invariants, and gotchas — captured automatically, organized by topic, interlinked by wikilinks.

Set up in 30 seconds

See what your agent sees

Every page is a markdown file your agent can read, search, and link to

.almanac/supabase-over-firebase.md

# Why Supabase over Firebase

topics: auth, infrastructure · type: decision

Firebase was the default choice, but RLS policies

let us enforce row-level access without a custom

middleware layer. The Postgres foundation also means

we can use raw SQL for complex reporting queries

that Firestore can't express.

## Gotchas

! Token refresh race on parallel requests — see [[token-mutex]]

! CORS middleware must run before auth — see [[cors-ordering]]

## Related

[[api-rate-limiting]] · [[rls-policies]] · [[auth-flow]]

Three steps. Zero config.

codealmanac hooks into your existing workflow. Nothing changes except your agent gets a wiki.

Setup

Run npx codealmanac. The wizard checks auth, installs a SessionEnd hook, and drops agent guides into your config. Then almanac bootstrap seeds your first pages.

Work normally

Use Claude Code as usual. When your session ends, a writer agent reads the transcript, drafts wiki pages, and a reviewer agent QAs them. Pages land in git status.

Wiki compounds

Every session adds knowledge. Pages interlink via [[wikilinks]], topics organize into a DAG, and your agent starts each session with the full story behind your code.

Built for developers who ship

◇

Living wiki, not a flat file

Atomic markdown pages with [[wikilinks]], organized by a topic DAG. Not a single CLAUDE.md that gets stale and unwieldy.

◈

Agent-written, agent-reviewed

Writer and reviewer agent pairs draft and QA every page. Encyclopedia-quality prose, not raw session dumps.

▣

Auto-capture at session end

A SessionEnd hook backgrounds almanac capture. Your wiki grows after every coding session without you lifting a finger.

◆

Four page shapes

Entity, Decision, Flow, Gotcha. Each captures a different kind of knowledge your code can’t express on its own.

○

Multi-wiki, cross-linked

Each repo gets its own .almanac/ directory. Cross-wiki references with [[project:slug]]. A global registry tracks everything.

▸

One command setup

npx codealmanac — interactive wizard, idempotent, installs hooks and agent guides automatically. Set up in 30 seconds.

You've tried workarounds

codealmanac isn't docs or a RAG pipeline. It's a structured wiki that captures why your code is shaped the way it is.

CLAUDE.mdSingle flat file, manual upkeep, gets stale fast

Model memoryProvider-locked, session-scoped, no structure

README / docsWritten once, never updated, nobody reads them

Slack threadsKnowledge trapped in chat, invisible to agents

codealmanacStructured wiki, auto-maintained by agents, cross-linked, grows every session

Simple CLI, powerful brain

almanac bootstrapSeed stub pages and topic DAG from your codebase

almanac searchFind pages by keyword across the wiki

almanac showRead a page with full wikilink resolution

almanac healthCheck wiki coverage, stale pages, broken links

almanac captureWrite new pages from the latest AI session

almanac topicsBrowse and manage the topic DAG

almanac doctorVerify setup, hooks, and authentication

Questions

Give your codebase a wiki

One command. Agent-maintained. Free forever.

AI reads your code.Not the story behind it.