Claude Code plugin · self-compounding memory
Knowledge doesn't sit. It compounds.
Cortexes is a personal memory layer for Claude Code. Every session automatically records commits, findings, and decisions, which can later be distilled into refined notes and retrieved with mixed-language search when a request actually points back at prior work. The vault is plain markdown + git as the source of truth; the vector store is just a rebuildable derived index, and search keeps working from a local BM25 index when no embedding key is set. Built for anyone who wants working memory to compound across sessions instead of resetting every time.
Notes don't wait to be asked.
They rewrite themselves.
When a session surfaces something that touches an existing page, broadcast fuses it in place — new sections, corrected assumptions, sharpened caveats. The vault edits itself the way a wiki does, not the way a folder does.
Ask, don't dig
Hybrid retrieval (BM25 + vector) — mixed-language queries hit the right passage directly, without you remembering which file it's in.
Your vault is a living graph,
not a filing cabinet.
Cortexes writes straight into Obsidian vault format — this is the shape wikilinks actually grow into. Try dragging a node.
Skills that trigger themselves
When the user explicitly asks to search the vault ("查 cortex", "之前有記過", "/cortexes:query"), or when using-cortex routes a request here after one of its four signals. Not for general or merely difficult questions.
After a Raw has been distilled, to fuse it into related existing pages ("broadcast", "compound this into the vault"), or auto-dispatched at the end of the distill flow.
When the user wants to distill Raw session records into Notes/Projects ("提煉", "整理 raw", "distill").
When the user wants to save knowledge to the vault ("存到 cortex", "記一下"), or when the session-suggest hook recommends saving.
When context is running low and work needs to hand off to a later session ("交接", "takeoff", "交棒"). Produces temporary hand-off batons — one per work line — that are never committed or indexed. Four signals only — an explicit request, a reference to earlier work ("上次的", "之前那個", "we discussed"), a topic SessionStart actually listed, or resuming a session. Routes those to cortex-query, answers directly otherwise, and stays off once the user picks "直接開始工作".