akasha

A local knowledge base that gives coding agents a memory, served over MCP.

The problem

Every agent session starts from zero. Yesterday an agent spent an hour working out why a test fails one run in twenty: two tests share a fixture directory and the cleanup of one races the setup of the other. It fixed the test and the session ended. The reasoning lived in a context window, and the window is gone. Today another agent meets the same flake, reads the same files and derives the same answer, spending the same time and context to get there.

What you already know is not missing, it is scattered. Some of it sits in Claude Code project memory, some in Serena memories, some in a notes folder, some in markdown files inside repos. Each agent writes to its own corner, and none of them searches the others. Pasting notes into prompts does not scale: context is the scarce resource, and every pasted page crowds out the work. Conventions ("migrations are reviewed before merge", "never mock the database in integration tests") get retyped at the start of session after session.

Related MCP server: RepoRecall

How akasha fixes it

akasha builds one local index over the markdown you already have. It is read-only by default and copies nothing: your files stay the source of truth, and the SQLite index derived from them can be deleted and rebuilt at any time.

Agents search it through MCP before they start investigating, and write what they find back as ordinary markdown with knowledge_write and knowledge_append. The next session starts where the last one ended. Search is keyword (BM25) and, if enabled, dense retrieval, fused by reciprocal rank. Results are sized for a context window: a handful of capped hits, with knowledge_get to page into a document only when one is worth reading.

Conventions are documents of kind=convention. They are delivered automatically at session start and are read-only to agents; only the CLI can create or change one. Hooks keep the index fresh without anyone thinking about it (in Claude Code and Gemini CLI): a session-start hook refreshes it in the background, and a post-tool hook reindexes a note the moment an agent edits it.

Safety is enforced where the data enters. At index time, secret-shaped strings are redacted and known prompt-injection patterns are neutralised before any agent sees the text. Both are pattern-based: they catch the common shapes, not every secret. Destructive operations are CLI-only; an agent can archive a document, never delete one. There is no account and no server, and nothing leaves your machine (the one exception is a small embedding model, downloaded once if dense search is on).

A day with akasha: an agent running in claude records the flaky-test cause with knowledge_write. The next morning an agent in gemini is asked about the same flake, calls knowledge_search first, and finds the finding in one hit instead of an hour of investigation.

Requirements

• Python 3.11+ and uv

• A supported agent CLI: claude, gemini or copilot. akasha init --all registers with whichever are on your PATH. Any other MCP client can run akasha serve (stdio) by hand.

Install

The PyPI package is akasha-mcp; the command it installs is akasha.

uv tool install --python 3.12 'akasha-mcp[vectors]'

--python matters when your default Python is older than 3.11 (macOS ships 3.9): uv does not pick an interpreter from the package's requirement on its own, and downloads 3.12 if you don't have it. Without dense search: uv tool install --python 3.12 akasha-mcp. From git:

uv tool install --python 3.12 'akasha-mcp[vectors] @ git+https://github.com/anuress/akasha'

With [vectors] installed, akasha init writes provider = "model2vec" and search is dense plus keyword. Without it, search is keyword-only: init says so and akasha doctor keeps saying so. akasha config set embeddings.provider none turns dense search off. An existing config is never rewritten; to enable it there, set embeddings.provider model2vec and run akasha index.

Quickstart

akasha init

Creates ~/.akasha/ (mode 0700) with config.toml, the SQLite index and a knowledge/ directory for documents agents write. On first run it looks for existing notes to index: Claude Code project memories (~/.claude/projects/*/memory), and .serena/memories and graphify-out directories in the immediate subdirectories of ~ (change with --code-root DIR, repeatable).

akasha init --all

Registers the MCP server with every detected agent CLI through that CLI's own mcp add command (copilot: its mcp-config.json), and installs the two hooks for claude and gemini. For claude it also allows the mcp__akasha tools in settings.json so they do not prompt; skip that with --no-allow. --dry-run prints what would be written and changes nothing.

akasha index                         # build or refresh the index
akasha knowledge search "cache expiry" --limit 3
akasha doctor                        # what is degraded; exit 0 means healthy

Search defaults to the repo of the current checkout; --all searches every repo.

Tools

Eleven MCP tools:

Hooks

Two hooks, both fail-open (they never block a session or a tool):

• akasha hook session-start prints the repo's conventions, a short brief and an integrity note into the new session. The installed command passes --defer-refresh so it does not wait for an index walk.

• akasha hook post-tool reads the tool payload on stdin and reindexes the one file an agent just wrote, if it is inside an index root.

Documents of kind=convention are standing rules: they are injected at session start and are read-only over MCP. Only the CLI can create or change one.

Sources and config

The native knowledge directory (~/.akasha/knowledge) holds documents written through akasha. Everything else is an indexed root, one [[index]] block in config.toml:

[[index]]
path     = "~/notes"
source   = "notes"
include  = ["**/*.md"]      # optional globs
exclude  = ["**/cache/**"]
repo     = "my-repo"        # repo the whole root belongs to
writable = false            # default; true lets knowledge_append write into it

Roots are read-only by default. Add one without editing the file:

akasha index add ~/notes --source notes --repo my-repo
akasha index

Deleting things

Agents can only archive. Everything else is CLI-only.

Rebuilding and ids

The database is derived from the files:

rm ~/.akasha/akasha.db && akasha index

Ids of documents in indexed roots are derived from root and relative path, so links between documents survive a rebuild. Moving or renaming a file changes its id.

Privacy

At index time, secrets are redacted (scan_secrets, on by default) and prompt-injection shapes are neutralised before text reaches an agent; common secret files (.env*, *.pem, *.key, *.pfx, *.kdbx, SSH keys, .npmrc, .pypirc, credentials.json and similar) are denied outright; deny_files and deny_extensions in [security] replace the lists. A local audit log of events, including redacted query heads, is kept for 90 days (akasha housekeeping prunes it).

Development

uv run pytest -q
uv run --python 3.11 pytest -q

License

MIT