explaingit

akitaonrails/ai-memory

Analysis updated 2026-05-18

93RustAudience · developerComplexity · 3/5Setup · moderate

TLDR

A Rust MCP server that gives AI coding assistants a persistent, shared Markdown wiki so they remember a project across sessions.

Mindmap

mindmap
  root((ai-memory))
    What it does
      Persistent project wiki
      Cross-session handoff
    Tech stack
      Rust
      Docker
      MCP protocol
      SQLite FTS5
    Features
      Auto-captured sessions
      Full-text search
      Web UI
      Shared across tools
    Use cases
      Resume work in another tool
      Search past decisions
      Run on a home server
    Audience
      Developers using AI agents

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Pick up a task in Codex exactly where you left off in Claude Code

USE CASE 2

Search full project history for a past decision without re-reading old sessions

USE CASE 3

Give a whole team access to one shared project wiki from a home server

USE CASE 4

Browse the auto-generated project wiki in a read-only web interface

What is it built with?

RustDockerMCPSQLite

How does it compare?

akitaonrails/ai-memoryencrypted-spaces/prototypequininer/cbor4ii
Stars939589
LanguageRustRustRust
Last pushed2025-11-30
MaintenanceQuiet
Setup difficultymoderatehardeasy
Complexity3/55/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Runs as a Docker container, needs two setup commands to wire MCP and hooks into your agent CLI.

The README does not state a license.

In plain English

AI coding assistants like Claude Code and Codex have no memory between sessions. When you close a session and open a new one, you have to re-explain the project, the decisions already made, and what was being worked on. ai-memory fixes that by maintaining a persistent wiki for each project, written in plain Markdown and stored in a git repository. Every prompt, tool call, and session boundary is captured automatically without any manual note-taking step. When a session ends, the relevant entries are compiled into coherent narrative pages in the wiki. When the next session starts, whichever AI tool you use next receives a handoff summary showing where things left off, what decisions were made, and what questions remain open. This works across different AI tools: you can stop mid-task in Claude Code and pick up in Codex without re-explaining anything, because both read from the same shared wiki. The server is written in Rust and runs locally via Docker. It exposes an MCP (Model Context Protocol) endpoint that supported AI clients connect to, and it provides a built-in read-only web interface for browsing the wiki in a browser. Full-text search over wiki pages is available both from the agent CLI and from the web UI. No vector database is required, search runs on SQLite with FTS5. Each project's wiki is stored under a path keyed by stable identifiers, so two projects with identically named files never collide. Wiping a project removes only that project's data. The server can also run on a home server or another machine on the network so multiple devices share one memory store, with an optional bearer token for access control. Installation involves running the server as a Docker container and then running two commands that wire the MCP connection and lifecycle hooks into whichever agent CLI you use. The hooks fire automatically on session start and end, so there is nothing extra to do during normal use. The wiki files are plain Markdown, which means they can be opened in any editor, searched with standard tools, and backed up like any other directory. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Set up ai-memory as an MCP server for my project and wire it into Claude Code
Prompt 2
Search the project wiki for why we chose this database schema
Prompt 3
Summarize what was decided in the last session before this one
Prompt 4
Show me the handoff summary for this project so I can continue the task

Frequently asked questions

What is ai-memory?

A Rust MCP server that gives AI coding assistants a persistent, shared Markdown wiki so they remember a project across sessions.

What language is ai-memory written in?

Mainly Rust. The stack also includes Rust, Docker, MCP.

What license does ai-memory use?

The README does not state a license.

How hard is ai-memory to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is ai-memory for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.