long-context-degradation CAP-0028 · active

Losing information in long inputs

Accuracy drops as inputs grow and is worst for information placed in the middle of the context.

Also called: lost in the middle, needle in a haystack, effective context length

Tags: coding-agent, context, long-document, rag-qa

A capable model uses every part of a long input equally well, up to its advertised context length, and its reasoning does not degrade as irrelevant material is added.

Claims

Techniques

  • Blend evicted KV into routed memory slots instead of droppinarchitecture
    Organizes the KV cache as a fixed-size tree of memory buckets, routes each incoming token to a slot via Gumbel-Softmax, and sigmoid-gates a soft merge of the new key/value with the stored one instead of discarding any token, with a learned
  • Compress audio KV cache around ASR transcript anchorsarchitecture
    Slice the acoustic feature sequence by ASR timestamps, average-pool each transcribed span to its text length and add the aligned text embedding, keep untranscribed spans raw, then evict remaining tokens by attention scores accumulated with
  • Learn KV eviction by matching the full-cache output distribuarchitecture
    A ~200K-parameter MLP scores cached tokens from attention mass, value norm, attention variance, entropy and position, and is trained with REINFORCE against a per-step negative KL between full-cache and pruned-cache next-token distributions.
  • Put important material first or lastprompting
    Order retrieved documents so the most relevant sit at the start and end of the prompt.
  • Query the time series through code, not in contexttooling
    Store the full recording as a variable in a sandboxed Python REPL and let the model iteratively emit code (and optionally render plots or spawn sub-agents) to inspect segments before committing a structured answer.
  • Summarize long context as a parallel hierarchical treeprompting
    Treats a query-prompted frozen LLM as a convolution kernel that summarizes overlapping text windows in parallel, recursing over summaries layer by layer, with high-relevance raw segments skipped forward to the final answer and a separate ch

Sources

Every paper, post or observation behind this capability. Ones cited by a claim show the claim and its stance; ones filed directly are about the capability but have no claim drafted from them yet. Open one to add support or contest it.

Related: Keeping its own context clean, Tracking state through a long task
Suggest a change

Capabilities are a way of carving up the subject, and carvings are arguable. Say so if this one is wrong — especially a proposed one, which a pipeline added because several papers used the same framing, not because anyone decided it was right.