赋予代理“眼睛”以观察视觉差异
1 分•作者: jsfez•3 个月前
代码编写代理在编写代码方面已经相当出色了，但它们仍然无法验证是否破坏了用户界面。<p>作为人类，我们依靠视觉差异来做到这一点。我们打开它们，快速扫描，并捕捉明显的回归。代理完全脱离了这个循环。<p>我是 Argos（视觉测试）的联合创始人，最近发布了一个 CLI，以代理实际可以使用的方式展示视觉差异，而不是通过用户界面。<p>一旦我将其连接到代理工作流程中，一些有趣的事情就开始发生了。代理开始捕捉明显的回归。有时它会拒绝批准自己的 PR。在良好的提示下，它甚至在看到差异并迭代后修复了问题。<p>它仍然粗糙，并且不够可靠，无法单独信任。很大程度上取决于代理对代码库的理解程度。在本地测试中，它有时会陷入循环并耗尽 token。<p>让代理“看到”用户界面更改，这可能为未来更自主的开发代理提供一个有趣的反馈循环。
查看原文
Coding agents are getting pretty good at writing code, but they still have no way to verify if they break the UI.<p>As humans, we rely on visual diffs for that. We open them, scan quickly, and catch obvious regressions. Agents are completely out of that loop.<p>I’m a co-founder of Argos (visual testing), and I recently shipped a CLI to expose visual diffs in a way an agent can actually use, instead of going through a UI.<p>Once I wired it into an agent workflow, a few interesting things started happening. The agent started catching obvious regressions. Sometimes it would refuse to approve its own PR. With a good prompt, it even fixed the issue after seeing the diff and iterating.<p>It’s still rough and not reliable enough to trust on its own. A lot depends on how well the agent understands the codebase. In local tests, it sometimes gets stuck in loops and burns through tokens .<p>Giving agents “eyes” on UI changes might be an interesting feedback loop for more autonomous dev agents in the future.