/p/2026-10-17 · explainer
Paper explainer · 2610.21073 · Yang, Chatterjee, Udupi, Ramavarapu and Zhai

The compressor kept the tokens and lost the patch.

A repository does not fit in a context window, so something gets cut: you compress the text, or you retrieve the chunks that look most like the issue. Hold the budget fixed across 300 real issues and both lose to the dullest option — work out which whole files matter and paste them in untouched. That resolved 43.7% and 46.7% of issues on two models, against 30.0% to 40.3% for the best compressor, and the reasons are mechanical: a chunk retriever often never shows the file that has to change, and a compressor shows it rewritten, so the patch the model writes no longer matches the file on disk.

01 · The problem

Something gets cut before the model reads a line

how the budget was filled

02 · The mechanism

A retriever can miss the file; a compressor can only break it

03 · The evidence

One budget, ten ways to spend it

which model wrote the patch

04 · Why I care

The damage is in cutting inside the lines

same candidate files, different cut

how the files were chosen

05 · Apply it

Your budget, your repository illustrative

what you do when it will not fit

Results

What the paper actually measured

What it does not show

In practice