LLM = CPU (data: tokens not bytes, dynamics: statistical and vague not deterministic and precise)
Agent = operating system kernel
AGENTS
-
LLMs as CPUs: Statistical Processing and Agent Operating Systems
By
–
-
Terminal-Bench 3.0 and the Benchmark Factory Revolution
By
–
Terminal-Bench 2.0 went from ~25% → 80% in four months and became the standard eval for frontier CLI agents. Now, TB3 is in the works.
— vincent sunn chen (@vincentsunnchen) 31 mars 2026
I talked to @alexgshaw about what happens when model capabilities climb faster than we can measure them.
His answer: the benchmark factory… pic.twitter.com/phNP7ni43tTerminal-Bench 2.0 went from ~25% → 80% in four months and became the standard eval for frontier CLI agents. Now, TB3 is in the works. I talked to @alexgshaw about what happens when model capabilities climb faster than we can measure them. His answer: the benchmark factory (@harborframework)— infrastructure to develop hard, representative evals at the pace that the frontier moves. As Alex put it: "we need a thousand times more benchmarks than we have right now." 00:23 – How quickly models hill-climbed TB2 01:46 – What rapid progress reveals about benchmarks vs. real-world capability 03:28 – What made Terminal-Bench stick 04:58 – Why the terminal is the right abstraction for agentic AI 07:14 – How TB2 maintains task quality at scale 09:23 – Managing benchmark integrity in a benchmaxxing world 10:47 – Harbor: from experiment to benchmark factory 12:19 – What Harbor does that nothing else did 14:37 – The invariants: what won't change as agent evals evolve 16:55 – The benchmark Alex most wants to see built 18:18 – The ideal human-in-the-loop task creation flywheel 20:32 – How to contribute to Terminal-Bench 3.0
→ View original post on X — @snorkelai, 2026-03-31 18:50 UTC
-
AI Agent Leaks Claude Code, Recoded in Python
By
–
un agent IA a permis de faire leaker le code de claude code, un humain a recodé en python…
-

Cursor: Build AI Agents That Run Automatically
By
–
Build agents that run automatically · Cursor buff.ly/0wrnb02
#AI #MachineLearning #DeepLearning #LLMs #DataScience [Translated from EN to English]→ View original post on X — @miketamir, 2026-03-31 18:47 UTC
-

LangChain Partners with MongoDB for AI Stack Integration
By
–
Announcing our partnership with @MongoDB
: The AI Stack that runs on the database you already trust Atlas Vector Search as a drop-in retriever. MongoDB Checkpointer for durable agent state in LangSmith Deployment. Text-to-MQL for natural-language queries over operational data. -
LeWorldModel: Stable JEPA Architecture for Offline Robotics World Models
By
–
Paper review: LeWorldModel: Stable End-to-End Joint-Embedding Predictive Architecture from Pixelshttps://t.co/2dD7hPIURL
— John Carmack (@ID_AA_Carmack) 31 mars 2026
Nice clean github: https://t.co/YZ4e1eUACi
This is the application of the LeJEPA results to world models, trained offline on experience from three different… https://t.co/rJojWTCP6bPaper review: LeWorldModel: Stable End-to-End Joint-Embedding Predictive Architecture from Pixels arxiv.org/pdf/2603.19312 Nice clean github: github.com/lucas-maes/le-wm This is the application of the LeJEPA results to world models, trained offline on experience from three different robotics style tests with one to two million steps in each dataset. Re-states the benefits of the SigReg loss relative to prior world model approaches. Uses ImageNet standard 224×224 RGB pixel input images with an unmodified ViT-Tiny vision transformer from HuggingFace to generate latents. One extra post-projection step is needed to give SigReg the necessary freedom to perturb the latents into independent gaussians, since ViT ends with a layernorm’d layer. Also tested with ResNet-18, which still performed well, but slightly worse. Uses a 192 dimensional latent. Performance slightly dropped when doubling the latent size to 384; it would be nice to know if it was stable there, or if it continued worsening with excessive latents. There is a relationship between batch size and SIGReg, the larger latent may have improved performance if the batch size was increased. The predictor is implemented as a ViT-S backbone – Why a vision transformer when the latent is flat? Uses a history of 3 sets of latents for two of the benchmarks and 1 for the other. Performance was markedly better with the “small” ViT model than the “tiny”, but the larger “base” model degraded notably, which is interesting. Dropout of 0.1 on the predictor significantly improved performance. 0.2 was still better than 0.0, but 0.5 was worse. Trained with a batch of 128 x 4 trajectories. I wish their training loss graphs were more zoomed in with grid lines. Performs planning at test time instead of building a policy by training in imagination like Dreamer / Diamond. Rolls out 300 initially random sets of actions up to a planning horizon H of 5 (at frame-skip 5). Iterates up to 30 times using the Cross Entropy Method (CEM). The main paper body mentions using Model Predictive Control (MPC) strategy, where only the first K planned actions are executed before replanning, but appendix D says they execute all 5 planned actions. After training, they probe the latent space to demonstrate that it does capture and represent physically meaningful quantities. They also implement a decoder from the latent space back to pixels – not used by the algorithms, but helpful to see what things the latent space is actually representing. They tested incorporating the reconstruction loss into training, but it hurt performance somewhat. They wound up with a 0.1 lambda for SigReg, as opposed to 0.05 in the LeJEPA paper. 1024 sigreg projections, but observe the number has negligible impact I like the JEPA framework, but so far my attempts to use it on Atari games with value functions have not matched my other efforts. Lucas Maes (@lucasmaes_) JEPA are finally easy to train end-to-end without any tricks! Excited to introduce LeWorldModel: a stable, end-to-end JEPA that learns world models directly from pixels, no heuristics. 15M params, 1 GPU, and full planning <1 second. 📑: le-wm.github.io — https://nitter.net/lucasmaes_/status/2036080584569618741#m
→ View original post on X — @id_aa_carmack, 2026-03-31 18:24 UTC
-

