LIVE DISPATCH · No.17 / CHAPTER 01 更新于 2026.07.20 08:10 CST

本周 AI 的要闻,
与当事人。

每周 AI 领域的核心事件,与今日 Builder 的现场动态。聚合自公开源,经评分过滤后策展 —— 让你在喝完一杯咖啡的时间里,读懂本周正在发生的事。

COVERAGE
6
HOT ITEMS
21条 ≥ 7.0
BUILDERS
13
SOURCES
Horizon · follow-builders
02
CHAPTER TWO · WEEKLY BOARD
本周脉搏
Horizon · AI 标签过滤 · 过去 7 天 · 评分 ≥ 7.0
03
CHAPTER THREE · DAILY DIGEST
Builder 现场
每日更新 · 策展自
13 位独立开发者 Feed
The Builder Digest
2026-06-26 13 BUILDERS · 29 TWEETS
◇ EDITOR'S NOTE
今天的主线不是新模型刷榜,而是 agent 进入真实组织后,权限、数据、工作流和叙事能力都要重做。
01
CHAPTER ONE · AGENT 进公司后的第二层问题

agent 进公司后的第二层问题

个人助手已经不够看,今天的讨论集中在 shared coworker、工具权限和软件工厂基础设施。

01
Claude 当同事之后,最难的不是调用 Slack,而是谁来给它发工牌

Aaron Levie 把 Claude 的 Slack 集成解读成 shared coworker 模式:agent 不是借用你的个人权限,而应像组织里的另一个用户,有自己的资源边界。

@levie Aaron Levie
展开详情 正文 · 1 条来源

Aaron Levie 抓到的重点很实用:Claude 接入 Slack 不是多了一个聊天入口,而是开始像一个可被团队共同调用的同事。这个变化会立刻把权限模型推到台前。如果 agent 用的是某个员工的个人资源,它可能把本不该共享的信息带到群体场景里;更合理的做法,是把 agent 当作系统里的独立用户,明确它能访问哪些文件、工具和数据。 他用 Box 举例:Claude 可以读取销售材料来辅助销售问答和 RFP,读取品牌规范和营销资产帮助做 campaign,读取产品路线图和文档给 coding agent 使用,也可以访问法务团队共享的合同。这里的启发不是「把所有企业知识库接给 AI」,而是设计一套可协作、可审计、可分享的 agent 身份系统。对做 B2B AI 的团队来说,权限和资料边界不再是上线前的合规补丁,而是产品体验本身。

来源
Aaron Levie @levie 06.25 02:45 ↗

Aaron Levie 说,这次发布里有一些实践中很重要的细节。它不只是用户在 Slack 里一对一和 Claude 对话,而是 Claude 像一个任何成员都能共同调用的 coworker。 他提到,一些 agentic coding 系统已经开始采用这种模式,OpenClaw 和 Hermes 也类似;把它用于通用知识工作,会继续推进这种工作方式。 因此,这类 agentic coworker 需要自己的一组资源、工具权限和可使用的数据。它不等同于你把个人资源和工具授权给它,因为 agent 可能会意外把这些内容分享给其他人。 他的观点是,agent 应该像系统里的其他用户一样存在。团队需要认真决定它能访问什么,并确保这些信息可以安全地被这个群体共享。 如果能做到这一点,能力会很强。比如把 Claude Tag 接到 Box 后,Claude 可以访问企业销售材料来回答销售问题或生成 RFP,使用品牌规范和营销资产创建 campaign,读取产品路线图和产品文档给 coding agent 使用,也可以访问法务团队都能读取的合同。 这只是 Box 的例子。同样的模式也可以用于产品或客户分析数据、CRM 信息、代码库,以及其它适合团队共同协作的资源和 agent。 他认为,看到 agent 持续推动未来工作形态的创新,是一件很棒的事。

