Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

Fix stale Windows support claims and 3.0 unreleased label in comparison docs

Ryan Vo7cda5ed614b0
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 59954396..e4ad050f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -11,6 +11,13 @@ version in [`docs/changelog/`](docs/changelog/):
## [Unreleased]
+### Fixed
+- Corrected stale claims in `docs/comparison.md` and `docs/competitive-parity.md`
+ that said Windows has no service step and the Windows install is experimental.
+ The 3.1 `install.ps1` + `setup` Windows service step is shipped production,
+ not experimental; the "3.0 (unreleased)" observation-stream note is corrected
+ to reflect the released 3.0 line. (#1271)
+
## [3.1.0] - 2026-10-16
### Added
diff --git a/docs/comparison.md b/docs/comparison.md
index e18a9cb6..3211b3d9 100644
--- a/docs/comparison.md
+++ b/docs/comparison.md
@@ -53,7 +53,7 @@ It also publishes retrieval numbers, produced by the in-repo harness with full
provenance and measured end to end through the shipped capture pipeline:
LongMemEval-S hit@5 **0.666** zero-LLM and **0.815** with the default local
embeddings in the published 2.6 line. The observation stream in 3.0
-(unreleased, on by default) raises zero-LLM to **0.951** and local embeddings
+(on by default) raises zero-LLM to **0.951** and local embeddings
to **0.945** on all 470 questions, measured on one build with the stream off
and on. With capture skipped and each raw session indexed whole (component
mode, ranking only), zero-LLM FTS scores 0.972; the
@@ -253,10 +253,10 @@ ships something ai-memory does not, it is named.
`/admin/metrics` instead), the coordination tools (leases, actions,
routines, signals, sentinels), mesh sync (the nearest equivalent is the
git-based `ai-memory-wikisync` companion), image memory, the two-way Claude
- `MEMORY.md` bridge, PaaS deploy templates, an npm package (ai-memory 3.0
- installs natively on Linux and macOS in two commands, `install.sh` and then
- `ai-memory setup`, but has no `npx` route, and Windows gets no service
- step), and the opt-in local cross-encoder reranker. The benchmark numbers are not
+ `MEMORY.md` bridge, PaaS deploy templates, an npm package (ai-memory installs
+ natively on Linux, macOS and Windows in two commands — `install.sh`/
+ `install.ps1` then `ai-memory setup` — but has no `npx` route), and the
+ opt-in local cross-encoder reranker. The benchmark numbers are not
like-for-like (component vs pipeline, see above). To move your data, the
`ai-memory-importer` companion (3.0) reads agentmemory's Obsidian vault
(`agentmemory-vault`) or its `ExportData` JSON (`agentmemory-export`), and
@@ -389,9 +389,10 @@ ships something ai-memory does not, it is named.
not from a plugin marketplace.
- **An installer that detects and wires every agent.** `ai-memory setup`
(3.0) wires MCP, hooks and Agent Skills for each detected agent on Linux and
- macOS. Hindsight's coding-agent package covers 16+ agents, and memU's
- `memu-agent detect` finds unknown agents' transcripts. Windows has no
- service step yet.
+ macOS; 3.1 brought the same two-command install and a per-user service step to
+ Windows (`install.ps1` + a logon entry that starts `ai-memory service-host`).
+ Hindsight's coding-agent package covers 16+ agents, and memU's `memu-agent
+ detect` finds unknown agents' transcripts.
- **No end-to-end QA number.** We publish retrieval hit@5; Mem0, Zep,
Hindsight and EverOS publish end-to-end QA accuracy with a reader and a
judge model. Our opt-in `answer=true` synthesis (2.4) has only an early,
diff --git a/docs/competitive-parity.md b/docs/competitive-parity.md
index 46721c4c..36daed1c 100644
--- a/docs/competitive-parity.md
+++ b/docs/competitive-parity.md
@@ -66,7 +66,7 @@ coding-agent competitors as well as in their original camps.
| **MemPalace** (hook capture, team server) | **Partly**: overlapping goals, different substrate | Git-markdown truth, claim-once handoffs, typed cross-project messaging, the auth ladder | Its temporal graph and team server as shipped. Its 96.6% / 98.4% R@5 is retrieval-only like our hit@5, but on a different harness, so neither number ranks the tools |
| **mcp-memory-service** (fact rows + hook capture) | **Yes** if you liked hook capture + typed edges + published numbers | Files-as-truth (not opaque fact rows), handoffs, cross-project messaging, `as_of` temporal, a reproducible number, and (new on 2.4) its aging set at parity done zero-LLM/reversible/off-by-default (per-tier decay curves, extractive compression, DBSCAN cold-cluster dedup, access boosts, 0.4–0.75-band contradiction flagging) | Cloud/multi-backend replication (Cloudflare/Milvus), graph viz. (Belief-strength + clustering consolidation are no longer a give-up: ai-memory now ships both, clustering as a zero-LLM default-off pass, belief-strength off and eval-gated) |
| **basic-memory** (file-first markdown) | **Yes** for multi-harness coding continuity; **no** for a personal Obsidian KB with live team co-edit | Ambient capture (no `write_note` ceremony), full lifecycle, handoffs/messaging, git-versioned truth, published numbers | Local zero-cost reranking, real-time collaborative editing, Postgres backend, `build_context` graph-walk, hosted mobile/web UX |
-| **agentmemory** (hook capture, KV store) | **Yes** for operability + data ownership | Self-contained binary (no `iii-engine` sidecar, no ELv2 runtime), files-as-truth, SQL indexes committed in-txn, zero-LLM summaries and handoffs, typed claim-once handoffs, a multi-user auth ladder (DB tokens, OIDC), native Windows without a manual sidecar download (ours is still "Experimental"), and a 3.0 importer for its vault and `ExportData`. Both now default to auth on for new installs (theirs since 0.9.30, ours in 3.0) | Browser edit/forget (the 3.0 web UI adds page history/diff, a session timeline, a recall trace and a health panel, but stays read-only by design), the iii console's OTEL traces (we ship explain timings + Prometheus `/admin/metrics` in 3.0), a P2P mesh-sync primitive (`ai-memory-wikisync` is our git-based answer), the opt-in local cross-encoder reranker, an npm/`npx` install (ours is a two-command native install on Linux and macOS in 3.0, no npm package), ~31 more tools (54, all visible by default; mostly speculative). Benchmarks are not like-for-like: their 95.2% LongMemEval-S is a component measurement with the reranker disabled (their 2026-10-09 baseline adds 84.68% strict recall-all@5, which they say supports no competitive claim), ours is end-to-end |
+| **agentmemory** (hook capture, KV store) | **Yes** for operability + data ownership | Self-contained binary (no `iii-engine` sidecar, no ELv2 runtime), files-as-truth, SQL indexes committed in-txn, zero-LLM summaries and handoffs, typed claim-once handoffs, a multi-user auth ladder (DB tokens, OIDC), native Windows without a manual sidecar download (3.1 `install.ps1` + `setup`), and a 3.0 importer for its vault and `ExportData`. Both now default to auth on for new installs (theirs since 0.9.30, ours in 3.0) | Browser edit/forget (the 3.0 web UI adds page history/diff, a session timeline, a recall trace and a health panel, but stays read-only by design), the iii console's OTEL traces (we ship explain timings + Prometheus `/admin/metrics` in 3.0), a P2P mesh-sync primitive (`ai-memory-wikisync` is our git-based answer), the opt-in local cross-encoder reranker, an npm/`npx` install (ours is a two-command native install on Linux, macOS and Windows in 3.0/3.1, no npm package), ~31 more tools (54, all visible by default; mostly speculative). Benchmarks are not like-for-like: their 95.2% LongMemEval-S is a component measurement with the reranker disabled (their 2026-10-09 baseline adds 84.68% strict recall-all@5, which they say supports no competitive claim), ours is end-to-end |
| **Claude Code built-in memory** | **Yes** for teams / multi-machine / multi-harness; **not obviously** for a solo dev on one machine in Claude only | Cross-machine, cross-harness, team sharing, tool-lifecycle capture, real search | Zero setup: it's already on with no server to run (our one structural disadvantage for the solo case; 3.0's `install.sh` + `ai-memory setup` cut ours to two commands on Linux and macOS, but there is still a server) |
| **Hindsight** (pages-over-facts; coding-agent package) | **Yes** for zero-LLM, files-as-truth, or claim-once handoffs; **no** if you want its end-to-end QA numbers, git-history ingestion, or 16+ agent installer | Zero-LLM default (Hindsight needs an LLM, local or by subscription), markdown files as the source of truth (its markdown is a one-way mirror of Postgres), one binary, claim-once handoffs, cross-project messaging, and (new on 2.4) a belief-strength `confidence` + an opt-in "dream" rewrite that borrow their model but never delete a source and keep the zero-LLM default | Its published end-to-end QA accuracy, git-history ingestion, hooks for 16+ coding agents with one shared bank per repo, a reranker on by default, image/file ingestion, user/team/company scopes inside a bank, and belief-strength that *actually moves ranking by default* (ours ships but is off and eval-gated) |
| **Mem0** (fact extractor; coding plugins) | **Yes** for coding memory without a cloud key; **no** for app end-user personalization | Zero-LLM, no cloud API key, no telemetry, editable pages, git truth, claim-once handoffs, cross-project messaging | Native plugins for seven coding agents from one runtime, failed-command-to-fix capture with categories, a subdirectory search scope, shared team plus personal memory, cloud user profiles, and its SDK/integration ecosystem |
@@ -281,7 +281,7 @@ invariants), **ALREADY** (we have it and should say so).
| Viewer read side: version diff, session timeline/replay, recall trace, health | SHIPPED (3.0) | Page history with server-side diffs, a paged session timeline, a recall trace with per-stream ranks, a root-only health panel |
| OTEL traces / metrics | SHIPPED (3.0) as explain timings + content-free Prometheus `/admin/metrics`; OTLP export MEASURE-FIRST (demand-gated) | If built: off by default, no subscriber layer when off, OTLP over http/protobuf on the existing reqwest/rustls, exporter modules filtered out of the subscriber (invariant 15), a span-field allowlist (durations, counts, UUIDs only), ratio sampling, and `cargo deny` must pass |
| Auth on by default | SHIPPED (3.0) for new installs; requiring auth on existing loopback installs DECLINED for 2.x | Flipping existing installs would break every env-less hook and MCP config, a major change under our semver. Existing installs opt in with `ai-memory auth enable` |
-| One-command installer / onboarding | SHIPPED (3.0) for Linux and macOS (`install.sh` + `ai-memory setup`); the agent-driven install doc is folded in | No npm package; no Windows service step |
+| One-command installer / onboarding | SHIPPED (3.0 Linux/macOS, 3.1 Windows) for three platforms (`install.sh`/`install.ps1` + `ai-memory setup`); the agent-driven install doc is folded in | No npm package |
| Many-language README | DECLINE | Translations go stale on every release, and stale docs are defects under our quality bar |
| Large speculative tool surfaces (leases, task graphs, routines, sentinels, sketches, crystals, facets; 50+ tools visible by default) | DECLINE | No evidence of real use; each tool adds prompt-surface cost; we keep 24 tools and have run leases where needed |
| Signals between agents | ALREADY | Typed cross-project messaging with exactly-once pop |