AI Agent Traps: Beyond Prompt Injection to Environment-Level Threats
By
–
AI agents don’t just inherit LLM risks — they amplify them. I came across an interesting paper: “AI Agent Traps.” Most discussions still focus on prompt injection. That’s already incomplete. Because once agents have: – autonomy – persistence – tool access …the attack surface fundamentally shifts. ➡️ The real vulnerability becomes the information environment itself. Everything an agent interacts with can be adversarial: – web pages – emails – APIs – databases All of it can be weaponized. The paper outlines a taxonomy of six adversarial trap classes — from: – hidden prompt injections embedded in content – to systemic risks across multi-agent ecosystems What stands out is the shift from: model-level threats → environment-level threats That’s where most current agent architectures are still underprepared. If you’re building or deploying AI agents, this is worth paying attention to. Paper link : papers.ssrn.com/sol3/Deliver… 🔗 Follow my communities and personal initiatives: • Amazing AI, Data, Quantum Computing & Emerging Technologies — drdebashisdutta.com/ • Research & Innovation – Quantum, AI & Advanced Systems — researchedge.org/ #AIAgents #LLMSecurity #PromptInjection #AgenticAI #AISafety #MultiAgentSystems #CyberSecurity #CyberSecurity
→ View original post on X — @debashis_dutta, 2026-03-31 18:11 UTC
-
GenAI and RAG Automate Industrial Diagnostics and Troubleshooting
By
–
GenAI and RAG instantly search manuals, logs, and forums to provide probable cause and recommended action.
— Lucian Fogoros (@fogoros) 31 mars 2026
No more digging through 6,000-page turbine manuals. AI agents layer over ML tools to give context to anomalies.
From alert to answer in seconds. pic.twitter.com/eYiljr3nPuGenAI and RAG instantly search manuals, logs, and forums to provide probable cause and recommended action.
No more digging through 6,000-page turbine manuals. AI agents layer over ML tools to give context to anomalies.
From alert to answer in seconds. -

Agentic Inference: Hybrid GPU-RDU Hardware Strategy for Token Serving
By
–
Agentic inference isn’t a “future trend” anymore — it’s the default. The real question: how do you serve fast, premium tokens without building a multi‑MW Frankenstack? Our take: GPUs for prefill, RDUs for decode. Hybrid > GPU‑only. 🔗 sambanova.ai/blog/agentic-in…
→ View original post on X — @sambanovaai, 2026-03-31 17:30 UTC
-

Liquid AI Releases LFM2.5-350M Compact Agentic Model
By
–
Very proud of our tiny powerhouse. Amazing performance in data extraction and tool use at such a small scale. Enjoy! 🚀 Liquid AI (@liquidai) Today, we release LFM2.5-350M. Agentic loops at 350M parameters. A 350M model trained for reliable data extraction and tool use, where models at this scale typically struggle. <500MB when quantized, built for environments where compute, memory, and latency are constrained. 🧵 — https://nitter.net/liquidai/status/2039029358224871605#m
→ View original post on X — @maximelabonne, 2026-03-31 17:29 UTC