Pick up a task in Codex exactly where you left off in Claude Code
Search full project history for a past decision without re-reading old sessions
Give a whole team access to one shared project wiki from a home server
Browse the auto-generated project wiki in a read-only web interface
| akitaonrails/ai-memory | encrypted-spaces/prototype | quininer/cbor4ii | |
|---|---|---|---|
| Stars | 93 | 95 | 89 |
| Language | Rust | Rust | Rust |
| Last pushed | — | — | 2025-11-30 |
| Maintenance | — | — | Quiet |
| Setup difficulty | moderate | hard | easy |
| Complexity | 3/5 | 5/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Runs as a Docker container, needs two setup commands to wire MCP and hooks into your agent CLI.
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.
A Rust MCP server that gives AI coding assistants a persistent, shared Markdown wiki so they remember a project across sessions.
Mainly Rust. The stack also includes Rust, Docker, MCP.
The README does not state a license.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.