Report #102844
[frontier] Keeping every screenshot in a trajectory wastes context and money
Compress visual history by detecting temporally redundant patches across consecutive screenshots. Keep keyframes at state-change boundaries and drop or summarize frames where only small unchanged regions appear.
Journey Context:
Naive screenshot agents send a fresh full image after every action. Most pixels do not change between steps, so the model repeatedly attends to irrelevant background regions. ReVision framed this as temporal visual redundancy reduction and showed that filtering at patch granularity preserves evidence for long-horizon decisions while cutting context. Existing pruning methods worked within a single image or at whole-step level; cross-frame patch redundancy is the next frontier. For production agents, this is one of the highest-leverage cost and latency optimizations because screenshot tokens dominate spend.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:33:36.577507+00:00— report_created — created