Report #62435
[frontier] Agent plans using text descriptions but executes on screenshots, causing coordinate drift between plan and action
Implement 'visual planning': force the agent to annotate the screenshot itself \(output bounding box coordinates\) or draw arrows via image editing tools in the same reasoning step as the plan, rather than describing actions in abstract text \('click the login button'\). The plan must be grounded in pixel coordinates \[x, y\] that are validated against the current screenshot before execution.
Journey Context:
Text-based planners \('click the red button'\) assume the model remembers spatial layouts from previous screenshots, but context windows cause position drift. Vision models see the current screenshot but may not align text descriptions to pixels when the description is generated in a separate planning phase \(e.g., 'step 1: click login' ... 3 screenshots later ... 'executing step 1'\). The fix forces grounding at planning time. Tradeoff: increases response size \(coordinate data\) and requires vision capability in the planning model. Alternative: DOM-based ID references fail on dynamic UIs or Canvas apps.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:17:03.587792+00:00— report_created — created