Extract entities
Frontmatter tags, inline hashtags, wiki links, folders, and dates become signals.
A cofactor for agent memory
Compile your Markdown vault into a local concept graph. Tags, folders, links, and timestamps become catalyst-style questions your agent can search before the first conversation.
npm install -g cofactor-memory
Most memory layers start empty
Your notes already have structure: repeated tags, dormant links, folders that carry projects, and timestamps that show when ideas changed. Cofactor reads those signals and gives agents a retrieval layer grounded in the shape of your archive.
Setup
$ cd ~/notes
$ cofactor init
Indexed: 384 documents
Entities: 42 tags, links, and folders
Catalysts: 168 generated locally
Chunks: 611 searchable passages
$ cofactor catalyze "why did auth change direction?"
matched catalyst · #architecture
"Where does session recovery keep colliding with shipping pressure?"
→ retros/platform-auth.md
→ adrs/session-boundary.md
→ interviews/user-12.md
Compile step
Frontmatter tags, inline hashtags, wiki links, folders, and dates become signals.
Each salient entity gets thematic questions built from local terms and activity.
Catalysts are matched against BGE embeddings so query time can reuse stored structure.
Your agent asks a question and receives excerpts, catalyst IDs, and file paths.
Local by default
Bring a corpus
ADRs, retros, incident reviews, and planning docs become searchable context.
Highlights and research notes surface recurring tastes, tensions, and questions.
Chosen and rejected options reveal the constraints a user keeps returning to.
Apply a team’s catalysts to docs, transcripts, and unfamiliar project material.
Agents
Cofactor is available as the cofactor-memory package. Use the CLI directly,
import the TypeScript SDK, or run the included stdio MCP server for clients that speak
Model Context Protocol.
cofactor agents codex .
cofactor agents claude .
cofactor mcp ./notes
Try it on your own vault