Technology

context compression

2 synchronized stories carry this tag.

A controlled study isolates coding-agent harness effects

A preprint and MIT-licensed Yuj harness compare the same coding model under a full chronological context against a treatment that compresses older tool output and intervenes on repeated or stalled work. Under a 20,480-token window and fixed 480-second endpoint on 169 SWE-bench Verified tasks, complete solutions rose from 43 to 72; the frozen treatment was also tested with three additional model designs.

Why it matters: Coding-agent scores can move materially without changing model weights. Model selection, procurement, and safety evaluation therefore need to name the harness, context policy, tools, recovery rules, runtime limits, and verifier as part of the tested system.

Read storyOriginal source · arxiv.org

Headroom 0.36.4 closes upstream-validation paths in its agent proxy

Headroom 0.36.4 changed its proxy to validate caller-supplied upstreams on every resolution path. The same release preserved Codex additional-tools payloads and corrected streaming behavior; 0.36.5 followed later on 22 August with ChatGPT-auth detection and Claude-routing diagnostics, making 0.36.5 the current patched line for this dated event.

Why it matters: Headroom can sit between coding agents and model providers while handling prompts, tool output, memory, and credentials. Incomplete upstream validation at that boundary can route sensitive traffic somewhere operators did not intend, even though the release…

Read storyOriginal source · github.com