创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

Anthropic 发布常驻型智能体架构指南

AI 总结

Anthropic 的《Building always-on agents》是一份设计指南,并非功能发布。指南将具备状态且可主动行动的智能体拆分为事件收件箱、定时器、记忆、权限和发件箱五个基本组件;每次运行会读取记忆、在权限范围内行动、更新状态并发送消息。Anthropic 还称近期模型进步提高了这一模式的实用性,并援引一项厂商自报数据称,在某项长时程编程基准中,Opus 5.5 每个已解决任务的成本比 Opus 5 低 78%。

深度见解

该指南为开发者提供了构建跨会话保留状态,并能由事件或计划唤醒的智能体的具体架构方案。

Over the past few months, we’ve seen a resurgence of always-on agents.

Always-on agents are stateful and proactive, meaning they manage context across sessions and take actions without direct supervision. Underneath, they run on the same core loop as other agents. The difference is the surrounding architecture, which is built from primitives that control when the agents wake up, what carries over between runs, and how their work reaches the user.

The resurgence is largely due to recent model advancements, which have made always-on agents more practical to run. First, the latest models have better judgment: they’re more reliable at understanding user intent and knowing when to check in. Second, intelligence is becoming cheaper, with long-horizon tasks benefiting the most. For example, on one long-horizon coding benchmark, Opus 5.5 cost 78% less per solved task than Opus 5, compared with 40% less on typical workloads.

Customers have started to ask us how to integrate this type of experience into their own products. Some companies want to make their existing agents more proactive, while others are looking to build them from the ground up.

#Anthropic#Claude#Claude Code#Messages API#Opus 5.5#Opus 5

原文约 11 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。