ai-memory: 24 Agents, One Memory, and the Four Harnesses That Silently Drop the Handoff

Tue, 20 Oct 2026 00:00:00 +0000

The pitch is a single sentence, and it is a good sentence: “Quit Claude Code mid-task, start OpenAI Codex in the same directory, continue without re-explaining the architecture, the failed approaches, or the open questions.”

That is the promise of ai-memory, a Rust project by Fabio Akita (akitaonrails). It is not a small promise. It says the boundary between agent vendors — the one every team hits when a subscription runs out, a rate limit lands, or a model gets worse — is a solved problem, because the memory lives in your server instead of inside one vendor’s client.

This article is not a review of whether that promise feels true. It is an attempt to measure it, using the document the project publishes about itself: docs/support-matrix.md. That file is unusual. It is a per-agent table where the maintainers wrote down, harness by harness, exactly which lifecycle event fires, which one discards stdout, which one needs a rules file taped to it, and which one has never been run end to end. It is the most honest integration table I have read in this category, and it is also the document that most sharply limits the headline.

Cross-Vendor Handoff on SoloSoft

ai-memory: 24 Agents, One Memory, and the Four Harnesses That Silently Drop the Handoff