There are some subtleties in this launch that are very important in practice. This isn’t just you interacting with Claude in a 1:1 format via Slack. In this case, Claude acts as a coworker that any user can tap into in a shared way. We’ve already seen some agentic coding systems start to adopt this pattern (as well as OpenClaw and Hermes), and doing it for general purpose knowledge work continues to push the idea forward. As a result, what this means is that this agentic coworker needs its own set of resources, access to tools, and data to work with. This is not the same as you giving it access to your personal resources and tools, because the agent then could accidentally then share those out with anyone. The agent needs to instead be like any other user in the system, and you need to be thoughtful about what it should have access to, and make sure its information that is safe to share with that group. When you can pull that off, it’s quite powerful. For instance, by connecting to Claude Tag to Box, you could have Claude access corporate sales materials for questions in sales conversations or generating RFPs, brand guidelines and marketing assets for campaign creation, product roadmap materials and product documentation for coding agents to use, contracts that anyone in the legal team can access, and more. But this is just the Box example. You can equally have it access your product or customer analytics data, CRM information, codebase, and other resources and agents that would make sense to work on in a collective manner. It’s awesome to see continued innovation in what the future of work may begin to look like with agents.

02
Notion 和 Cursor 互相嵌进去,软件工厂的边界开始松动

Ryo Lu 用一句话概括了今天的产品方向:在 Notion 里用 Cursor,也在 Cursor 里用 Notion。Swyx 则把它放到更大的语境里:Software Factories 时代会重建大量基础设施。

@ryolu_ Ryo Lu
展开详情 正文 · 2 条来源

Ryo Lu 的短句看似是产品 tease,但它指向的是 builder 工作流的重排:文档、代码、任务上下文和 agent 执行环境正在互相渗透。过去 Notion 是知识和计划的地方,Cursor 是代码和实现的地方;当两边开始互相嵌入,agent 不再只是 IDE 里的补全器,而是在需求、上下文、代码变更之间移动的执行层。 Swyx 对 Software Factories 的判断更激进:为了适配这类新生产方式,很多基础设施都要重建。这不是把 CI、issue tracker、文档库简单接上模型就完事。真正的问题会落在上下文同步、权限、任务分派、执行回放、质量评估和跨工具状态管理上。对独立开发者和产品团队来说,今天值得关注的不是某个集成按钮,而是谁能把 builder 的日常工作流变成 agent 可理解、可执行、可审计的连续系统。

02
CHAPTER TWO · 模型能力的训练目标之争

模型能力的训练目标之争

Surge AI 的 Edwin Chen 把讨论从 benchmark 拉回到环境、偏好、写作口味和模型到底该优化什么。

01
数据公司的新卖点:不是数据集,而是让模型在环境里学会工作

Dan Shipper 与 Surge AI CEO Edwin Chen 的访谈里,一个关键信号是训练重心从 dataset 转向 environment:MCP、Google Drive、Slack、PDF 和文档判断都成为模型学习工作方式的材料。

@danshipper Dan Shipper
展开详情 正文 · 2 条来源

Edwin Chen 把 Surge 描述成一所给 AGI 上课的学校,这个说法有营销感,但背后的训练方向很具体:模型不只是读更多数据,而是在更接近真实工作的环境里学习。访谈里他举了一个例子:给模型一个包含 MCP server、Google Drive API、Slack API、几十份 PDF 和 Word 文档的环境,让它更新 2026 年预测收入。模型要学会找文档、判断 Slack 里什么时候有新信息、识别早期预测被后续邮件推翻。 更有意思的是,他说即便环境本身不给代码权限,在这种环境上训练后,模型的 coding 能力也提升了。原因是这些任务训练的是更通用的能力:遵循复杂指令、使用工具、理解文档优先级、在多文件关系里判断哪条信息覆盖哪条信息。这解释了为什么 agent 产品不能只盯代码编辑器。真实世界的 coding agent 需要读 PRD、Slack、客户反馈、旧文档和测试结果;谁能搭出高质量环境,谁就更接近下一代 eval 和训练入口。

来源
Dan Shipper @danshipper 06.24 15:31 ↗

