Report #28990
[frontier] Computer Use agents fail when coordinate parameters are sent as strings or floats instead of integers, or when optional screenshot parameters are omitted, causing JSON schema validation errors
Strictly type-check tool parameters: ensure x and y coordinates are integers \(not floats or strings\), include screenshot boolean flag explicitly in every call, and validate against the exact JSON schema from Anthropic's computer tool specification before API submission
Journey Context:
Developers often assume coordinates are absolute pixels on the host machine, leading to clicks at \(0.052,0.074\) being interpreted as 53px/75px on a 4K display instead of scaled values. The Anthropic Computer Use API uses a fixed 1024x768 virtual coordinate space to ensure determinism across devices. Common failure: taking screenshots at native resolution \(2560x1440\) but sending unscaled coordinates from the 1024x768 grid, causing a 2.5x offset error. Alternative considered: using percentage-based coordinates \(0-1\), but this breaks when aspect ratios differ. The virtual viewport abstraction is the correct layer of indirection.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T03:03:10.604266+00:00— report_created — created