CLI
Search, context, history, and validation from a terminal or script.
wordcell context packages/parser/src/index.ts \
--root kb --repo .For coding agents
Keep a Markdown knowledge base beside your repository. Save decisions, tie them to code paths, and let the next agent look them up from the file it edits.
Latest release: v0.24.0 · Free under the MIT license · Exact search needs no account or model.
Get started
You need Bun 1.3.14 or newer and Git. These steps install Wordcell v0.24.0.
bun add --global --ignore-scripts https://github.com/hraness/wordcell/releases/download/v0.24.0/hraness-wordcell-0.24.0.tgz
wordcell --helpbunx skills add hraness/wordcell#v0.24.0 --skill wordcellThe skill gives a compatible agent instructions; it does not run a service. Set up repository memory step by step. See how this release was built and verified.
The workflow
Every step writes or reads plain Markdown. The agent pulls the record when the task needs it.
wordcell init kbCreates a folder of Markdown that any editor can read.
wordcell note create notes/parser-contract --title "Parser contract" --type concept --root kbOne file holds the constraint; frontmatter makes it queryable.
repository_scopes: [packages/parser]The scope lives in the note's own frontmatter, so there is no central table to update.
wordcell context packages/parser/src/index.ts --root kb --repo .Returns scoped notes, related plans, and inherited AGENTS.md rules.
wordcell history notes/parser-contract --root kb --repo .Lists the commits that changed the note.
wordcell context packages/parser/src/index.ts \
--root kb --repo .
wordcell backlinks notes/parser-contract --root kb
wordcell history notes/parser-contract --root kb --repo .Start from the file you are changing. context lists the notes and AGENTS.md guides that apply to it, backlinks shows what links to the note, and history lists the commits that changed it. They print paths and short summaries, and the agent opens a full note when it needs one.
In the vault
Search returns a limited set of results, each with a source the agent can open.
A note lists the repository paths it is about. Starting from the file you are changing, one command returns the notes and plans tied to it and the AGENTS.md guides that apply.
AGENTS.md holds the rules an agent loads on every task. The vault holds the history, evidence, and reasoning behind those rules, and the agent reads it when a task calls for it.
A vault committed with the repository keeps its history. List the commits behind a decision when you need to know how it changed.
A plan wikilinks to the constraint it implements. Backlinks on the decision recover the work that depends on it.
Clip the issue, discussion, or PDF that motivated a decision. The capture keeps a record of where and how it was saved, beside the note.
The TypeScript SDK opens a read-only snapshot of a vault. Build agent or CI workflows on top of it.
Measured
Packed snippets carry what matched, not the whole note. Across four queries on a seven-note public vault, snippets used 80% fewer UTF-8 bytes than the same notes in full.
Payload size, not accuracy; savings depend on your notes and query. Method and raw report.
Oh backs Wordcell’s graph queries and source proofs. Markdown and Git remain authoritative; Wordcell search has its own retrieval path and evidence. How the integration works · Wordcell’s retrieval study.
Interfaces
The CLI is the smallest commitment. The skill teaches an agent the same commands; the SDK embeds them in your tools.
Search, context, history, and validation from a terminal or script.
wordcell context packages/parser/src/index.ts \
--root kb --repo .Open a read-only snapshot of a vault from TypeScript and run searches and workflows against it.
import { openKnowledgeBase } from "@hraness/wordcell/sdk";
const session = await openKnowledgeBase({ root: "kb" });Give your agent instructions for finding and maintaining saved context.
bunx skills add hraness/wordcell#v0.24.0 --skill wordcellTrust
Wordcell records only what you save as notes, and its hosted features stay off until you use them.
Data
Know what stays on your machine and what a connected agent can see.
FAQ
wordcell context starts from a repository path and returns only the notes, plans, and rules scoped to it. Exact and hybrid search cover the cases where you know the words. The agent opens full notes only for the results it needs.
It installs instructions for a compatible agent, such as Claude Code, Codex, Cursor, or GitHub Copilot. It does not start a service, create a vault, or grant access to external accounts.
Yes. Exact search reads any existing Markdown folder without initialization. Repository scopes are optional frontmatter you add where the context is worth recovering.
No. Wordcell stores only what you save as notes. It does not reconstruct private chat or silently record agent actions; Git history is opt-in and covers recorded commits.
Save one decision beside the code, then let the agent find it.
Latest release: v0.24.0 · Free under the MIT license · Exact search needs no account or model.