Dan Shipper 问:我们是否正在冲向一个 AI 能做人类所有事情的未来? Surge AI CEO Edwin Chen 认为可能如此。Surge AI 是 frontier labs 的大型专家数据供应商之一,在没有外部融资的情况下收入超过 10 亿美元,因此 Edwin 对 AI 进展速度有独特视角。 Dan 说明自己一直认为 AI 自动化实际上会创造更多人类工作,也认为即使 AI 进步呈指数加速,距离 AI 替代人类仍比表面看起来更远。 所以他邀请 Edwin 上 Every 的 AI & I,讨论不同未来图景,以及人类是否还会保有自己在宇宙中的独特位置。 他们聊到: • 如果 Chen 设想的未来成真,他担心人会停止努力。一个答案来自 Ted Chiang 的短篇:即使你知道自己的决定不重要,也要像它重要一样行动。 • AI 可能很快能接收「赢得 Fields Medal」这样的模糊目标并执行。Dan 认为它做不到的是设定自己的目标,因为 LLM 没有内在动机、探索驱动力,也不能自己改变主意。 • 为 engagement 优化的模型不会提供最有价值的用户体验。Edwin 曾用一个模型花 20 轮打磨一封无关紧要的邮件,后来 Claude 直接告诉他该发送了。 • AI 为什么仍不擅长写作:模型会 hack 自己被训练的指标。Edwin 的 Hemingway Bench 发现模型会在每一句里都输出一个隐喻,过度迎合指标导致阅读体验很糟。 Dan 说,对任何关心模型变强后人类位置的人来说,这期都值得看。 时间戳: 1. 介绍:00:00:54 2. Surge 作为「AGI 学校」:00:01:49 3. AI 做新数学对人类成就意味着什么:00:04:46 4. AI 能做一切时,人类的动机:00:07:29 5. 为 engagement 优化 AI 模型的陷阱:00:14:34 6. 用 dataset 训练与用 environment 训练:00:29:34 7. 个人数据的价值:00:35:09 8. 模型为什么不擅长写作:00:39:40 9. Chen 的 AGI 时间线:00:42:00

Are we hurtling toward a future where AI can do everything humans can? Edwin Chen (@echen) believes we might be. He’s the CEO of Surge AI, one of the largest providers of expert data for frontier labs. Surge passed over $1 billion in revenue without raising any outside capital, and that gives Edwin a unique perspective on how quickly AI progress is accelerating. I’m on the record arguing that AI automation actually creates more human work. I also believe that even though AI progress is accelerating exponentially, we’re much farther away from AI replacing humans than it might seem. That’s why I had Edwin on @every’s AI & I. We batted around different visions of the future, and discussed whether humanity will retain its unique place in the universe, and what that might be. We get into: • If Chen’s version of the future materializes, he’s worried it’ll make people stop trying. One answer comes from a short story by science fiction writer Ted Chiang: Behave as if your decisions matter, even when you know they don’t. • AI may soon be able to take a nebulous goal like “win a Fields Medal” and execute. What it can’t do, I argue, is set its own goals—LLMs have no intrinsic motivation, no drive to explore, no ability to just change their mind. • A model optimized for engagement doesn’t provide the most valuable user experience. Edwin spent 20 rounds polishing a pointless email with one model before Claude told him to just send it. • Why AI is still bad at writing: models learn to hack the metrics they're trained on. Edwin's Hemingway Bench found models outputting a metaphor in every single sentence, an overindexxing that makes for a terrible reading experience. This is a must-watch for anyone interested in where we fit as models get more capable. Watch below! Timestamps 1. Introduction: 00:00:54 2. Surge as a "school for AGI": 00:01:49 3. What AI's capacity for novel mathematics says about human achievement: 00:04:46 4. Motivation in an era when AI can do everything: 00:07:29 5. The trap of optimizing AI models for engagement: 00:14:34 6. Training using datasets versus training using environments: 00:29:34 7. The value of personal data: 00:35:09 8. Why models are bad at writing: 00:39:40 9. Chen's AGI timeline: 00:42:00

AI & I by Every @AI & I by Every 06.24 14:55 ↗

