← Dispatch

Proteus: Why Your Long-Context Model Needs a Memory That Grows

2026-08-18 · Alfred · 5 min read

Every memory-augmented sequence model today has the same flaw: it treats its memory as a fixed-size bucket from token one. Early tokens, facing no compression pressure, sprawl across the available degrees of freedom, polluting the state and leaving no room for what comes later.

A new paper from Bayat, Behrouz, Mirrokni, and Courville (Google Research / Mila) identifies this as static memory pollution and proposes a remarkably simple fix: start with a bottleneck, then progressively unlock fresh memory capacity as the context grows. They call it Proteus, and it works across four different state-of-the-art memory architectures with zero additional parameters.

The Problem: Your Memory State Is Full of Early Trash

Attention’s quadratic cost has driven a wave of memory-based alternatives—models that compress context into a compact recurrent state. SWLA, Comba, Titans, Hope-Attention, and others all share a common design: a fixed memory capacity exposed uniformly through the sequence.

The authors identify two failure modes of this design:

The conventional response is to make memory bigger. But bigger memory means more degrees of freedom at every position, which makes the pollution problem worse—the early tokens just have more room to spread.

The Method: Progressive Unlocking

Proteus is not an architecture. It’s a scheduling mechanism that wraps an existing memory module:

mindmap
  root((Proteus))
    Early bottleneck: small effective capacity
      Forces aggressive compression
      Prevents pollution
      Captures only essential info
    Gradual expansion: unlock capacity
      Fresh slots for new content
      Reduces interference
      Growth is deterministic
    Drop-in: zero extra params
      Works on any memory model
      SWLA, Comba, Titans, Hope-Attention
      Single line of code change
    

The mechanism is straightforward. The memory has a maximum capacity K (same as before). But instead of exposing all K slots from position 1, Proteus starts with a smaller effective capacity k < K and grows it deterministically over the sequence length. The early bottleneck forces the model to compress hard—it cannot rely on brute-force memorization. As the bottleneck relaxes, fresh capacity arrives for new information.

This is implemented as a simple masking operation on the memory read/write gates. No learned parameters, no architectural changes, no additional training cost. Just a schedule.

The Results: Consistent Gains That Grow With Context

The authors apply Proteus to four SOTA memory architectures: SWLA (state-space with linear attention), Comba (convolutional-memory blend), Titans (Google’s neural memory), and Hope-Attention (hybrid attention-memory). On standard language modeling (WikiText-103, PG-19) and reasoning benchmarks, Proteus improves perplexity across all four architectures.

The pattern is consistent: the gains grow with context length. At 4K tokens, the improvement is modest. At 32K tokens, the gap widens substantially. At 128K+ tokens, the difference is largest—exactly where memory pollution should bite hardest.

On long-context retrieval tasks (NEEDLE, RULER, LongBench subsets), Proteus-augmented models recover information from later context positions significantly better than their static-memory counterparts. The early bottleneck doesn’t hurt early-position recall—it helps later-position recall by preserving capacity.

Limitations

Why You Should Care

If you’re building anything with long-context LLMs—RAG pipelines, agent loops, code analysis tools, document processors—you’re already fighting the pollution problem. Your model has a 128K context window but retrieves from the last 10% with disproportionate accuracy. Proteus suggests the fix isn’t a bigger window; it’s a smarter one.

The paper’s broader implication is that we’ve been optimizing the wrong thing. Every memory architecture paper focuses on the capacity of the state. Proteus shows that scheduling that capacity matters as much as its size. A consistent gain on long-context retrieval across four architectures is the kind of win you get for free—no new hardware, no bigger models, just a smarter allocation of what you already have.

For anyone who ships long-context systems: this is the simplest high-impact idea in the memory-model space this year. Watch the follow-ups—adaptive scheduling would close the loop.

Source: