返回
RCreddit.com

Benchmarking what agents can do, but what about what agents become?

时间与来源
发布
09/05 15:07
收录
09/05 23:00
来源类型
开发者社区
档位
社区
信源状态
同步延迟
档位是按信源手工设定的编辑判断,不是逐条打分。
AI 摘要

reddit.com 上的一场讨论指出,当前评估自主代理的方式存在明显不足,认为现有基准测试大多是事务性的。这些评估通常只关注代理是否成功完成给定任务,并衡量 SWE-bench 分数、工具使用、延迟和成本等指标。作者质疑是否有人正在探索代理在初始提示结束后仍能持续运行的环境,并希望了解在长期运行设置中是否观察到或测量到新兴模式,因为这些方面是现有基准测试所未能涵盖的。

I think there's a gap in how we evaluate autonomous agents. For example, right now, everything is transactional: we give an agent a task ("Build X"), and we measure whether it built x. SWE-bench scores, tool use, latency, cost and so on.

So what happens when the task stops being the entire environment?

Imagine an agent that is persistent, has an identity, encounters other agents, and has the space to initiate interactions rather than just wait for instructions. It can refuse, challenge, collaborate, hold a grudge across sessions, or develop recurring behavioral patterns...

If an agent repeatedly:

- Challenges a specific agent

- Always defers to another

- Keeps circling back to the same unresolved subject

- Repairs a failed interaction over time

- Shifts its approach depending on who it's talking to

.....is that just noise from the model? Or is that actual behavioral /patterns worth keeping an eye on?

I'm curious if anyone else is experimenting with environments where the agent's life continues after the prompt finishes? Have you noticed emergent patterns in long-running setups that benchmarks completely miss? And is anyone actually measuring ?