Fetching from the wire…
Public story · 2026-07-10 · high
AutoMem runs two meta-LLM loops, one reshaping the scaffold, the other training a memory specialist from its traces.
Why now: The paper surfaced in research coverage dated July 10, 2026.
AutoMem lifted a 32B open-weight model to parity with Claude Opus 4.5 and Gemini 3.1 Pro Thinking, using memory training alone, per a new Stanford paper.
That's a 2x to 4x gain across three game-based benchmarks, using the same base model, with no bigger checkpoint required.
The system runs two meta-LLM loops. One reshapes the agent's scaffold: prompts, file schemas, and the vocabulary of actions available to it. The other trains a memory specialist from the agent's own traces, so it learns what to keep and drop from experience.
Filesystem operations count as memory actions, on equal footing with task actions, and the model decides when to use them. The results come from three environments: Crafter, MiniHack, and NetHack.
A 32B model with trained memory matching bigger models makes memory design the cheap lever, not a solved problem. The paper doesn't say how this holds up on tasks with real tool use instead of game state.
Each link below shares sources, entities, or timing with this story.
Stanford benchmarked against Gemini / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Stanford benchmarked against Gemini); both cover Gemini, LLM, Opus; reported by the same outlet (arxiv.org).
Stanford benchmarked against Gemini / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Stanford benchmarked against Gemini); both cover Claude Opus, Gemini, Opus; reported by the same outlet (arxiv.org).
Stanford benchmarked against DeepSeek / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Stanford benchmarked against DeepSeek); both cover Claude Opus, Gemini, Opus; reported by the same outlet (arxiv.org).
Claude Code uses Opus / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code uses Opus); both cover Claude Opus, Opus, Stanford; overlapping topics (agent, claude, model, opus).
Opus built by Anthropic / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Opus built by Anthropic); both cover Claude Opus, LLM, Opus; overlapping topics (model, opus).
Claude Code uses Opus / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (Claude Code uses Opus); both cover Claude Opus, Gemini; reported by the same outlet (arxiv.org).
Stanford benchmarked against Claude / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Stanford benchmarked against Claude); both cover Claude Opus, Gemini, Opus; overlapping topics (agent, claude, opus).
Stanford benchmarked against Gemini / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Stanford benchmarked against Gemini); both cover Gemini, LLM; reported by the same outlet (arxiv.org).