
RSM @wekaio | MBA Grad @UCLA | Husband | @Chelseafc fan
Los angeles, CA
Joined June 2025
- Tweets354
- Following280
- Followers63
- Likes458
This @weka article takes a closer look at KV cache and why storing and reusing context more effectively can have a major impact on inference costs and performance.
Worth a read if you're thinking about the infrastructure behind agentic AI. spr.ly/6013BGL4dP
Ruben Abdalian retweeted
Working with Cerebras has been amazing. When we first integrated Cerebras into Gimlet, we were blown away by the speed of AI: You can stay in-context and get more done.
Now we're bringing it online asap. Reach out if you want to learn more!
We’re bringing @cerebras wafer-scale compute to Gimlet Cloud.
100 MW planned. First datacenter expected later this year, with speeds up to 3,000 tokens/sec.
Building the multisilicon inference cloud.
Blog: gimletlabs.ai/blog/cerebras-…
Interesting results from a new benchmark with @nebiusai.
@weka Augmented Memory Grid delivered 2.4x more requests on the same @nvidia HGX B300 hardware, while recomputing 3.2x fewer tokens. spr.ly/6015BGcLAb
New benchmark results from @weka and Nebius show the impact of shared KV caching on sustained agentic inference.
Running on @nvidia HGX B300 instances in Nebius AI Cloud, WEKA’s Augmented Memory Grid served 2.4× more requests than HBM-only while keeping median time to first token near one second.
Worth a read for anyone working through the infrastructure demands of long-context agents: nebius.com/blog/posts/nebius…
👏 Great to see @weka connecting with customers, partners and the broader AI community around where the industry is headed at #AIInfraSummit.
Interesting to see how data can stay on @weka NeuralMesh while still being part of @databricks workflows.
WEKA OpenSharing makes it possible to query selected data without copying it to the cloud, while keeping access and governance in place. spr.ly/6015BGVJ7t
🏆 Excited to see WEKApod recognized as a 2026 TechForward Awards winner in the AI Infrastructure & Systems category!
📄 Download the TechForward Buyer’s Guide: spr.ly/6010BGTok8
Heading to #AIInfraSummit 2026?
Be sure to check out the WEKA booth (710) for some swag, dirty sodas and a good conversation about where #AIInfrastructure is headed.
Hope to see you there! spr.ly/6016BGuQ3K
At sundown tonight, Rosh Hashanah begins, marking the start of the Jewish New Year.
It’s a time to reflect, spend time with the people we care about, and look ahead with hope for the year to come. And, of course, no Rosh Hashanah is complete without apples and honey for a sweet new year.
From all of us at WEKA, we wish a happy, healthy and sweet new year to our colleagues, friends and families in Israel, the U.S. and around the world who celebrate.
L’shanah tovah! 🍎🍯
🙌 Excited to see @weka and @backblaze team up!
The collaboration gives AI teams a validated way to use NeuralMesh for performance-sensitive workloads and Backblaze B2 for the data, checkpoints and outputs they need to keep at scale. spr.ly/6018BGzGA0
🙌 #AIInfraSummit 2026 is just two weeks away!
If you’re heading to the show, keep an eye out for the @weka team at booth 710 and catch Shimon Ben-David’s session on the economics of inference.
🔗 spr.ly/6016B1CYlu
👏 WEKA NeuralMesh with Augmented Memory Grid is a 2026 A.I. Awards finalist for Best AI Infrastructure Solution.
Proud to see our work helping AI workloads get more performance and efficiency from GPU infrastructure recognized by The Cloud Awards.
📄 weka.ly/4gpCtGi
🏆 ICYMI: WEKApod was named a finalist in the #AIInfrastructure & Systems category of the SiliconANGLE & theCUBE TechForward Awards.
🔗 Check out the full list: weka.ly/3SYpNgB
As agentic workloads evolve, so does the question of where inference should happen. CPU? GPU? Both?
Don't miss this convo with @weka, @Oracle, and @SemiAnalysis_ to learn more about the tradeoffs and what they mean for building #AIInfrastructure. spr.ly/6014B1Fgpe
Ruben Abdalian retweeted
Most used coding agent at Activeloop is Claude Code.
Over last 90 days, our internal use
- 250K traces
- 3K sessions
- 60% of sessions succeeded
Success is measured by a judge LLM reviewing the traces and looking for explicit feedback.
Over the last 90 days, we captured traces from our coding agents to do continual learning.
Here’s what I shared during my keynote on the Continual Learning Loop at the AGI Summit.
We plugged Hivemind into every coding agent at the company: Claude Code, Codex, Cursor, OpenClaw, and Hermes.
- 93% of tokens are used for computer interaction
- 77% of sessions contain at least one correction
- 60% of sessions are judged by an LLM to have been resolved correctly
More interestingly, 1 in 10 sessions leaked a secret credential to an LLM provider.
In-context learning is considered one of the best continual learning methods so far. But how good is it?
Apparently, it is 80% as good as weight updates without all the heavy lifting of fine-tuning.
Naive SFT on coding-agent traces causes the model to collapse. At best, it delivers only marginal improvements. As coding agents use frontier models, distillation can work into smaller models.
But learning from your own LLM traces is very hard. You can easily
- misalign the model
- forget knowledge
- lose capability.
Doing this continually is even harder. You can easily run into cumulative catastrophic forgetting.
Furthermore, learning a new capability from your own traces does not work. So how can we expect the model to develop new capabilities?
How can we dream?
One recipe that worked for us was generating the missing experiences based on failures observed in the traces.
We then used RL environments to train the model and ran it in shadow mode for three weeks. It outperformed Claude Code 60% of the time.
Many people asked, Where should we start?
Start capturing your traces now.
Ruben Abdalian retweeted
We talked to hundreds of engineers at AGI Summit this weekend.
We started to notice some patterns around issues.
The same frustrations came up over and over:
• “We are trying to reel in our engineer spend and API cost on tokens”
• “We’re seeing the same bugs come up repeatedly from different engineer output. There doesn’t seem to be any knowledge carry over from things we’ve already fixed across teammates.”
• “Our knowledge base doesn’t seem to be enough to optimize agent output. My agent finally learns our codebase conventions, then the session ends and it's all gone."
Are you facing similar issues internally? What do your agents keep forgetting? 👇
What stood out to me most is how much valuable learning is hidden inside everyday agent usage.
Every correction, failure, and successful workflow creates data that can help the next session perform better.
The companies that start capturing those traces now will have a real advantage as coding agents become a bigger part of how teams operate.
Over the last 90 days, we captured traces from our coding agents to do continual learning.
Here’s what I shared during my keynote on the Continual Learning Loop at the AGI Summit.
We plugged Hivemind into every coding agent at the company: Claude Code, Codex, Cursor, OpenClaw, and Hermes.
- 93% of tokens are used for computer interaction
- 77% of sessions contain at least one correction
- 60% of sessions are judged by an LLM to have been resolved correctly
More interestingly, 1 in 10 sessions leaked a secret credential to an LLM provider.
In-context learning is considered one of the best continual learning methods so far. But how good is it?
Apparently, it is 80% as good as weight updates without all the heavy lifting of fine-tuning.
Naive SFT on coding-agent traces causes the model to collapse. At best, it delivers only marginal improvements. As coding agents use frontier models, distillation can work into smaller models.
But learning from your own LLM traces is very hard. You can easily
- misalign the model
- forget knowledge
- lose capability.
Doing this continually is even harder. You can easily run into cumulative catastrophic forgetting.
Furthermore, learning a new capability from your own traces does not work. So how can we expect the model to develop new capabilities?
How can we dream?
One recipe that worked for us was generating the missing experiences based on failures observed in the traces.
We then used RL environments to train the model and ran it in shadow mode for three weeks. It outperformed Claude Code 60% of the time.
Many people asked, Where should we start?
Start capturing your traces now.
Ruben Abdalian retweeted
That's a wrap on AGI Summit 2026
Two days at the Palace of Fine Arts. 500+ of you stopped by the booth and wanted to learn more about the infra layer that levels up your coding agents.
Standard memory tools collect prompts and outputs.
Hivemind turns your coding agents' traces into skills: crystallized once and propagated to every agent on your team.
Legion Code cut token spend 34% (~$12K/month saved) doing exactly this.
Missed us at the booth? DMs are open.
Agents that compound.



















