Skip to content
aicoolies logo
ai-memory logo

ai-memory

Shared, git-backed long-term memory and handoffs for AI coding agents

Open-source (MIT) long-term memory server for AI coding agents by Fabio Akita. Lifecycle hooks capture sessions from Claude Code, Codex, Cursor, Gemini CLI, OpenCode and many other coding agents into a git-backed markdown wiki, so you can quit one agent mid-task and continue in another with a typed handoff. One self-hosted Rust binary; default features need no LLM API key and it has no telemetry.

About ai-memory

ai-memory is an open-source memory layer that sits outside your coding agents. Lifecycle hooks and MCP registration record what happens in a session (prompts, tool calls, session boundaries), sanitize it at a privacy boundary and consolidate it into readable markdown pages in a per-project wiki. The next session, in any supported agent and on any machine, gets a bounded brief and can search earlier work with full-text, entity and link search, optionally fused with vector search.

Its headline feature is cross-agent handoff. Quit Claude Code mid-task, open Codex in the same directory, and the next agent receives a handoff describing where you stopped, what failed and what is still open; handoffs are a typed protocol with an owner and are claimed exactly once. Starting agents through ai-memory run can also pass a temporary local projection of the previous agent's visible session history. A small cross-project profile carries habits such as your package manager and test layout into new repositories.

The source of truth is a git-backed wiki of ordinary .md files that you can grep, open in Obsidian or edit by hand; the database is a derived index that can be rebuilt. Memory ages on a tunable schedule without an LLM, and optional compaction, deduplication and an opt-in LLM "dream" pass that merges cold notes are off by default. For teams, one server provides shared per-project knowledge with multi-user auth, per-person attribution and an audit log, which the README says are not a paid tier.

ai-memory ships as one self-contained Rust binary for Linux and macOS (Windows via WSL2; native Windows is experimental), with install scripts that verify SHA-256 checksums, a Claude Code plugin, AUR/RPM packages, a macOS app and a Docker image. It is free and MIT-licensed; you run the server yourself, and optional cloud model or embedding providers bill under your own accounts. A default install listens only on 127.0.0.1 and, per the project's security page, has no analytics, crash reporting or usage tracking.

Pricing & Platform Specs

Pricing Summary

ai-memory is free and open source under the MIT license. You self-host the server on your own machine or infrastructure; team features such as multi-user auth and audit logs are included, not a paid tier. Optional LLM or embedding providers are billed by those providers.

Supported Platforms

Self-hosted Rust binary for Linux and macOS (NixOS module, AUR/RPM packages, macOS app, Docker image); Windows via WSL2, native Windows experimental; integrates with Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Devin CLI and many other agents via hooks and MCP

Explore categories, tags & use cases

Open-source, cross-harness session history and self-improving memory for coding agents

Beacon by Asymptote Labs is an MIT-licensed memory and telemetry layer for AI coding agents. It captures sessions from Claude Code, Cursor, Codex, OpenCode, Cline and 20+ other harnesses into one OpenTelemetry-based trace format, then turns reviewed workflows, corrections and debugging patterns into skills and MCP memory that any agent can reuse. Self-host the open-source stack for free, or use Beacon Cloud (free tier; Cloud Pro $20/month, or $15/month billed annually).

freemiumOpen Source

Side-by-Side Comparisons

ai-memory logo
ai-memory
vs
Beacon logo (Asymptote Labs)
Beacon

ai-memory vs Beacon: Self-Hosted Agent Memory or Cross-Harness Trace and Memory Layer?

ai-memory and Beacon both give AI coding agents a memory that outlives a single session and a single tool, and both are MIT-licensed. They start from different places. ai-memory, by Fabio Akita, keeps memory as a git-backed markdown wiki on a server you run and hands work explicitly from one agent to the next. Beacon, by Asymptote Labs, records full session traces from more than 20 harnesses and turns them into findings, skills and memory, with an optional paid cloud. This comparison is based on each project's README, website and pricing page, checked on October 21, 2026; we did not run our own tests.

ai-memoryBeacon

Community experience

Sources & verification

Sources checked
Content verified

Verification dates are editorial checks. Routine CMS saves and automatic updatedAt timestamps do not advance them.

FAQ

What is ai-memory?

Open-source (MIT) long-term memory server for AI coding agents by Fabio Akita. Lifecycle hooks capture sessions from Claude Code, Codex, Cursor, Gemini CLI, OpenCode and many other coding agents into a git-backed markdown wiki, so you can quit one agent mid-task and continue in another with a typed handoff. One self-hosted Rust binary; default features need no LLM API key and it has no telemetry.

Is ai-memory free?

Yes — ai-memory is open source and free to use. ai-memory is free and open source under the MIT license. You self-host the server on your own machine or infrastructure; team features such as multi-user auth and audit logs are included, not a paid tier. Optional LLM or embedding providers are billed by those providers.

Is ai-memory open source?

Yes — ai-memory is open source.

Is ai-memory still maintained?

Yes — ai-memory is active. Its listing was last verified on October 20, 2026.

What are the best ai-memory alternatives?

The first editor-selected ai-memory alternatives are Beacon.