
Shared structural memory for AI coding agents: bi-temporal graph, MCP-native, zero LLM calls.
By Tanmay Verma, Founder · Last verified 03 Jul 2026
In short
Memtrace Public — Shared structural memory for AI coding agents: bi-temporal graph, MCP-native, zero LLM calls. Best for Teams running multiple AI coding agents concurrently, Engineering teams with large monorepos needing impact analysis, Organizations automating CI/CD agent workflows. Contact Sales pricing.
See what real users actually say. We scan live discussions, reviews and complaints across the web and hand you an honest verdict — in under a minute.
3 free scans · no card needed · downloadable report
Promises a compelling solution to agent coordination and memory, but with no public access, unverifiable benchmarks, and zero documentation, it remains vaporware for now. Watch for its Phase 2 rollout to evaluate real-world performance.
Compare with: Memtrace Public vs Bito, Memtrace Public vs LangSmith, Memtrace Public vs Chrome DevTools MCP
Last verified: July 2026
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
1 mentions across 1 source (Hacker News).
How likely is Memtrace Public to still be operational in 12 months? Based on 4 signals — momentum (how recently it shipped), wrapper dependency, revenue model, and web presence.
Last calculated: July 2026
How we score →Memtrace is a shared memory layer for AI coding agents, built as a bi-temporal graph database that tracks code structure and version history. It serves as a single source of truth that an entire fleet of agents can read from, providing a live code map, coordination, and persistence without relying on any LLM calls. Targeted at teams using multiple AI coding agents (e.g., Cursor, Claude Code, Codex, Windsurf), Memtrace aims to eliminate common problems like forgotten context, merge conflicts, and redundant work. It does this by having agents announce intent before editing, checking the code map for overlaps, and automatically resolving safe conflicts. Key differentiators include a custom-built graph database (MemDB) where time is a first-class citizen—every record knows its validity period, so the system can instantly rewind to any past state. The platform is MCP-native, integrates directly into editors via plugins, and boasts a 97.3% accuracy rate on impact analysis, with 13ms query latency. However, as of July 2026, Memtrace is not yet publicly launched. The website only shows a sign-in flow to join a paced access queue (waitlist). No pricing, no changelog, and no public documentation are available. The claims on the homepage (benchmark numbers, fleet coordination) are self-reported and unverifiable without public access. The privacy-conscious design (no LLM calls, local graph) appeals to teams wary of sending code to third-party APIs.
Memtrace is targeting a real pain point: multi-agent chaos. If you've run more than two AI coding agents on the same repo, you've seen context loss, merge conflicts, and wasted token spend. Memtrace's core idea—a shared, time-aware graph that agents read from without LLM calls—is clever and technically ambitious. The self-reported numbers (97.3% accuracy, 13ms latency, 90% auto-merge) are impressive, but they come with zero public validation. There's no code, no docs, no third-party review. MemDB being custom-built in Rust is a positive signal, but without benchmarks you can reproduce, it's a claim. For now, this is a waitlist product. Teams needing a solution today should look at alternatives like Codegen (SDK for code analysis) or Context (shared memory via MCP). However, if Memtrace delivers on its promises, it could be a game-changer for agent coordination. We'll revisit when access opens.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Common stack mates teams adopt alongside Memtrace Public, with the specific reason each pairing earns its keep.
Used Memtrace Public? Help shape our editorial sentiment research.