创建

登录 ReadmeX

或

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

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

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

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

资讯

LangChain提出智能体“目标工程”框架

AI 总结

LangChain认为,智能体的能力正从文本生成、工具调用和决策,扩展到执行完整任务并追求开放式目标,Hone被其作为这一方向的案例。文章建议为智能体定义优化指标,并围绕便于人类提供高质量反馈的范围进行设计。Actively AI将原先按客户账户设置的智能体重构为基于Deep Agents的可复用销售“motions”,同时由后台智能体汇总账户信息。

深度见解

LangChain将人类反馈与审查流程置于智能体设计的核心,认为处理主观和长期目标时,智能体必须便于专家纠错并复用这些反馈。

The scope of tasks that agents can take on has increased drastically over the past few years. They have gone from simple text generation to tool calling and decision making to executing full tasks. The future of agents is them taking on open ended goals and driving towards completion of those goals. Launches like that of Hone give us a glimpse into that future.

In this world, designing the scope of agents is crucial. Point them in the wrong direction, and you’ll get a lot of wasted tokens. A key part of the Hone agent set up is defining metrics for them to optimize.

How to design goals

As we’ve worked on similar styles of agents, we’ve realized something about designing the scope for agents: you want to design the scope of an agent such that it makes it as easy as possible to give feedback as the agent operates within that scope.

Why is this?

When agents mess up, a big reason they mess up is lack of right context. In order to fix this, you need to give the agent the right context. There are different types of context. Some types of context are things like access to the right documents or APIs - that is relatively easy to fix. The trickiest context to give the agent is context that is not written down anywhere already. This context needs to be given to the agent as feedback from a human expert.

#LangChain#Actively AI#Hone#Deep Agents

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

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