Updates, insights, and deep dives from the MemClaw team.
Looking for case studies and integrations? Browse Use Cases →
A brand-new agent has flawless reasoning and nowhere to stand. Pre-seeded, scoped ingestion (per organization, per department) plus mandatory keystones give it the knowledge base and the rulebook on turn one — governed, auditable, and shared, instead of an ever-growing system prompt.
Read article →Claude Fable 5 posts the highest win rate on PeerRank's board — then places third, because a safety classifier refuses ninth-grade biology and logs the refusals as empty, successful calls that get averaged into its score. The numbers, the forfeits, and the fix Anthropic already ships.
Our new arXiv paper formalizes the fleet-memory problem, defines the primitives a governed memory system needs, and measures MemClaw against a live production service — including the two architectural bugs the measurement caught. The negative results are the point.
When several agents independently learn the same lesson, MemClaw's Skill Factory distills it into a reusable skill — then a deterministic scanner and an active-only gate keep it safe. The mechanism, plus a live run that blocks 6/6 adversarial skills.
Most teams build organizational intelligence as a pile of bespoke skills — one per capability, one per agent. You don’t need the pile. You need one skill, used properly, over governed shared memory: recall before work, obey the keystones, reuse the playbooks, compound what every agent learns.
In a fleet, the tokens that dominate the bill aren’t spent on reasoning — they’re spent on repetition. The memory-infrastructure principles that keep cost flat as the fleet grows.
When your user pushes back and your AI agent caves, the problem isn’t the model — it’s the enforcement layer. Probabilistic enforcement isn’t enforcement; it’s hope. Here’s how MemClaw’s keystones primitive fixes it.
Apache 2.0. The whole storage layer, the 12 MCP tools, the OpenClaw plugin, the audit trail — yours to read, run, fork, and ship. Five minutes from git clone to a working multi-agent memory layer.
Six operations and one collection-based primitive that replaces a shelf of side-systems. Customer records, config, skills, playbooks — one tool, with semantic search opt-in per collection.
Single-agent memory is a solved category with many good vendors. Multi-agent governed shared memory is a new category — and MemClaw is the one defining it.
MemClaw on the two public agent-memory benchmarks: 23 ms p50 search, 96–99% token savings, accuracy comparable to the leaders — and the fleet-shaped problem these benchmarks can’t measure.
The Karpathy Loop proved autonomous AI research works. But scaling it to agent fleets needs governed shared memory — persistent, structured, and self-improving.
How AI agents evolved from stateless chatbots to Karpathy loops and Meta’s self-modifying hyperagents — and why governed shared memory is the missing infrastructure layer.
A deep dive into MemClaw’s architecture: the write path, search path, governance layer, and integration surface that power governed shared memory for agent fleets.
OpenClaw turned AI from a tool you prompt into a coworker that lives on your machine. Now enterprises are deploying fleets — and discovering that the hardest problem isn’t the agent.
Agent fleets are scaling. Memory isn’t. The missing layer between isolated agents and compounding intelligence is governed shared memory — and building it is harder than you think.