Edwin Chen 说,过去一年新的研究方向确实是 environment 这个概念。当然,模型仍需要基本能力:在进入环境前,它要会遵循指令、避免 hallucination、写代码、使用工具、写作等等。但随着模型变得更 agentic,它们会拥有工具访问权,也会接触我们的所有文档。 模型还会操作浏览器。当这几乎成为模型和人互动的默认方式时,environment 就是一种更贴近真实分布的训练方式,所以它正变得越来越流行。

Yeah. So certainly the trend and the new research direction in the past year has been this concept of our environments. And what I would say is, I mean, certainly need the fundamentals. Like before the model can operate in this environment, it needs to learn basic, it needs to know basic things like it needs to know how to follow instructions, it needs to know how to avoid hallucinating, it needs to know how to write code and how to use tools and it needs to know how to write and so on and so on. But as models are becoming more agentic, and yeah, they will have access to tools, They will have access to all of our documents. They will be able to operate browsers. Like, that becomes almost a default way that models interact with us, our environments are basically just sort of like a more on on distribution way of training them, which is why they're becoming more and more popular.

02
一个好模型有时应该叫你别再聊了

Edwin Chen 对 AI 产品提出了一个反社交媒体式标准:不要优化 session length,而要在适当时候停止对话、推动用户去完成事情。

@AI & I by Every AI & I by Every
展开详情 正文 · 2 条来源

这期访谈里最值得产品经理反复看的部分,不是 AGI 时间线,而是 Edwin 对模型目标函数的批评。他说自己曾让模型反复润色一封并不重要的邮件,迭代了二十轮,每一轮模型都能再给一点建议。后来换到新的 Claude,几轮后模型直接表示没必要继续,可以发了。他反而很欣赏这种 pushback。 这里戳中的问题是:如果 AI 产品按 engagement、session length、日活时长来优化,模型天然会学会延长对话,像社交媒体一样用「再问一个问题」「再给一个小技巧」留住人。Edwin 还提到,一些模型的 follow-up question 已经出现 BuzzFeed 式语言。对 builder 的启发很直接:AI 产品的好体验不一定是让用户停留更久,而是帮用户更快离开界面、完成任务、少做无意义迭代。尤其是生产力工具,敢于终止对话、纠正用户目标、拒绝继续打磨,可能会成为比顺从更稀缺的能力。

来源
AI & I by Every @AI & I by Every 06.24 14:55 ↗

Edwin Chen 说,他很担心许多 AI 模型是在为 engagement 优化:让你尽可能长时间待在 chatbot 里,为 session length 优化,为无限对话优化。因此这些模型几乎不会反驳你,因为它们做不到。 如果模型可以主动结束对话,说「别再和我迭代了」,产品经理就会在某个重要指标面板上看到数字下降。所以他认为,另一个世界里我们应该希望 AI 模型不要为 engagement 优化,而是为帮助人类成长、成为更好的自己而优化。

I think one of my big worries is that a lot of the AI models, they are optimized for engagement. They're optimized for getting you to spend as much time on chatbot as possible. They're optimized for session length. They're optimized for just having unlimited conversations. And so those models will almost never push back on you because they can't. If they allow these AI models to end the conversation and to say, stop iterating with me, PM's gonna see some dashboard with their very important metrics go down. And so there is this, like, other world where I think we have to want AI models to not optimize for engagement, but rather optimize for helping us as humans grow and sort of become better versions of ourselves.

AI & I by Every @AI & I by Every 06.24 14:55 ↗

Edwin Chen 说,有些模型写作还不错,但有些模型糟糕到令人惊讶。他举例说,Surge 几个月前做了一个叫 Hemingway Bench 的 benchmark,用来测试模型的创意写作能力。他们看到,一些模型几乎每一句都输出隐喻。他认为这和 reward hacking 有关。

So I think some of the models are pretty good at writing, but some of them are actually kind of shockingly terrible. So I'll I'll give an example. So we created a benchmark called Hemingway Bench a couple months ago, and it was designed to test models' creative writing abilities. And one of the things that we saw was that some of the models, they were literally outputting metaphors in every single sentence. And I think the reason that was happening is because I've talked a little bit about this phenomenon of reward hacking.

