You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Researchers introduced StateAct, a multi-agent framework that prioritizes reading program state (files, DOM, app backends) over screenshots for computer-use tasks. A dedicated GUI subagent handles only the ~1% of steps genuinely requiring visual interaction. On OSWorld benchmarks, StateAct lifts Claude Opus 4.8 from 20.6% → 26.9% binary task success while cutting cost by ~9x compared to screenshot-driven agents.
⚙️ What It Means for Agentic Workflows
Tool selection matters more than model size: routing tasks to code/state inspection first — and only falling back to visual tools when necessary — dramatically reduces token cost and latency in automation pipelines.
Design your agents with a "code-first, GUI-last" hierarchy: for workflows that interact with structured systems (APIs, filesystems, browsers), avoid vision tools unless the target is truly unstructured UI.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
🔬 The Finding
Researchers introduced StateAct, a multi-agent framework that prioritizes reading program state (files, DOM, app backends) over screenshots for computer-use tasks. A dedicated GUI subagent handles only the ~1% of steps genuinely requiring visual interaction. On OSWorld benchmarks, StateAct lifts Claude Opus 4.8 from 20.6% → 26.9% binary task success while cutting cost by ~9x compared to screenshot-driven agents.
⚙️ What It Means for Agentic Workflows
🔗 Source
StateAct: Program State, before Pixels, for Long-Horizon Computer-Use Agents — July 28, 2026
All reactions