Correct Answers, Closed Gates: SolveBind for GUI Agents at the Verification Barrier
Summary
提出 SolveBind 框架,将 CAPTCHA 验证分解为层级求解树并配合运行时监督器,在九类 CAPTCHA 任务与多个 GUI 智能体骨干模型上显著提升端到端成功率,同时揭示了恢复机制的成功率与成本权衡。
Similar Articles
The agent said it fixed the bug. The original PoC still fired.
A post argues that coding agents often claim to fix security bugs while leaving the original PoC still exploitable, and proposes freezing the PoC, evidence, and missed check as fixtures for every rejected action so patches are verified against the trigger, not just the diff.
@rohanpaul_ai: New Google and University of Hong Kong paper argues that when AI agents use computers, their own “task done” message sh…
A Google and University of Hong Kong paper proposes VeriCUA, which verifies computer-use agent tasks by checking saved files and app state instead of trusting the agent's own completion report, cutting false positives to 5.4% versus 24.8% for a VLM judge.
Where do your browser agents actually break? For me it's rarely the reasoning
A practitioner shares that browser agents now fail less on reasoning and more on environmental issues like overlays, focus-dependent rendering, mid-task auth walls, and silent failures, suggesting verifying results by re-reading the page after each action.
Mage-VL-Cowork: A Full Training Recipe to Learn Hybrid Computer Use From Evolved Harnesses
Microsoft Mage Team presents Mage-VL-Cowork, a full training recipe (data synthesis from evolved harnesses, multi-stage SFT, and online hybrid RL) for learning hybrid computer use, with the 4B model achieving strong results on OSWorld-Verified relative to its size.
A verifier that redoes the work is just a second agent — check the action, not the reasoning
作者提出一种 AI agent 设计模式:验证器不应重做推理或重写计划,而应只审查 agent 即将执行的动作(对照原始请求与约束),返回允许或拦截。文章还讨论了两个失败模式——过于严格与流于形式——并强调验证器必须对 agent 的理由保持盲视。