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.
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
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 your coding agent
Your coding agent starts with what you already decided
Give the next session the reasons behind your code. Wordcell connects decisions to their evidence and the plans that use them, in Markdown your agent can find and update.
Before changing a file, your agent can recover the decisions, active plans, and AGENTS.md rules tied to that path. Local semantic search helps it find a note in different words; Git history shows how the reasoning changed with the code.
Keep sources, current understanding, and ongoing work connected. When an assumption changes, revise the decision and leave the evidence for the next session. Use your existing agent and editor through the CLI, local MCP server, or TypeScript SDK.
Choose your tools
How Wordcell compares
Built for coding agents that need lasting decisions, semantic search, and Git context. All in Markdown you control.
How it looks
Your agent finds the rule and names the file
The same note, found three ways. Pick one to see the command and what comes back.
- 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.”
Get started
Save and find your first decision
You need Bun 1.3.14 or newer and Git. These steps install Wordcell v0.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 kbwordcell search "parser retries" --root kb --mode exactNext, follow the first-vault tutorial or search an existing vault or connect a coding agent.
Agent memory
Let your agent search and add notes
Connect your coding agent to the vault. Every note it adds is Markdown you can 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.
Claude Code
claude mcp add --transport stdio --scope user wordcell -- wordcell mcp --root /absolute/path/to/kbCodex
codex mcp add wordcell -- wordcell mcp --root /absolute/path/to/kbCursor
~/.cursor/mcp.json{
"mcpServers": {
"wordcell": {
"command": "wordcell",
"args": [
"mcp",
"--root",
"/absolute/path/to/kb"
]
}
}
}Gemini CLI
gemini mcp add --scope user wordcell wordcell mcp -- --root /absolute/path/to/kbGitHub Copilot
.vscode/mcp.json{
"servers": {
"wordcell": {
"type": "stdio",
"command": "wordcell",
"args": [
"mcp",
"--root",
"/absolute/path/to/kb"
]
}
}
}For manual setup, replace /absolute/path/to/kb with your vault’s absolute path.
Capabilities
What a vault gives you
A vault is a folder of Markdown files. Wordcell adds the structure a database would provide, and the files stay readable in any editor.
Files you own
Notes stay plain Markdown. Read them in any editor, review changes in Git, and rebuild every index from the files.
Find a past decision
Search by exact words without a model or account. Add an optional local model to search by meaning, and follow named links between notes.
Context for the file at hand
Tie notes to repository paths. Starting from a file, get the related notes, plans, and AGENTS.md rules before the next edit.
Sources you can reopen
Save a web page or PDF as Markdown with its assets and capture details. Keep the source beside the decision it informed.
Publish
Publish your notes as a website
Turn your Markdown notes into a readable website with navigation, search, and backlinks. Build static files locally, then host them where you choose.
Local by default
The record stays yours
- Your Markdown is the record
- Your notes stay in plain files you can read, edit, and keep using without Wordcell.
- What can leave your machine
- Local search needs no account. Your agent’s AI provider and optional hosted search ranking can receive selected note content.
- Sources stay inspectable
- Open the note, authored link, or commit behind a result.
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.
Give the next session what this one learned.
Save one decision beside the code, then let the agent find it.
Latest release: v0.26.0 · Free under the MIT license · Exact search needs no account or model.