
@xmemory_aii
š¬š§Account based in
About this account
- Account based in
- United Kingdom
- Connected via
- Web
Account-level information from X, not a live location or the device used for a specific post.
The memory layer for AI workflows, built for precision, reliability, observability, and governance.
Joined March 2026
- Tweets20
- Following2
- Followers19
- Likes3
Agents should get better with experience. We teamed up with @tolokaAI to measure that.
Toloka evaluated xmemory on closed datasets. No peeking at the data. No tuning to the benchmark. Just learning from failures and measuring what improves.
š The results:Ā 26% lower token costsĀ when xmemory replaced document search as the policy store. And adding lessons from past runs lifted scores byĀ 4.8 percentage points on held-out tasks.
š” It means with memory, a mid-size open-weight model scoredĀ 0.75 ā beating Sonnet 5 at 0.68 and GPT-5.6 Terra at 0.69Ā without memory.
This experiment is just the beginning of what memory can unlock. We see even bigger gains on longer-horizon tasks, where every lesson has more chances to pay off.
Read our blog post below!
The right model for the right step. Thatās how we build memory at xmemory ā benchmarking for quality, cost, and latency.
We tested @typesafeai's Jev as a judge of extracted data. It recoveredĀ 81% of the accuracy gapĀ between a fast and a slow extractor while sending onlyĀ 38% of recordsĀ back for another pass.
The catch? It worked when judging individual fields. Asked to judge a whole record, it did no better than a coin flip.
Link in the first comment!
Weāre excited to announce @xmemory_aiās partnership with @temporalio!
We have deep respect for Temporalās leadership in reliable workflow execution, and weāre glad to work closely together as developers build the next generation of long-running agents and agentic teams.
The integration brings togetherĀ durable execution and shared, structured memory. Temporal helps workflows recover from interruptions and continue their work. xmemory lets developers define the facts, relationships, and domain rules agents rely on ā keeping that knowledge available across runs, sessions, and teammates.
Together, weāre helping developers build agents that keep working ā and teams that build on what each agent learns. Learn more in our blog post via the link in the first comment!
#Temporal #xmemory #AgenticAI
Agentic memory harness is more difficult than harness for coding agents.
There is no quick self-correcting loop, and unlike with coding tasks mistakes accumulate and multiply.
At #xmemory we are solving this once and for all.
66.88%. 80.1%. 85%. 90.79%. 93%. 100%.
These are all SOTA scores on agentic memory benchmarks. None of them tell you whether the system will work in production.
The deeper problem isn't the data ā it's that we often misunderstand what these numbers actually measure. In our recent white paper we open-sourced datasets that target specific memory functions. Today we published a follow-up that explains why we think the well-known agentic memory benchmarks (LoCoMo, LongMemEval) miss the mark for production systems, and what we measure instead.
We're in a field that is measuring itself against itself. The real question isn't 'are we beating last week's leaderboard?' ā it's 'are we building something that makes people's work meaningfully better?' That's harder to measure. It's also the only thing that matters.
(Link in the first comment)
Let's sit down and talk about your real use cases!
Weāre excited to share that our team at @xmemory_ai has published our main white paper.
The core idea is simple: without focus, AI systems try to "remember" everything, and that is where they fail. Schema is the best way to teach them focus.
We compared xmemory against major open-source and commercial RAG and hybrid RAG systems, markdown-file memory approaches ("agentic memory"), and memory implementations in customer-facing frontier AI apps. Instead of testing whether systems can recall similar text, we evaluated whether they can store, update, deduplicate, and retrieve facts and relationships reliably.
xmemory achieved 97% accuracy, compared with 87% for the strongest competitor. Our core also outperforms the latest frontier modelsā one-shot APIs in extraction tasks, showing that the harness matters just as much as model quality.
Weāve also open-sourced our measurement datasets and a toolkit to generate new ones synthetically.
Huge thanks to the dream team of engineers at xmemory who keep pushing this vision into production. If your company is seeing memory systems fail in real workflows, weād love to talk.
Why are we forcing agents to adapt to software stacks that were never designed for them? A lot of what people call "agent infrastructure" today looks like a temporary patchwork - prompts, wrappers, glue code, and brittle orchestration compensating for systems that cannot express meaning clearly enough on their own.
We think that is backwards. Agents should handle intent and reasoning. Systems should handle semantics, structure, and ambiguity. If that shift happens, it could change the software stack more than most people expect.
Read our second blog post via the link in the first comment.
xmemory retweeted
We first open-sourced @BessemerVP's AI Infrastructure roadmap in 2024. The velocity of progress across the landscape in the past 18 months has been breathtaking, and weāve already seen generational companies arise.
But the infra evolution is far from over, as the next generation of platforms may prove even more consequential. @lancectk @davidcowan @TaliaGold @gracejhma @bhavikvnagda @BrandonNydick @bar_weiner & I believe the stage is set for five new infra frontiers, each representing a fundamental shift from building AI that can process information to building AI that can truly operate in the world in 2026.
Our full report: bvp.com/atlas/ai-infrastructā¦
Thrilled to see @xmemory_ai featured in @BessemerVPās latest AI Infrastructure Roadmap for 2026.
Weāre one of the companies highlighted in Memory, Context, and State Management, alongside seven other strong builders.
What stands out even more than the mention is the broader shift it signals: memory is becoming core infrastructure for production AI.
As AI moves from one-off interactions to persistent, real-world workflows, the systems that win will be the ones that can retain context, manage state, and stay grounded over time.
Proud of what the our team is building, and excited for what comes next.
#AIInfrastructure #Memory #ContextManagement #AgenticAI #EnterpriseAI
Today weāre sharing our first blog post:Ā āSchema as the Core of Reliability.ā
Our view is simple:
AI memory breaks down when facts are stored as unstructured text and reconstructed later. That approach can work for thematic recall, but it becomes fragile when systems need to answer exact questions, maintain state, support workflows, and drive automation.
In the piece, we explore why:
- Search can recover context, but memory must support facts
- Graph RAG is a meaningful step forward, but not the endpoint
- Reliable memory needs structure - types, relations, constraints, deduplication, provenance
- Schema is not decoration - it is the contract that makes memory observable, enforceable, and dependable
If AI systems are going to do more than sound coherent - if they are going to make decisions, trigger workflows, and operate over long horizons - memory has to become a governed system of facts.
That is where reliability starts.
Read the full post - link in the first reply.












