Report #77679
[frontier] Multi-Modal Context Interference from Dense OCR Noise
Separate Visual Scratchpad: Use vision model first to extract structured JSON representation of UI elements \(type, bounding box, text\) with enforced schema via Structured Outputs, then pass only that JSON \(not raw OCR text dump\) to the reasoning LLM to prevent text hallucinations.
Journey Context:
Feeding raw OCR output from screenshots into text context causes severe hallucination: the model invents UI elements that look like text but don't exist \('mirage buttons'\), or misses critical elements obscured by OCR noise. The naive fix of 'better OCR' \(e.g., GPT-4V native text detection\) still injects unstructured dense text into the context window, interfering with chain-of-thought reasoning. The emerging architecture is a strict separation: a Vision Module \(GPT-4o/Vision\) outputs structured JSON \(e.g., \{'elements': \[\{'id': 1, 'type': 'button', 'text': 'Submit', 'bbox': \[x,y,w,h\]\}\]\}\) using Structured Outputs/JSON mode. This JSON becomes the 'visual scratchpad' for the Agent Reasoning Module \(Claude 3.5 Sonnet/etc.\), which never sees raw pixels or OCR dumps. This eliminates hallucination and reduces token count by 80%.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:58:45.338135+00:00— report_created — created