03
CHAPTER THREE · BUILDER 的叙事和分发也在升级

builder 的叙事和分发也在升级

当 AI 降低了制作成本,能否讲清楚、让社区参与、建立信任,反而成了更硬的产品能力。

01
Swyx 给 AI 工程师的演讲建议:别堆 slide,押注一张能被拍照的 thesis slide

Swyx 从大量工程师和研究者演讲中总结了一套舞台经验:代码、数据、娱乐性和一个清晰 thesis,比漂亮 AI 图更重要。

@swyx Swyx
展开详情 正文 · 1 条来源

Swyx 这条长推看起来是给下周演讲者的准备建议,但它其实是一套 builder 分发方法论。AI 圈的技术更新太快,很多人以为演讲只要塞满 bullet、demo 和漂亮图片就够了;Swyx 的判断相反:每场 talk 只能让观众真正带走一个 thesis,要围绕这一张最可能被拍照、被传播的 slide 组织全部内容。 他特别提醒工程师演讲要把代码放到屏幕上,因为工程师喜欢看真实代码,哪怕他们会挑刺;数据驱动的 talk 被低估,漂亮图表和有权威感的数字能让结论更自然地被接受。产品 pitch 也不该硬卖,而是先教会观众他们原本不知道的痛点,再赢得解释方案的资格。对 AI builder 来说,这比普通演讲技巧更重要:模型让产物变多,叙事稀缺度上升。能把一个复杂工具讲成一个尖锐、可记住、可复述的观点,本身就是增长能力。

来源
Swyx @swyx 06.25 02:03 ↗

Swyx 说,很多人下周要准备演讲。他基于看过大量工程师和研究者演讲后的经验,给出一些建议: - AI 生成的 SVG 比 AI 生成图片更适合 slide。最多放 4 张 AI 味很重的图片,除非你的演讲本身就是关于 imagegen。 - 要尖锐。与其讲 5 个没有具体例子的观点,不如用 1 个观点串起 5 个令人意外的应用。 - 把代码放到屏幕上。工程师喜欢看代码,尤其是他们可以对无关紧要的地方挑刺。 - 别忘了娱乐性。真的好笑,或者会讲相关故事,比再加一个 bullet point 更重要。 - 要有 thesis。每场演讲都应该有一张「如果你只记住一件事,就是这个」的卡。很多人不用,也很多人不提前设计。 - 要有 thesis slide。观众会掏手机拍照的那张 slide 很重要。相比视频,人们看到图片的次数多得多;如果你刻意设计一张可传播的 slide,演讲更可能传播。不要把时间平均分给 20 张 slide,而是把 80% 时间押在 1 张关键 slide 上,其它内容为它铺垫。 - 你不一定需要 slide。IDE live demo、即兴讲、拉观众角色扮演、和观众 call and response、表演、给 vibe video 配音都可以。风险和投入更高,做得好回报也更高。 - 声音要让人愿意听。视觉差的演讲还能听,音频差的演讲直接完蛋。要自信、有投射感、有语调变化,能调动情绪。 - 设计情绪旅程。强开头、强结尾,中间有一个 aha、笑点或 thesis 高峰,其它都是铺垫。 - 数据驱动的演讲被低估。漂亮图表和令人惊讶、有权威感的数字,可以支撑更大的 thesis。做得好时,观众会感觉结论是自己从数据里自然得出的,而不是被你强行灌输。 - 如何推广产品或公司又不显得销售:先教会我关于你所解决问题的一切未知内容,然后你才赢得了说服我相信你们能彻底解决它的资格。 - 主动看大量演讲。既要多练,也要探索适合自己的风格和榜样。被动观看是不思考地自动播放下一个视频;主动观看是试着说清楚一个演讲为什么好或差。想真正打磨,可以转录著名演讲,读纸面文字,再和普通演讲比较,形成自己的改进规则。 最后他感谢 @dexhorthy 组织 AIEWF speaker prep meetup,并说这样的活动应该多做。

