Markdown memory for coding agents
Give coding agents the decisions behind your code.
Decisions, plans, and sources kept as Markdown beside your repository, one command away from the agent about to change a file. Give the next change the context your repository already recorded.
Latest release: v0.26.0 · Free under the MIT license · Exact search needs no account or model.
- Do we have a rule about parser retries?
- Run commandwordcell search "parser retries" --root kb --mode exact Exact results for “parser retries” (1) 1. 1.000 notes/parser-contract.md:9 — Parser contract [exact#1] --- document_id: 03f883ae-0c6a-4dc8-9168-6bc4c21d3303 type: concept title: Parser contract …
- Yes. notes/parser-contract.md, line 9: “Parser retries stop after three attempts.”
I really like wordcell tbh, gone are the days where i have to send a
handoff.mdto a colleague to get ahandoff.mdfrom them
Wordcell hands the next agent session what this one learned. Decisions, plans, and sources live as Markdown files beside your code. Tie a note to the paths it explains, and an agent about to change that code gets the note first. Search matches exact words or meaning, with an optional local model, and every index rebuilds from files you can read in any editor.
Ask your agent to set it up: wordcell.io
Memory for agents
Your coding agent starts with what you already decided
Tie a note to the paths it explains, and the agent about to change that code gets the note first.
Get started
Save and find your first decision
Installs Wordcell v0.26.0. Get Bun first.
macOS
bun add --global --ignore-scripts https://github.com/hraness/wordcell/releases/download/v0.26.0/hraness-wordcell-0.26.0.tgznpm install --global --ignore-scripts @hraness/wordcell@0.26.0
Linux
bun add --global --ignore-scripts https://github.com/hraness/wordcell/releases/download/v0.26.0/hraness-wordcell-0.26.0.tgznpm install --global --ignore-scripts @hraness/wordcell@0.26.0
Windows
bun add --global --ignore-scripts https://github.com/hraness/wordcell/releases/download/v0.26.0/hraness-wordcell-0.26.0.tgznpm install --global --ignore-scripts @hraness/wordcell@0.26.0
- macOS
- Linux
- Windows
wordcell init kb
wordcell note create notes/parser-contract \
--title "Parser contract" --type concept \
--body "Parser retries stop after three attempts." --root kb
wordcell search "parser retries" --root kb --mode exactNext, follow the first-vault tutorial or search an existing vault.
Connect an agent
Let your agent search and add notes
Paste one prompt into your coding agent; its notes are Markdown you review in Git.
Set up Wordcell as memory you can use between tasks. Keep my decisions, reasoning, and sources in a Markdown vault on my local machine or in persistent project storage. Use your terminal to install and connect it. 1. Install Wordcell unless `wordcell --version` already shows 0.23.0 or later, the first release with `wordcell mcp`. This needs Git and Bun 1.3.14 or later: bun add --global --ignore-scripts https://github.com/hraness/wordcell/releases/download/v0.26.0/hraness-wordcell-0.26.0.tgz wordcell --help 2. Choose a vault that will be available on future tasks. On a local or persistent computer, create one with wordcell init ~/kb. On a disposable session computer, put kb/ in the repository and preserve the notes with the project. Reuse my existing vault when there is one. 3. If your client supports stdio MCP, connect `wordcell mcp --root <vault-absolute-path>` using its setup guide: https://wordcell.io/docs/agent-handoffs. Claude Code: claude mcp add --transport stdio --scope user wordcell -- wordcell mcp --root /absolute/path/to/kb. Codex: codex mcp add wordcell -- wordcell mcp --root /absolute/path/to/kb. Otherwise use the Wordcell CLI directly. 4. If you support skills, install the Wordcell skill: bunx skills add hraness/wordcell#v0.26.0 --skill wordcell 5. Save decisions with their reasons and sources. Before changing related code, search the vault and check the repository context. When I ask you to remember a conversation, follow the skill's session-memory reference.
Show full prompt
Set up Wordcell as memory you can use between tasks. Keep my decisions, reasoning, and sources in a Markdown vault on my local machine or in persistent project storage. Use your terminal to install and connect it. 1. Install Wordcell unless `wordcell --version` already shows 0.23.0 or later, the first release with `wordcell mcp`. This needs Git and Bun 1.3.14 or later: bun add --global --ignore-scripts https://github.com/hraness/wordcell/releases/download/v0.26.0/hraness-wordcell-0.26.0.tgz wordcell --help 2. Choose a vault that will be available on future tasks. On a local or persistent computer, create one with wordcell init ~/kb. On a disposable session computer, put kb/ in the repository and preserve the notes with the project. Reuse my existing vault when there is one. 3. If your client supports stdio MCP, connect `wordcell mcp --root <vault-absolute-path>` using its setup guide: https://wordcell.io/docs/agent-handoffs. Claude Code: claude mcp add --transport stdio --scope user wordcell -- wordcell mcp --root /absolute/path/to/kb. Codex: codex mcp add wordcell -- wordcell mcp --root /absolute/path/to/kb. Otherwise use the Wordcell CLI directly. 4. If you support skills, install the Wordcell skill: bunx skills add hraness/wordcell#v0.26.0 --skill wordcell 5. Save decisions with their reasons and sources. Before changing related code, search the vault and check the repository context. When I ask you to remember a conversation, follow the skill's session-memory reference.
Your agent’s AI provider and optional hosted search ranking can receive selected note content.
Register the MCP server by hand · Move from Supermemory to Wordcell
Capabilities
What a vault gives you
A vault is a folder of Markdown files; Wordcell adds the structure a database would, and the files stay readable in any editor.
Compare
How Wordcell compares
Built for coding agents that need lasting decisions, semantic search, and Git context, in Markdown you control.
| Tool | What Wordcell adds |
|---|---|
| Obsidian | Add semantic search and code context to your Markdown vault. |
| Basic Memory | Find the decisions and rules behind the code you’re changing. |
| Supermemory | Free local memory, with no account or subscription. |
| Mem0 | Keep memories editable and review every change in Git. |
Publish
Publish your notes as a website
Turn selected notes into a static website with navigation, search, and backlinks, built on your machine and hosted where you choose.
wordcell publish --root kb --out site · Read how publishing works
FAQ
Before you install
Is Wordcell only for code?
No. The vault itself is general: notes, captured sources, plans, and research in plain Markdown. The code-related features (repository scopes, AGENTS.md rules, and Git history) apply when the vault sits beside a repository. The developer workflow has its own page.
Can I use my existing Markdown or Obsidian vault?
Yes. Point exact search at your existing directory with --root. You can read and search without initializing or converting the files. Add links and repository scopes as you need them.
Do I need an embedding model or an account?
Not for the quick start. Exact search, backlinks, and publishing need neither. Hybrid and semantic search add an optional local model through QMD. Bun 1.3.14 or newer and Git are required to use the CLI.
Why is it called Wordcell?
The name nods to roon’s essay A Song of Shapes and Words, which split thinking into wordcels, who think in words, and shape rotators. Coding agents are made of words, so Wordcell gives them a library of your notes. Read the essay.
Does publishing upload my whole vault?
No. Choose notes, folders, metadata, or linked neighborhoods, inspect a dry run, then build a local static site. You decide where to upload it. Notes marked publish: false stay out, but review selected text and attachments for private content before sharing.
