咕噜纪

博主雷达 / @hwchase17

Harrison Chase

Harrison Chase

AI开发者与产品

@hwchase17

粉丝 13.6万关注 599最近同步 10/19 20:37雷达库已收录

CEO、联合创始人 · LangChain

去 X 主页

粉丝趋势近 30 天

10-12 → 10-19:+1,441最高 13.6万 · 最低 13.4万

近 7 天

数据积累中

情报贡献参与 0 条已上架情报 · 首发 0 条

无数据

最近帖子最多 20 条

Harrison Chase

大部分有意思的 agent harness 工作都发生在 harness 和 infra 的交叉点上: 1/ dreaming 2/ 异步子 agent 3/ 心跳 4/ 让 agent 安排提醒 这也是我看好托管 agent 平台的部分原因! 这些全都在托管的 deep agents 里!

机器翻译
Harrison Chase

编程智能体(Claude code、codex)-> 个人智能体(instinct、muse)-> 公司操作系统(???)

机器翻译
Yohei@yoheinakajima

after switching our approach to building a "FirmOS", I'm increasingly confident that the future of agent collaboration within organizational settings is going to be a "company operating system" or CompanyOS, designed for agent and human collaboration instead of a "company brain" that holds everything, the OS is for storing rules, processes, decisions made, which tools to use and how. it can mirror some data, but the source of truth is often best held in your existing tools (CRM, etc.). it's continuously updated and used by your agents i think of this as a "flipped playbook" where instead of writing down the company rules first and following them (which is kind of like waterfall development), you're constantly updating the playbook as you decide or learn new things day-to-day running the business

查看被引用的帖子
Harrison Chase

路由器住在 harness 里,而不是网关里,因为 harness 知道任务是什么 博客:langchain.com/blog/how-to-build-a-model-router-in-the-harness x.com/neil_xbt/status/2109979966859510156

机器翻译
NeilXbt@neil_xbt

LangChain gave its coding agent three models and a router. Open SWE, their open-source coding agent, now sends each thread to the cheapest model likely to finish the job. they tested it on 973 threads, half routed and half always on GPT-6 Astra. median cost per thread: $0.94 against $2.61. that's 64% lower. threads ending in a merged PR: 29.2% routed, 27.3% on Astra. LangChain's p-value for that gap is 0.49. the router sent 56% of threads to the balanced model, 34% to the fast one and 10% to the performance one. they also tried always using the fast model. that test ended within a day, because engineers reported low output quality. LangChain's own caveats: the control was the most expensive model, and the router is a proof of concept. Which three models would you put in the tiers?

查看被引用的帖子
Harrison Chase

我们正在大量思考如何让 deepagents 更加异步原生。具体来说,就是如何让异步子代理工作得更好、更突出 一个关键问题是:一个已完成的子代理如何“通知”父代理?我们正在考虑一些默认行为,用于父代理仍在运行时的场景: 1/ 中断父代理运行,应用子代理更新,然后继续(基本上等同于“steer”) 2/ 等待父代理运行结束,然后把子代理更新与其他新消息一起批量处理(基本上等同于“queue”) 另一个问题是如何处理 human in the loop?如果主代理没有在运行,而是暂停了,正在等待人类对某个操作的明确回应,该怎么办? a/ 等待人类回应,然后把子代理更新与那个回应一起批量处理 b/ 用子代理更新恢复线程(这会取消人类中断)(线程之后可以重新请求同一个人工批准) 还有我们漏掉的其他选项吗?

机器翻译
Harrison Chase

哈哈,上周我把这个观点分享给了我们团队 很快会分享一些我围绕这个随手写(非常基础的)东西 这里有很多值得探索的!

机器翻译
Nicolas Bustamante@nicbstme

One of my more controversial bets: the AI feed will be the form factor of 2027! Most people don’t know what to prompt, and they won’t prompt their way into complicated agentic workflows. With chat, we ask users for digital labor: figure out what AI can do, explain the task, provide the context, repeat. That’s a lot to ask if we want billions of people using agents every day. Meanwhile, people already spend hours in feeds. Twitter, Instagram, LinkedIn. They know how to scroll, discover something useful, and act on it. An intelligent system that knows you should bring you the next useful action. Here’s the email you need to answer, already drafted. Here are the latest sales numbers, with an update ready to send to your team. You approve, edit, dismiss, or jump into chat to go deeper. That’s how people will discover what agents can do, without having to invent a prompt first. And you can put ads in a feed, one of the biggest business models on the internet. A system that understands your plans can recommend a relevant restaurant, product, or service, clearly labeled as sponsored. You get a reason to come back every day, useful work ready to approve, and a business model to fund the agents doing it.

查看被引用的帖子