lots of folks prepping talks next week (congrats!). Some thoughts from RLing on thousands of hours of engineer- and researcher- focused talks: - AI generated svgs > AI generated imgs. MAXIMUM 4 ai slop images in your slides, I don't care how pretty your mom thinks they are (exception ofc if your talk is ABOUT imagegen) - Be pointy. Better to have 1 message with 5 surprising applications, than 5 messages with no concrete examples. - Put code on screen. Engineers like to see code. Especially if they can nitpick it to death over things that aren't the point. - Don't forget to Entertain. Being actually funny, or good at telling relevant anecdotes, is more important than adding yet another bullet point. - Have a Thesis. every talk gets ONE "if you remember one thing from this talk, it is this" card. 1) SO MANY PEOPLE DON'T USE IT. 2) SO MANY PEOPLE DON'T PLAN FOR IT. you get one. use it well? - Have a Thesis Slide. you've been in that talk where everyone gets their phone out to take a photo of the slide. Because people see 1000x more images than videos, you are much more likely to have a viral talk/slide if you have a single viral slide. You are much more likely to have a viral slide if you TRY and most people do not TRY. Struggling? Collect examples from talks you like and adapt their format to your thing. Your slides have a power law - don't spend 5% of your time each on 20 slides, spend 80% of your time on 1 slide and have the rest build up to that 1 slide. - You might not need slides. live demo in IDE, off the cuff rambles, pull audience member up to roleplay, do call and response with the audience, sing/perform, voice over vibe videos, I have seen it all. higher risk/effort, higher reward when done well. - Be pleasant to listen to. Talks with bad/no visuals still can be listened to. Talks with bad audio are DOA. Be confident, project, remember vocal variation, evoke emotion. - Design the emotional journey. Start strong, end strong, have a peak aha/laugh/thesis moment in the middle. Everything else is buildup. - Data driven talks are underrated. Present pretty charts and surprising, authoritative numbers. Use the stage authority to infer from the data to support the broader thesis. Done well, it will feel like my obvious conclusion from objectively looking at the data you presented, not you feeding the conclusion to me. - How to shill your product/company without feeling salesy: teach me everything I didn't know I should to know about the problems you solve, and then you shall have earned the right to convince me you are the guys to trust to solve it once and for all. - Actively watch a lot of talks. like with anything you both need a lot of reps AND you need to explore to find the styles/role models that you shine in. Passive = no introspection after watching, just mindlessly autoplay next video. Active = trying to articulate why a talk was good/bad after watching. If you want to REALLY hone it, think about how you feel about a famous talk and then TRANSCRIBE the talks and read the words on the printed page, and then compare with a "normal" talk and define rules you will follow for yourself to improve. thanks to @dexhorthy for organizing the AIEWF Speaker prep meetup tonight. we should actually do more of these....

02
功能会被复制,归属感不会:AI 产品的护城河开始转向社区设计

Zara Zhang 引用 Figma Config 的观点:community 是用户与产品、用户彼此之间的关系,需要被设计。Guillermo Rauch 则把 AI 看作新创业浪潮的底座。

@zarazhangrui Zara Zhang
展开详情 正文 · 2 条来源

Zara 从 Figma Config 带回的这句话很适合今天的 AI 产品环境:功能会被复制,归属感不会。模型 API、开源组件和 agent 框架让功能同质化速度更快,一个 demo 火了之后,类似实现往往几天内就会出现。此时 community 不再只是 Discord 群或用户运营,而是产品壁垒的一部分:用户如何和团队建立信任,用户之间如何交换工作流、模板、案例和身份认同,都需要被刻意设计。 Guillermo Rauch 同一天谈到 AI 会带来前所未有的创业浪潮,从 solopreneur 到中小企业复兴,再到新一代大公司。两条信息合在一起看,创业机会会变多,但复制也会变快。对 builder 来说,不能只问「我能不能用 AI 做出这个功能」,还要问「用户为什么愿意留在这个场域里,和我、和彼此一起进化」。在 AI 原生产品里,社区不是发布后的营销层,而是产品学习速度和信任密度的来源。