初创公司Paperboy融470万美元 押注系统层数据重构AI交互

人类和 AI Agent 的最佳配合方式,还没被发明|对谈 Paperboy — 十字路口Crossing

十字路口Crossing

现有的会话式Chatbot并非最优解,人与Agent配合的最佳方式需要通过收集操作系统多模态数据、构建持久且具主动性的通讯化界面来实现。

AI-assisted summary of 人类和 AI Agent 的最佳配合方式,还没被发明|对谈 Paperboy — original source. Check the original for full context.

Source published:

Detailed notes

## Background 这期节目由播客频道“十字路口Crossing”于2026年5月20日在Web/RSS平台发布。节目简介指出,本期对话了融资470万美金、由12人组成的Paperboy创业团队,共同探讨人类与AI Agent在工作流中更自然、更可协作的全新交互配合方式。

## TL;DR 本期节目深入探讨了当前AI Agent产品基于会话(session-based)与被动触发的痛点,并详细介绍了Paperboy如何通过操作系统(OS)层面的多模态数据收集来构建超长持久上下文。两位年轻的创始人分享了团队内部诸如“Mini Vivian”等主动型Agent的实际应用、对未来全新人机交互界面(The Last Interface)的思考,以及面对大厂竞争时小团队凭借产品品味、独立性与高密度人才建立壁垒的创业思考。

## Atmosphere & style 整期节目呈现出一种高能量、极具极客浪漫与精英主义色彩的对话氛围。年仅21岁和19岁的年轻创始人操着流利的中英夹杂语言,在真诚坦率的自嘲(如大方承认公司每天都在亏钱)中,透露出极强的逻辑思辨能力与对产品细节的极致追求;主持人与嘉宾之间的互动高频且高带宽,既有对技术前沿的硬核拆解,又充满了年轻人特有的无畏、热烈与对“躺平未来”的幽默遐想,让人能清晰感受到初创团队在AI大潮中狂奔的兴奋感与笃定感。

## Key takeaways - `01:59` 人类和 AI Agent 配合工作的最佳方式很可能还没被发明,现有的 Chatbot 和 Agent 存在基于会话(session-based)与被动触发(reactive)两大根本性痛点。 - `01:43` Paperboy 的融资情况为以 2500 万美元的估值融了 470 万美元,团队规模 12 人,包含 10 位工程师,目前每天都在亏钱。 - `04:10` Agent 赛道的解决空间可划分为三个维度:环境集成与学习(Context)、个性化与可靠性(Personalization & Reliability)以及极简且直觉的设计(Design)。 - `11:13` 从操作系统(OS 层)层面去抓取和收集用户数据是获取高浓度上下文(Context)的最佳方式,比单纯导出微信或 iMessage 数据更具扩展性。 - `21:55` 通过 OS 层的全局上下文聚合,可以实现跨应用的文本自动补全(Autocomplete),效果显著优于 Cursor 或 Copilot 等局限于单一应用的工具。 - `16:21` 团队开发出 Mini Vivian 和 AutoJong 等专属 Agent 分身,能够深度理解用户的品味与判断力,从而在 Slack 里处理招聘和工作交接。 - `28:13` Paperboy 放弃了最初的“AI Slack”概念,因为企业替换 Slack 的数据迁移成本极高,且单纯靠聊天信息无法为 Agent 提供足够的自然上下文。 - `25:00` Paperboy 的界面设计受到微信多群聊机制的启发,通过将产品打造成 IM 式的收件箱架构,解决了为不同角色定制复杂侧边栏的难题。 - `33:37` 产品的速度层级设计(如 The Last Interface)受到 Long Now 基金会“节奏分层”(Pace Layers)理论的启发,需根据用户的行动时间跨度来匹配 Agent 的形态。 - `37:28` 作为初创公司,市场选择至关重要,理想的市场必须具备能够支撑起十年期产品线演进的持续复利能力,而非仅仅看眼前的变现价值。 - `41:14` Paperboy 的工程团队由两种画像构成:一种是高 IQ 且具备极强创造力的快速原型开发者,另一种是来自 AWS 等大厂、深谙操作系统内核的系统专家。 - `45:00` 在招聘顶尖人才时,创始人的成长斜率(Slope)往往比初始截距(Intercept)更重要,而考核候选人最核心的是看其过去的人生选择。 - `47:11` John 曾拒绝过 Cognition (Devin)、Vercel 和 Sentry 的收购或加入邀约,认为这些本质是 aqua-hire,创始人应尽最大可能保持独立性。 - `48:38` 相比 Cloud Code,团队更推崇 Codex 的产品打磨度(craft)与高并行式 UI 交互;同时 OpenAI 在基础设施层面的算力补贴使得 Codex 比 Anthropic 的工具运行更稳定。 - `50:41` 在 OpenAI 与 Anthropic 的选择上,嘉宾更倾向于 OpenAI 允许用户在最小限制下自由探索的自由意志主义理念,而认为 Anthropic 在使用上过于说教。 - `51:50` 未来最大的 AI 公司将诞生于消费级市场(Consumer AI)而非企业级,未来的赢家往往也是产品公司与模型公司的复合体(如 Cursor)。 - `53:06` 在自动化和网络安全领域,哪怕产品能比对手多挖出 10% 的漏洞就极具价值,壁垒在于模型之下的优化层(optimization layer)。 - `53:49` John 对 Paperboy 一年后的期许非常务实:希望改善财务状况不再每天亏钱,并持续提升团队的人才密度。

## Detailed walkthrough 以下是根据播客录音片段整理的详细内容:

### `00:00` 团队背景与传统快问快答 节目伊始,主持人 Koji 介绍了本期《十字路口》的嘉宾——Paperboy 的创始人江洋(John)以及他们的 Funding Engineer Jet(成)。由于江洋习惯用英文表达,本期节目呈现出中英夹杂的对话模式,视频版本则会配备相应的翻译字幕。

在“快按快答”的传统开场环节中,两位嘉宾分享了各自的基础背景: * **年龄:** 江洋 21 岁,Jet 19 岁。 * **毕业院校:** 江洋毕业于上海星河湾双语学校高中,目前刚结束在卡耐基梅隆大学(CMU)大一的学业;Jet 的学校在片段中未详细展开。 * **MBTI 与星座:** 江洋是 ISTJ 双子座;Jet 是 INTJ 处女座。

在创立 Paperboy 之前,江洋已经有了第一次创业经历。他的第一家公司叫 Million,曾在 React 生态系统里做了很多开源的开发者工具(dev tools)。他们开发过一款名为 `same.dev` 的产品,让普通人可以通过输入一个 URL,直接生成和任何网站一模一样的一套 UI 界面。此外,Million 还成功入选了 YC(Winning 24)。

---

### `01:43` 从第一家公司到 Paperboy 的诞生 江洋透露,Paperboy 的诞生源于他自己对不同产品形态和技术解决方案的摸索(hacking around)。他发现当时的 AI 产品存在很大的技术和形态痛点:用户被迫要将邮箱、姓名等大量个人隐私信息输入到不同的应用中。他认为,如果人与人、人与 Agent 之间需要协同,应该在一个统一的上下文窗口(context window)里非常轻松地完成。理想情况下,Agent 了解用户的方方面面,应当能够“主动(proactive)”帮用户解决问题。

然而,现有的聊天窗口(chat window)和基于会话(session-based)的产品形态根本无法实现这种主动性。由于模型能力与实际部署产品之间存在巨大的鸿沟,江洋看到了在产品体验上进行探索和创新的巨大机会,因此将新公司命名为 Paperboy。

在财务和公司现状方面,江洋非常坦诚且幽默地自嘲。他们此前向朋友们发布过一个原型产品,该 Agent 可以通过学习操作系统的活动来成长,但由于成本太高且效果不尽如人意,他们正在努力于本月内完成新一轮的产品迭代并重新推向市场。 - **融资额度:** 公司以 2500 万美元的估值融了 470 万美元。 - **财务现状:** 目前是“零且负的毛利率(Zero and negative gross margins)”,并且“我们每天都在亏钱(we lose money every day)”。 - **团队规模:** 团队共有 12 人,其中包含 10 位工程师。

---

### `04:10` AI 交互的“移动球门”与三大技术维度 Jet 提到,他第一次和江洋见面面试时,江洋给他看了一篇为公司第一次全员大会(All Hands)准备的文档。那篇文档的核心论点是:“与 AI 合作的最佳方式尚未被发明(the best way to work with AI hasn't been invented)”,而他们的目标就是成为找出这个解法的团队。

江洋以 Cursor 为例,指出其在探索“如何用 AI 写代码”这一目标上取得了巨大成功,因为他们比其他人更早地聚焦在这一终点线上。但江洋强调,这是一个“移动的球门(moving goalpost)”,你永远无法真正触达市场预期的终点,只能不断做得更好。因为只要你做出新东西,其他有品位的团队和用户就会看到其中的摩擦点。随着 OpenAI 和 Anthropic(推出 Claude Artifacts 等)的不断迭代,许多创始人感觉每天都在面对一个全新的世界。

从技术和产品形态的角度来看,江洋将这个问题的解决空间划分为三个 Category(类别): 1. **环境集成与学习(Context):** Agent 必须能够从用户的环境中学习,直接整合到用户工作的地方,读取电脑上的大量文件和各项集成数据。 2. **个性化与可靠性(Personalization & Reliability):** 个性化意味着用户不需要写那么多 Prompt,可以信任它去处理更复杂、更高风险的决策。可靠性则意味着模型可以持续、长时间地稳定运行。 3. **极简的设计(Design):** 产品必须极其直观,用户不需要像学习新工具那样去刻意学习它。如果 Agent 是主动的,它需要一个合理的形态来承载这些主动输出的内容,并能和现有的团队良好协作。目前新出的工具还没能突破这三个由人类团队定义的维度。

---

### `06:40` 现有 Session 机制的痛点与 Paperboy 的解法 在谈到为何要使用 Paperboy 时,江洋对比了目前市场上最成功的 Agent 形态——ChatGPT 和 Claude。他认为这些产品虽然成功,但它们是“基于会话(session-based)”且“一对一基于提示词(prompt-based)”的,这带来了两大局限性:

首先,**Agent 是被动的(reactive)**。用户必须非常具体地给指令。虽然可以创建自定义的 skill 或上传 doc 文件来描述背景,但用户需要主动去维护这些文件。更糟糕的是,人类很难将自己的品味、判断力和对最佳工作方式的理解,完全转化为冰冷的纯文本文件。

其次,**会话是不连续的**。很多人现在攒了几百甚至上千个会话窗口。有些窗口里可能包含了非常有价值的洞察,但如果用户没有刻意、主动地把这些最核心的精髓保存下来,这些信息就会永远迷失在历史记录里,无法带入未来。

Paperboy 正面迎击了这两个痛点,其核心特征表现为: * **多模态 OS 层数据收集:** 在获得用户授权的前提下,Agent 通过观察用户日常使用电脑的行为来自动学习。这包括屏幕截图、按键、鼠标轨迹、包含音视频的会议记录、浏览器历史记录,甚至 iMessage。 * **超长且可搜索的持久上下文:** 它存在于一个拥有超长历史记录的聊天中(远长于单个 context window),且所有聊天记录均可搜索。形式上就像打开 iMessage 或微信,用户直接与其中的参与者对话,但 Agent 能从过去的聊天历史中深度学习。

---

### `11:13` OS 层上下文的“高浓度”优势 针对通过读取邮件、信息来实现个性化的路线,江洋和团队在早期做原型时,也曾尝试过导出用户完整的微信或 iMessage 的聊天数据。但他们很快发现这种方法并不具备可扩展性(not scalable)。

最具有扩展性的方式其实是从操作系统(OS 层)的层面去收集用户数据。他们发现,按照信息浓度来算,用户日常操作电脑的信息浓度极高。观察用户用电脑 60 分钟所能学习到的信息量,远比观察过去 60 分钟的微信聊天数据要多得多。因此,团队很早就押注(Bet)在通过 OS 层的 Context 来做用户适应(user adaptation)。

主持人 Koji 提到,此前采访过的 LG Alley 创始人也在做类似的 Mac/Windows 桌面客户端来抓取上下文。江洋回应称,从电脑抓取 Raw Data(原始数据)并处理成记忆,是包括 Codex、Claude 等各大公司都会做的“明显的新前沿”,但关键在于如何对待和结构化这些原始数据。

江洋认为,压缩和结构化数据的方式与 Agent 的具体应用场景直接相关。比如一家聚焦于帮用户回邮件的公司,其记忆结构和压缩邮件 Action Space 的算法就会完全不同。目前的赛道空间足够大,关键在于谁能率先通过跨应用、跨人际关系的数据,真正建模出用户一天的完整行为。

---

### `13:58` 探索全新领域与用户的前 5 分钟价值 目前,诸如 Codex 这样的公司会将屏幕数据作为 Context Layer,用来学习用户平时是如何开发应用程序的。江洋指出,这依然是一个非常新的领域(Domain),在收集屏幕和基础数据之外,还有巨大的探索空间。

其中的研究和工程难点在于:如何做出最好的主动型 Agent?是预测用户的下一个按键(keystroke),还是预测用户接下来一个小时要干什么?目前行业内并没有人找到绝对完美的“配方(recipe)”,因此对初创公司来说,探索这一未知领域仍是极佳的选择。

当用户首次安装 Paperboy 时,团队希望在最初阶段(如前 5 分钟或 1 小时)通过**会议准备(meetings prep)**来向用户展示产品的潜力: * 产品不需要用户设定太高的预期,因为“它用得越久就越聪明”。 * 用户授权日历和邮箱后,会看到一个真正的聊天窗口(而不是一个 Prompt 输入框)。 * Agent 读取数据后会主动提问以了解用户身份,并提供主动建议。例如:“我看到你有一个即将开始的会议,需要我帮你提前了解一下吗?” * 这种方式让用户建立起一种预期:这是一个可以用非常合理、不打扰的方式,主动发信息帮你的 Agent。

---

### `16:21` 团队的“啊哈时刻”与对 Prompt 的厌恶 团队自身也是 Paperboy 的深度使用者。江洋分享道,团队里来自小红书(前红杉)的成员 Vivian 拥有一个专属的 Paperboy 叫 “Mini Vivian”,而江洋自己的则叫 “AutoJong”,它们目前活跃在 Slack 里。团队成员经常直接在 Slack 里向 AutoJong 提问,它能处理各种工作交接,帮产品和设计团队找到所需的协助。

而 “Mini Vivian” 则成为了 Vivian 的招聘实习生。因为它参与了 Vivian 的会议、听过她在 Slack 上的发言,完全理解她对候选人的品味、判断力以及挖掘渠道。它能主动在 GitHub、小红书和 Twitter 上筛选并推荐候选人。正因如此,Vivian 从今年 2 月份开始就再也没有用过原生的 Claude,因为 Claude 根本不具备这些个性化的背景 judgment。

随着 Context 的增加,江洋直言自己现在“极其讨厌 Prompting”: > “从现在开始 like I just did not want to prompt. I think prompting is such a... I mean, you have to communicate. But people, we don't think in prompts.”

他指出,人类交流不靠提示词,而是发信息并期望对方能心领神会。高质量的关系来自于高带宽的沟通。他特别享受被告知“自己不知道的事情”,尤其是那些“不知道自己不知道”的盲区。面对现在高智商的模型,江洋调侃自己期待未来能直接躺平,让智商更高的 AutoJong 替自己打理一切。

---

### `19:07` Agent 的责任边界与命令行自动补全功能 Jet 随后分享了他的视角。他开玩笑说,很多时候和 AutoJong 聊天甚至比直接和江洋本人聊天体验更好。但他指出,用户最终必须为自己的 Agent 负责。AutoJong 的搭建不是一蹴而就的,它有一个包含 onboarding 的设置过程。

Agent 在这个过程中会主动向用户确认权限和边界。例如它会问:“我可以对这个特定的人分享多少信息?”在默认情况下,它会镜像人类的关系。比如江洋和 Jet 分享很多,但对刚入职的工程新人分享较少,Agent 通过观察就能自动掌握这种人际分寸。

在日常工作中,由于 Agent Factually(事实上)拥有了江洋的大部分上下文,并通过观察掌握了江洋的启发式思考(Heuristic),Jet 作为工程师(IC)在思考如何为公司产生最大价值、该去做什么研究和工程时,去和 Agent 交流就能获得极大的帮助。

对 Jet 而言,另一个巨大的“啊哈时刻(Aha moment)”来自于**文本补全(Text Completion)**功能的上线。 - **功能背景:** 虽然现在很多 AI 命令行工具很火,但流畅度不如传统终端,且传统终端缺乏 AI 整合,写脚本时常让人抓狂。 - **具体应用:** 团队开发出 Text Completion 后,Jet 写完一堆代码准备提交 Git Commit 时,只需在终端输入激活词 `ats pb commits`,系统就会根据上下文自动写好完整的 Commit Message,直接回车即可发送。

---

### `21:55` 跨应用上下文聚合与工作效率“监督” Jet 进一步展开阐述了 Paperboy 的开发流程。团队首先攻克了将操作系统数据收集并转化为优秀记忆系统(Memory System)的难关。在工程上,这套系统会实时更新一个类似于 Framework 的 Markdown 文档,里面涵盖了用户的职业以及过去几天干了什么,让 Agent 时时刻刻拥有最新的上下文。

在此基础上,他们寻找的应用场景就是“在操作系统的任何地方实现类似自动补全(Autocomplete)的功能”。比如在微信聊天框里输入激活词 `@pp`,后面可以加简短的指令,甚至**可以完全不输入任何指令**。 * **心领神会的默契:** 当用户不输指令直接艾特时,Agent 会根据当前上下文猜测用户的意图。就像老同事之间一个眼神、指一下屏幕就知道看哪、问题出在哪里一样。 * **超越传统工具:** 这种基于 OS 层的全局上下文,效果显著优于 Cursor 或 Copilot 等局限于单一应用的工具。Jet 举例称,自己开发大功能时,一会儿在 IDE 里敲代码,一会儿在微信里和江洋发消息,一会儿又在浏览器里做研究,Paperboy 能把所有这些散落在各处的行为上下文聚合在一起,直接以一个 Pull Request(PR)的形式帮他做好 Draft(草稿)。这比任何单一应用的 Agent 都要聪明得多。

在片段的最后,Jet 还分享了一个充满趣味的个人细节。他怀疑自己有 ADHD(注意力缺陷多动障碍),写代码时经常会分心去旁边刷 Hacker News。如果看到好玩的文章,一读就是 30 分钟,等回过神来代码可能已经断掉十几分钟了。

针对这个问题,Jet 每天晚上会让 Paperboy 给自己生成一份效率报告: > “我每天晚上就是会让 Paperboy 就类似给我一个 report 就说我今天到底有多 efficient,我让他会去就是相当于骂我,我什么时候就是不够高效、我什么时候分神了。”

他发现,当自己意识到 Paperboy 在后台“盯着”自己工作的时候,他的整体工作效率反而会变得更高。

`25:00` The Inspiration for Paperboy's Interface and Overcoming the "Sidebar" Dilemma

The conversation centers on the underlying inspiration for Paperboy and how the team navigates complex product decisions. One speaker explains the desire to move beyond manual processes—like sketching thoughts on paper—and instead leverage a smart model that intimately knows the user to thread disparate ideas together across different planes. This philosophy directly influenced Paperboy's latest interface, which began development just two weeks prior.

The team encountered a significant product dilemma when considering venture capitalists (VCs) as part of their Ideal Customer Profile (ICP). They realized VCs require highly specific, varied modules: a personal CRM, an upcoming meetings tracker, a quarterly deals overview, and tools to monitor both portfolio companies and LP relationships. Initially, the team considered shipping a standard sidebar with these pre-built modules. However, this triggered a broader architectural question: since operators, founders, and real estate salesmen all require vastly different sidebars, should these features be shipped as "skills, plugins, or recipes" for the user to manually add?

Ultimately, Paperboy itself helped resolve the dilemma by steering the team away from an overly complex sidebar model. It pushed them toward an instant messaging (IAM) framework inspired by WeChat and iMessage dynamics in China. In these ecosystems, users organically and intuitively manage multiple group chats—sometimes creating four separate groups for the exact same three people just to segregate distinct topics. Instead of building a traditional, annoying "infinite list" or a standard inbox feature, the team decided to turn the product itself into an IAM-style inbox, resulting in Paperboy's unique communication and design layout.

* **VC Module Requirements:** Personal CRM, upcoming meetings, quarterly deals, portfolio tracking, and LP relationship management. * **The WeChat Inspiration:** Users creating multiple distinct group chats with the same participants to naturally isolate and organize different topics. * **The Interface Philosophy:** Shifting away from rigid sidebars and instead designing the core product to function natively as an intuitive IAM-style inbox.

---

`28:13` The Competitive Landscape and the Limitations of "AI Slack"

The discussion shifts to how a small startup like Paperboy can survive and maintain an edge against massive tech incumbents with superior distribution channels. The team acknowledges that they must rely on having a "taste" edge to beat larger players to new interfaces, drawing a parallel to how the code editor Cursor carved out its own space. While an exceptional individual product experience is vital, the ultimate goal for monetization is entering the enterprise market.

Interestingly, Paperboy’s very first product concept was actually an "AI Slack." The team initially viewed this as the logical answer for how humans should collaborate with AI agents. However, the speaker notes that the AI Slack space has quickly become incredibly crowded, with numerous products attempting to solve team-and-agent integration. Despite a deep admiration for Slack and its leadership, the speaker outlines two massive friction points that ultimately caused Paperboy to pivot away from trying to replace it.

First, the enterprise adoption barrier is incredibly high. To convince a company to switch, a competitor must build a flawless one-to-one data import/export experience alongside a mountain of custom data connectors for all the existing software an enterprise uses. Furthermore, the speaker candidly shares that from a user perspective, Slack is "honestly not a great product" to use due to its rigid channel-and-thread structure, even though companies scale into it because nothing better currently exists. Second, the team does not believe AI agents can effectively learn how to work with humans if their only context comes from chat messages. Employees are simply too busy to train agents manually; they expect software to work out of the box.

* **The Incumbent Advantage vs. Taste:** Small teams must rely on superior design taste and rapid execution, similar to Cursor's strategy. * **Enterprise Switching Costs:** Replacing Slack requires building extensive data connectors and a seamless one-to-one data migration infrastructure. * **The Agent Training Flaw:** Relying solely on Slack channels and threads does not provide enough natural context for AI agents to learn effectively without burdening busy users.

---

`31:37` Network Effects and the Complementary "OS Layer" Strategy

The speakers analyze Slack's formidable network effects, comparing its defensive moat to WeChat's dominance. A key element of this moat is Slack's "external connections" feature. For transparent and serious companies, inter-company communication has largely shifted away from traditional email and into these shared enterprise channels. Because of these deep integration network effects, trying to completely replace Slack for any team larger than 50 people is a monumentally difficult task.

Instead of fighting these network effects head-on, Paperboy shifted its strategy to a complementary approach. Rather than trying to build a new chat app from scratch, they view their product as a layer operating above or alongside existing workflows—closer to an Operating System (OS) level. This creates a much more compelling adoption story, as it brings AI agents directly to where people are already working instead of forcing an organizational migration.

The conversation transitions to Paperboy's philosophy on product speed, referencing an unreleased blog post on their website titled *The Last Interface*. This post outlines "five kinds of speed." The speaker clarifies that five is just a sensible categorization inspired by the "Pace Layers" concept originated by the Long Now Foundation in San Francisco. The Pace Layers model views the world through six layers changing at different velocities—ranging from fashion and commerce at the fast end, to infrastructure, civilization, and nature at the slow end.

* **Slack’s Moat:** External connections have replaced email for business-to-business communication, locking companies into the ecosystem. * **The Complementary Strategy:** Bringing agents to existing workspaces rather than forcing teams to switch off Slack. * **Pace Layers Influence:** A framework adapted from the Long Now Foundation to understand how different systems and velocities interact within a product architecture.

---

`34:42` The Time-Horizon Spectrum of Human and Agent Tasks

The speakers break down how the concept of pace layers applies to user actions and AI augmentation. They view user behavior as a spectrum of time horizons. On one extreme, a user performs rapid actions, such as taking one to ten seconds to reply to a message on WeChat. On the opposite end of the spectrum, a user might spend several hours reading ten deeply detailed reports to make a major business decision.

The team believes that while AI agents will inevitably augment or automate tasks across this entire spectrum, the required product form factor changes radically depending on the time horizon. Automating a multi-hour task remains an entirely open and highly experimental product frontier that the team is eager to explore.

The host transitions the topic to Jump’s background, noting that despite being born in 2004, his maturity and clarity stand out to everyone who interacts with him. Jump playfully pushes back on this, claiming he is still a "pretty childish person" who likes to have fun with his co-founder, Jet. However, he acknowledges that running a startup requires extreme clarity, efficiency, and focus. He defines his primary job as CEO as bringing absolute clarity to the team: defining what success looks like and ensuring every person has complete, accurate context regarding their goals and operations.

* **The Task Spectrum:** Ranges from short-horizon tasks (1–10 second messaging) to long-horizon tasks (multi-hour report analysis and decision-making). * **The Product Frontier:** Designing the ideal user interface and form factor to automate multi-hour, complex workflows. * **The CEO’s Role:** Ensuring high context alignment across the team so everyone understands their exact goals and operational boundaries.

---

`37:28` Early Startup Lessons, Market Selection, and the Role of a First-Time CEO

Jump reflects on his personal journey from high school to college, noting that his insatiable curiosity has been his primary driver. Before Paperboy, he took several internships across different companies to learn diverse problem-solving methodologies. He and his peers initially started a B2B business selling web performance PR bots to large enterprises. They quickly learned that enterprise sales is an incredibly difficult business to scale, especially for 20-year-olds who lack experience navigating enterprise relationships.

This early lesson taught Jump the vital importance of "founder-market fit" and "team-market fit." He argues that market selection is perhaps the most critical trait for an early-stage founder. When picking a market, it cannot just be about the current dollar sign; the market must be highly sustainable and capable of compounding over a decade so the team can continuously evolve its product lineup. Jump points out that history's most successful products are rarely just a single release; they represent a decade-long product lineage aimed at eventually reaching mass consumer adoption.

Transitioning into his first role as a CEO, Jump admits, "Man, it's fucking hard. I gotta own everything." He details the intense leverage a CEO holds, where a single bad idea can cost the company immense amounts of money. As the team scales, the responsibilities shift heavily toward hiring the right people, fostering their continuous growth, and learning basic management skills on the fly—like conducting performance reviews and avoiding micromanagement.

* **Early B2B Pivot:** Shifting away from an enterprise PR bot startup after realizing 20-year-olds face steep structural disadvantages in enterprise relationship building. * **Market Criteria:** A viable market must have a compounding scale that allows for a decade-long product lineup trajectory. * **CEO Leverage:** The realization that a CEO's strategic choices carry massive financial consequences compared to isolated execution delays.

---

`41:14` Management Mentors, CEO Coaching, and Structuring an Engineering Team

To navigate his first managerial role, Jump leaned on resources and mentorship. He credits Panpan, the CTO of Amanis (where Jump previously worked), as an exceptional engineering manager who gave him invaluable advice during one-on-one sessions. Jump also devoured classic business literature, citing Andy Grove's *High Output Management* as the best management book he has ever read, alongside Ben Horowitz's *The Hard Thing About the Hard Things* and Bill Campbell's biography, *Trillion Dollar Coach*. Additionally, an investor introduced him to a executive coach whom he meets with weekly for an hour. Interestingly, Jump uses Paperboy during these coaching calls; the AI listens to the audio and automatically helps him organize his action items and commitments.

When asked how he structures his small 10-person team given the abundance of modern AI tooling, Jump explains that serious infrastructure development still requires deep human expertise. Paperboy intentionally hires two distinct profiles on the engineering side. The first profile, exemplified by Jet, consists of young, high-IQ, highly creative individuals who excel at rapidly prototyping creative solutions to any problem they encounter. The second profile consists of rock-solid systems experts who intimately understand operating systems and kernels, such as a recent hire from AWS who specialized in Windows kernels for AWS infrastructure.

The conversation concludes with Jet explaining why he chooses to stay in college at Carnegie Mellon University (CMU) despite being a Founding Engineer at Paperboy, especially at a time when companies like Palantir are offering high schoolers direct paths to skip university entirely. Jet explains that for most people, university provides crucial value because many students are still unsure of what they want to do. CMU allows him to steadily elevate his technical abilities in a structured environment where academic work only takes up a fraction of his time, leaving the rest of his schedule free for self-directed exploration over a four-year period.

* **Essential Management Reading:** *High Output Management* by Andy Grove, *The Hard Thing About the Hard Things* by Ben Horowitz, and *Trillion Dollar Coach* (Bill Campbell biography). * **The Two Engineering Profiles:** 1) Young, high-IQ rapid prototypers. 2) Deeply experienced systems/kernel engineers from infrastructure giants like AWS. * **The Value of College in the AI Era:** Jet notes that CMU provides a low-risk environment to compound technical skills while offering ample free time for independent projects.

`45:00` 创始人特质与招聘中的“高斜率”

对年轻的首次创业者(first-time founder)而言,如何吸引优秀人才加入是一个关键课题。谈到加入 Jump 的原因,嘉宾借用数学概念解释了职业选择的逻辑:选择创始人就像看一个函数,既有截距(intercept),也有斜率(slope),而在很多时候,**“slope(斜率/成长速度)比 intercept(截距/起点)重要很多”**。在同龄人或者年龄稍大一点的圈子里,John 被评价为一个在极短时间内实现了诸多厉害成就、具有强“agency(自主性/驱动力)”、学习极快且能迅速适应各种新情况的“high slope”创始人。对于创业者来说,这种头脑清醒与快速适应的能力是极为关键的品质。此外,长期的合作基础也建立了深厚的信任,其在研究、工程乃至产品上的不俗品味(taste),加之其独特的个人魅力(charismatic),成为了吸引顶尖人才的利器。

在具体到如何说服新的候选人(candidate)时,John 坦言自己并不会用一套固定的脚本(script)去生硬地推销公司(hard sell)。他认为招聘必须是双向奔赴的(mutual),他更倾向于针对每个人进行个性化的沟通。在挑选人才时,他强调必须寻找最顶尖的人,拒绝平庸(mediocre)。判断一个人的成色,可以通过深入聊对方过去的工作,而最核心的则是观察他们**“过去的人生选择(past life decisions)”**。特别是对于年龄稍长、拥有十年以上决策经验的人,这些真实的选择是无法伪装的(You can't fake that)。

- **职业选择金句**:很多时候,Slope(成长斜率)比 Intercept(初始截距)重要得多。 - **面试考核核心**:不看包装,最看重候选人过去的人生选择(past life decisions)。

---

`47:11` 独立发展与拒绝大厂 Aqua-hire

当被问及除 Paperboy 之外最喜欢的 AI 产品时,John 毫无掩饰地表达了对 Cursor 的喜爱,甚至直言自己至今不怎么用 Codex,而是对 Cursor 推崇备至。有趣的是,对话揭示了一段关于独立性抉择的往事:在 John 还是十几岁(when he was a billion/teen)的时候,曾经收到过来自 Devin 的母公司 Cognition,以及 Vercel 和 Sentry 等知名公司的收购或加入邀约(offers)。

然而,John 最终拒绝了这些橄榄枝。他理性地剖析道,这些邀约本质上都是**“人才兼并(aqua-hires)”**,并不会涉及特别巨额的资金。一旦选择加入,就意味着要变成这些大公司里的另一个普通员工,去为别人的想法(somebody else's ideas)打工。他对开发工具(dev tools)本身没有那么大的热情,因此如果让他作为个人去加入 Sentry、Vercel 或 Cognition,是毫无吸引力的。他的信条是,如果一个创始人能够保持独立,并且通过保持独立去实现自己的梦想,那就应该坚守独立(stay independent),这也是每个创始人内心深处的渴望。

- **曾收到过的 Offers/Aqua-hires 来源**:Cognition (Devin), Vercel, Sentry. - **拒绝理由**:本质是 aqua-hire,缺乏独立性,对单纯的开发工具不感兴趣,不愿为别人的想法打工。

---

`48:38` 细品 AI 产品:Codex、Cloud Code 与产品打磨力

随后话题转向对特定 AI 工具的深度对比。谈到最喜欢的两款产品,嘉宾澄清了为什么是 Codex 而不是 Cloud Code。在他们看来,Cloud Code 展现的更多是底层模型(如 Claude 3.5 Opus)有多好,而非其命令行界面(CLI)本身有多惊艳。相比之下,Codex 有着诸多令人心动的点:首先,其核心 agent、命令行以及整体的 agent loop 实际上都在 GitHub 上开源;其次,在桌面端 App 的**“打磨水平(craft)”**上,Codex 展现出了极高的水准。这得益于他们之前收购了由开发 Apple Shortcuts(快捷指令)成员组成的 Sky 团队。由这群极度追求精致(polished)的人操刀,Codex 展现了极强的产品感,例如最近推出的 Codex Test、以及在 computer use 和 browser use 的体验上都做到了极致。

此外,Codex 还是市场上第一个将“高并行式”(不同 agent 同时工作)作为主要 UI 交互并推向大众的产品。在基础设施(infra)层面,嘉宾指出 OpenAI 相比 Anthropic 拥有巨大的算力与基础设施优势。OpenAI 能够通过在 infra 层面进行**算力补贴(subsidize more compute)**,使得即便在模型能力大差不差的情况下,Codex 的运行要稳定得多。而 Anthropic 目前因为投资不够、算力受限,不得不采取一些“奇怪的操作”,例如用户的 repo 里如果包含 open cloud 或 hermes agent,Cloud Code 甚至可能会直接收取十倍的价格。

---

`50:41` 投资风向与“模型吞噬一切”的哲学思辨

关于如果购买二级市场股票会如何选择,两位嘉宾给出了不同的视角。一位表示会选择 **“All in OpenAI”**,或者按照 OpenAI 80%、Anthropic 20% 的比例进行资产配置。尽管两家公司都会发展得极好,但他更倾向于 OpenAI 的理念。他赞赏 Anthropic 在可解释性(interpretability)和安全社会影响(social impact)方面的杰出工作,但他认为 Anthropic 在用户如何使用大语言模型上表现得“过于说教/傲慢(opiniated)”(无论是在道德层面还是具体使用习惯上)。相反,OpenAI 奉行的是一种在最小局限性下由用户自由探索的理念,更符合自由意志主义(libertarian)的价值观。不过,另一位嘉宾从纯投资角度给出不同意见,表示在目前的估值水平下“两者都不会买”,但他个人更倾向于 Anthropic 对安全(safety)的承诺与投入。

针对“模型吞噬一切(Model eats everything)”的行业说法,大家展开了辩论。一种有力的论据是,未来许多公司可能会提供大同小异的模型,产品的差异性(differentiation)依然会保留在产品公司手里。但 Cursor 提供了一个硬币的另一面:它打破了传统边界,一开始是产品公司,现在通过借助 xAI 的算力去训练前沿编程模型(frontier coding model),变成了既是产品公司又是模型公司的复合体。因此,未来的赢家不能将自己局限于单一标签,"it's usually both"。

在预测未来巨大机会时,John 给出了他的投资画像。如果有3亿美元,他会投向几类方向: - **Slack 类产品**:看好特定的人,比如对 Richard 的下注。 - **具身智能(Robotics)公司**:这绝对是一个巨大的蓝海,虽然会非常内卷。 - **聚焦于 Infra(基础设施)的公司**。 - **消费级 AI(Consumer AI)**:正如 Cursor 一样,未来最大的公司将诞生于消费级市场,而非企业级 AI(Enterprise AI)。这也是 Paperboy 坚定选择在这个市场深耕的原因。

---

`53:06` 网络安全、国家安全与 Paperboy 的未来期许

在自动化的浪潮中,面对 Anthropic 或 OpenAI 这类拥有最强原生模型的大厂竞争,垂直创业公司如何建立壁垒?嘉宾认为,拥有最好模型只是起点,关键在于**模型之下的优化层(optimization layer)**该怎么做。是做更好的 harness(治理/调教)?是将人类安全研究员的各种启发式规则(heuristics)深度融入到 agent 中?还是去做一个极度庞大的多智能体系统(multi-agent system)去不知疲倦地挖掘漏洞?这个探索空间极大。由于这是一个极其崇尚精英主义、凭实力说话的市场(meritocratic market),哪怕你的产品比竞争对手多挖出 10% 的漏洞,你就是非常有价值的。提及安全领域的发展,诸如 Long Horizon 的法律应用、以及最近张阳阳等人推出的全新 Sweet-bench(用以复现完整的代码库,而非局限于简单的 stocks 或 specs),都证明了这一领域的火热。

从宏观来看,安全能力直接关乎国家安全。模型最强的国家或大厂有很强的动机去实行技术垄断(例如限制只有特定国家可以使用),这反而给其他国家或不同的利益矩阵创造了巨大的本地化市场机遇。

对谈进入尾声,当被问及期待一年后的此时此刻 Paperboy 处于什么状态,或者害怕做错什么时,John 坦诚地给出了极为务实的回答: > "Well, I hope we're not losing money every day anymore."

除了希望公司不再每天亏钱、能够实现健康的现金流(cash flow)外,他最渴望的是持续吸引并聘用他所能找到的最优秀的人才,让团队的人才密度(talent density)比今天还要更高。在温馨与欢笑声中,这场关于 AI、产品与创业的深度对话落下帷幕。

- **Paperboy 一年后的两大期许**: 1. 改善财务状况,不再每天亏钱,实现现金流(cash flow)。 2. 持续提升人才密度(talent density),招聘最顶尖的人。

## Notable quotes > `01:59` 人类和 AI 配合工作的最佳方式,很可能还没有被发明出来。 — 江洋

> `06:21` 你不该像学新工具一样学怎么用它。 — 江洋

> `16:21` 从现在开始 like I just did not want to prompt. I think prompting is such a... I mean, you have to communicate. But people, we don't think in prompts. — 江洋

> `21:55` 我每天晚上就是会让 Paperboy 就类似给我一个 report 就说我今天到底有多 efficient,我让他会去就是相当于骂我,我什么时候就是不够高效、我什么时候分神了。 — Jet

> `45:00` slope(斜率/成长速度)比 intercept(截距/起点)重要很多 — Jet

> `45:00` 过去的人生选择(past life decisions) — 江洋

> `47:11` stay independent — 江洋

> `53:06` Well, I hope we're not losing money every day anymore. — 江洋

## Mentioned Paperboy, John Yang, 江洋, Jett Chen, Jet, Claude Code, Codex, Manus, OpenClaw, Claude, Cursor, Littlebird, Mini Vivian, Vivian, Auto John, AutoJong, Koji杨远骋, 微信, Slack, iMessage, The Last Interface, Million, same.dev, YC, OpenAI, Anthropic, Claude Artifacts, GitHub, 小红书, 推特, Twitter, Hacker News, Vercel, Sentry, Cognition, Devin, Sky, Apple Shortcuts, Codex Test, xAI, Panpan, Amanis, Andy Grove, High Output Management, Ben Horowitz, The Hard Thing About the Hard Things, Bill Campbell, Trillion Dollar Coach, AWS, Carnegie Mellon University, CMU, Palantir, Sweet-bench, 张阳阳

[Source](https://dts-api.xiaoyuzhoufm.com/track/60502e253c92d4f62c2a9577/6a0be0cfe1eb34a939abced5/media.xyzcdn.net/60502e253c92d4f62c2a9577/ltgXurpsEOwqGgFvGc32AURYMT-o.m4a)

中文简报

初创公司Paperboy获470万美元融资 押注系统层数据重构AI交互 现有的会话式Chatbot并非最优解,人与Agent配合的最佳方式需要通过收集操作系统多模态数据、构建持久且具主动性的通讯化界面来实现。 本期节目深入探讨了当前AI Agent产品基于会话(session-based)与被动触发的痛点,并详细介绍了Paperboy如何通过操作系统(OS)层面的多模态数据收集来构建超长持久上下文。两位年轻的创始人分享了团队内部诸如“Mini Vivian”等主动型Agent的实际应用、对未来全新人机交互界面(The Last Interface)的思考,以及面对大厂竞争时小团队凭借产品品味、独立性与高密度人才建立壁垒的创业思考。 Paperboy 团队以 2500 万美元估值融资 470 万美元,团队共有 12 人且正处于每日亏损状态,其核心理念在于人类与 AI Agent 的最佳配合方式仍未被发明。 (1:43) 当前主流 Chatbot 存在基于会话(session-based)与被动触发(reactive)两大痛点,Paperboy 尝试通过直接在操作系统层(OS 层)抓取高浓度屏幕与行为上下文,摆脱传统对 Prompt 的依赖。 (6:40) 团队在内部 Slack 中落地了 Mini Vivian 和 AutoJong 等专属 Agent 分身,能够深度理解用户的品味与招聘决策,甚至实现了跨应用的全局文本自动补全与代码提交生成。 (16:21) 由于企业替换 Slack 存在极高的数据迁移与集成壁垒,且单纯聊天记录无法提供足够上下文,Paperboy 转向类似微信多群聊的 IM 收件箱设计,作为补充层与用户现有工作流协同。 (28:13) 面对模型能力的大幅演进,团队坚信产品界面与打磨体验(craft)依然是创业公司的护城河,未来最大的 AI 机遇将诞生于消费级市场而非传统企业级应用。 (50:41)

Reading summary

Paperboy 创始人江洋(John)与创始工程师 Jet(成)指出,人与 AI Agent 协作的最佳方式尚未被发明;现有的基于独立会话与提示词(prompt-based)的产品形态存在割裂,真正的突破在于通过操作系统(OS)层捕获高密度上下文并构建主动交互能力。 现有交互局限与 OS 层全局上下文 (4:10) 江洋认为,ChatGPT 和 Claude 等主流工具局限于单次会话与被动响应,用户不仅需要反复输入提示词,还难以将隐性工作习惯和判断力转化为文本。此外,数以千计的对话历史互相割裂,造成关键背景丢失。Paperboy 选择转向操作系统层,通过合规获取屏幕截图、按键、光标轨迹、音视频会议和应用记录来持续学习。团队发现,观察用户使用电脑 60 分钟所吸收的信息浓度,远超单纯读取聊天软件的导出数据,能更有效地建立持久、可搜索的长期上下文。 从被动提示词转向主动协作与自动补全 (16:21) 基于全局上下文,团队希望摆脱繁琐的 Prompting,让 Agent 像熟悉业务的老同事一样主动协作。例如初次安装时,Agent 可通过读取日历与邮件主动发起会议准备,而不是等待用户下达指令。在实际工程与办公场景中,团队搭建了活跃在 Slack 里的专属数字分身(如 AutoJong 和 Mini Vivian),能够根据历史习惯协助招聘筛选与跨部门答疑;Jet 提到,在终端输入激活词后,系统能结合跨应用上下文自动生成 Git 提交信息甚至合并请求草稿,还能根据日常屏幕活动生成效率监督报告。 规避 Slack 正面竞争,切入即时通讯式收件箱 (25:00) Paperboy 早期曾尝试过“AI Slack”形态,但很快发现企业替换 Slack 的阻力巨大,不仅需要处理极其繁重的外部数据连接与数据迁移,且 Slack 依靠跨公司外部连接已筑起坚固的网络效应壁垒。团队进而意识到,如果仅依赖聊天文本,Agent 也无法获得足够的操作信息来理解工作。因此,产品放弃了传统侧边栏插件的堆叠设计,转向借鉴微信与 iMessage 的即时通信逻辑,将自身定位为一个叠加在现有工作流之上的 OS 层即时通讯式收件箱,避免逼迫企业迁移协作软件。 早期商业现状、团队构建与技术壁垒思考 (41:14) 目前 Paperboy 团队共 12 人(含 10 位工程师),以 2500 万美元估值筹集了 470 万美元,但由于探索初期算力与研发成本高昂,毛利率仍为负数且处于日常亏损状态。在团队配置上,公司结合了年轻快速的原型设计工程师与来自 AWS 等具备内核和系统底层开发经验的专家。针对“基础大模型吞噬一切”的行业争论,江洋认为未来最大的机会仍在消费级 AI,模型之下的优化层(如安全调教、特定启发式规则融合及人机界面品味)才是垂直产品在基础大模型迭代下赖以生存的核心壁垒。 江洋表示,公司当前首要目标是改善财务状况以结束每日亏损局面,并持续吸引高斜率顶尖人才;面对不断前移的行业终点线,团队仍在探索如何将人机协作从数秒的即时回复延伸至数小时的复杂长任务决策自动化。

Source quotes

[1:59] 江洋: 人类和 AI 配合工作的最佳方式,很可能还没有被发明出来。 [6:21] 江洋: 你不该像学新工具一样学怎么用它。 [16:21] 江洋: 从现在开始 like I just did not want to prompt. I think prompting is such a... I mean, you have to communicate. But people, we don't think in prompts. [21:55] Jet: 我每天晚上就是会让 Paperboy 就类似给我一个 report 就说我今天到底有多 efficient,我让他会去就是相当于骂我,我什么时候就是不够高效、我什么时候分神了。 [45:00] Jet: slope(斜率/成长速度)比 intercept(截距/起点)重要很多 [45:00] 江洋: 过去的人生选择(past life decisions) [47:11] 江洋: stay independent [53:06] 江洋: Well, I hope we're not losing money every day anymore.

Original transcript

[0:00] 嗨,我是Koji本周十字路口我们请到的嘉宾是Paperboy的创始人江洋以及他们的一位Funding EngineerJet成你好二位,欢迎来到十字路口Hello,Koji在这里也给大家说明一下因为江用英文表达会比较自然所以我们这一期内容会比较中音夹杂我们同时有音频和视频如果大家需要的话可以去看视频看视频我们就会配字幕和字幕的翻译帮助大家理解我们还是从十字路口的传统快按快答开始有请二位的年龄I'm 2119你们的毕业院校我是上海新欢双语学校高中毕业然后现在在CMU读大一大一刚结束你们的MBTI和星座是什么ISTJ双字座INTJ处女座创业之前你们做了一些什么Payboard是我第二家公司我的第一家公司叫Million我们是在react ecosystem里做了很多开源的dev tools然后我们做了一个产名叫same.dev普通人可以用一句话去输入一个url然后做出和任何网站一模一样的一个UIAnd miller was in YC, winning 24. started broadly with the mission of I am trying to figure out So yeah, Paperboy just started with me trying to hack around different approaches to try to figure out how to solve there are technical problems here but also form factor Like, I shouldn't have to put my information, email, and all this personal information into a situation. If I need to collaborate with each other, I can also talk to an agent. This should be a very easy way for me to, for us to collaborate within the same context window. Agents, if you know my many things, they should be proactive to help me do some things. But in the chat window, you really can't do it. And then all of the products are sessions based. So if you don't find out what context window is, you should continue to do it. So just all kinds of these problems, I think, where generally speaking, it's the gap between model capabilities and deployment. And I feel like there's still a large opportunity to explore and innovate on the product experience and hence the name is Paperboard Products. We'll open it up, but we'll do it again. What's your income? We raised 4.7 million at 25. Oh, cool. Zero and negative gross margins And we lose money every day So we shipped the prototype to friends And that's like our agent that learns from OS activities But there are cost issues It's too expensive It doesn't really work So the next iteration of this product We're tryinto wrap it up by this month. And it's going to try, we're going to try to go to market again. We'll put a link in the description below. If you're interested, you can sign up for it. Oh yeah, you guys will see it, I think, when this podcast comes out. And what's the team's规模? There are 12 people in the community, and there are 10 engineers. I remember when I first met him like this, you gave me a page. The article was written for the interview. The first thing was, you said that the best way to work with humans was not being published. When you wrote this article, what did you see? And then, you thought you saw some changes? Yes, so that doc is the one I prepared for our very first All Hands. That's when I was a company, I was a jet company. and and yeah I think we just started working with one thesis which is the best way to work with AI hasn't been invented and we have shot at being the team that figures out that way so Chris just started really trying to figure out what's the best way to code with AI and [5:00] they have been largely successful being the first company to really approach on that goal and to figure out how important it was to focus on that goalpost before everybody else. I think what's cool is this is a moving goalpost. Instead of market's expectation, you can't really reach it. You can only keep getting better because every time you come up with something new, Right, everybody else see it And if the other teams have taste If users have taste They will know And they will see the friction points There will always be frictions And so all you have to do You just keep getting better So I think it's really a moving goalpost And we're from Senzai You know, OpenCloud came out We have Cloud Cowork Which is Anthropics You know So actually, many founders Feel like there's a little dream Because in the process of the development There's a new world that's constantly happening Code 因为I think the problem space comes from people. How I think about this problem space from a technical form product point of view is three categories of problems. You have the technology of agents being able to actually learn from the user's environment. It has to be integrated into where the user already works, where the data comes from lots of files on a computer and integrations. And then the second thing is you have to be personalized. So personalization means you don't really have to prompt it as much. You can trust it to work on more and more complex and difficult things. You can trust it to make more higher stakes decisions. And it also means being more reliable. and that means you can actually use the model and just keep running it for longer and longer periods. And also from a design point of view, it needs to be extremely intuitive to use. You shouldn't have to learn it as like a new tool. If your agents are proactive, they can bring up new ideas by themselves. What is the form that holds all of these proactive outputs together? It has to be with the environment and it needs to be personalized It needs to be able to collaborate well with your existing team So when you look at new tools that come out there not really a new dimension that come out yet because these three dimensions are limited by the human teams. We have to explain to you very briefly why we use Paperboy. Because many people are already in the audience of our podcast, or a user, or an agent of the users. Why do we use Paperboy at this time? Yeah, so since I talk about Humanis, to me, they're kind of the most successful forms of agents out there. They are session-based and they are one-to-one like prompt-based. So these are two very important factors here. Session-based means in their sidebar, there is a bunch of, you know, you have workspaces, which are projects, and then per project, you have a bunch of sessions, right? And every time you want the model to do something new, you start a new session and you categorize into a workspace, okay? The second thing is the way you interact with the model is you prompt something and you wait, but then you just send another message and another assistant, a bunch of turns and another message. The problem with this is one the agent is reactive You have to be very specific You can create a bunch of skills or like doc agent files to describe sort of what you doing but you have to actively maintain that And it doesn't matter how much effort you keep into maintaining that. It's very difficult to translate everything you know about your tastes and judgments and what you believe is the best way to do things into these raw text files. That's one limitation. And the second thing is like sessions are not continuous and it sucks. It sucks to have like hundreds, I think many people even maybe have a couple thousand sessions now. And I know in the past, there are some sessions where the information in that context window might have actually contained some very valuable insights. But if I didn't save it, if I didn't save it directly, deliberately, like here, this is the most important part across all of these different sessions that we worked on this project. This is what we need to take away and take with us into the future. that session kind of just gets lost. Yeah, so to me, that's like, so what is Paperboy? Yeah, so we handle kind of these two problems head on. One is the agents have to learn by themselves from observing how you use your computer. And that includes all the information of your screenshots, your keystrokes, mouth movements, your meetings, which includes videos and audios, your browsing history, [10:00] or iMessage. And of course, you choose to give access to Paperboy what you want to get it. And the second thing is that it needs to exist in chats with persistent conversation histories that are much longer than a context window. And the chats need to be searchable. And the standard product form is really like, okay, you're just like opening your iMessage or opening a WeChat and you have a bunch of chats. And I go to the chat to keep having conversation with the participants in that chat. But actually, the main difference between the paperboy and the product is that The product context is that it mostly based on the user agent past chat history You can learn from this And there also a question that the user gives these agents your email or messages history learn他们也可以就是说通过读这些email去逐渐的去更加personal去学习关于这些用户的更多信息但是我们一开始做的prototype其实也试图去导出用户所有的微信两线数据或者说iMessage的所有两线数据但是我们很快就发现这其实并不是一个非常scalable的方式然后最scalable的方式其实是通过观测用户在日常使用他的电脑就是从一个OS层面的一个形式去collect user data然后我们其实发现这样子的话会对用户每天做什么事情有一个非常全面的了解而且你按照信息的浓度来说用户的一般的computer use他信息的浓度是非常高的你只要观察用户比如说用电脑用个差不多60分钟就可以学习到用很多的信息但是如果你只观察用户过去60分钟的微信聊天数据其实学不到太多东西所以说我们很早的就是Bets就是说通过OS层面的这个context去做这个user adaptation其实十字路口之前有一期播客的嘉宾LG Alley的Founder他们其实在做的也是一个Mac或者一个Windows的桌面客户端来抓尽可能多的上下文所以你们在做的时候和大家是类似的这个实践吗还是你们有什么不一样的一些想法和做法从Mac还有用户使用的电脑上去抓起 raw dataand processing it into memoriesThat as a general thingis going to happen not just to startups that are deliberately focused on it like AirJelly but Codex, CloudCode work, CloudCode they're all going to do it it's sort of like the most obvious next frontier of context available but of course how people treat that raw stream of data and how it gets processed will happen very differently what you choose to and how you choose to structure that information is directly related tothe application of the agentsyeahso what every individual agentand what your application actually decides to help the user onyou shouldn't probably structureand like you can't compressthe raw activity stream in the same waysand so yeah likejust that alone probably gonna havelike for a company that hyper focusedfor example on on studying um how a user replies to emails right then they probably going to have a different memory structure whatever way of compressing the raw emails that they learn from the action space is big enough that there is enough room right now to be able to be the first to get to that it's really understanding who the user is across all their application services across their relationships and then you can sort of model what the user actually does within a day. Yeah, it's just that capability alone, I think it's just going to be so obvious. Everyone's jumping into that, but depends on the application, there's room to, you know, customize and change the algorithm. I also think that now, through the user's user's computer, or computer use, to build the context, it's a certain extent to become a business. And the last thing is, in this process, what are you doing in this process? 目前像是Codex或者说类似Little Bird的这种 他们会把这个屏幕数据当做一个context layer 就比如说对Codex Chronicle 他其实目前的use case是说 你可以通过就是收集用户屏幕数据 去学习用户一般是怎么去develop这个application的 如果你的use case不一样 他确实就你最后这个pipeline也会不一样 我觉得这是一个非常非常新的一个domain 然后你在基础的就是收集用户屏幕数据 还有收集就是个 [15:00] 比如这个情况下你其实还可以干非常非常多的其他的事情然后这个需要非常多的就是engineering还有research就比如说你如何去做最好的proactive agent你是在预测用户下一个keystroke还是说预测用户后面一个小时去干什么还是说去预测什么其他的事情这些都是relatively就是没有被这么好explore的一些problem space然后目前其实我认为也没有任何人发现一个就是说绝对最好的一个recipe去干这件事情所以说我觉得目前就是对于一个公司人说去探索这个Aware还是一个非常好的选择那如果今天用户安装了Paperboy他立即会比如说在第一个小时甚至在前面五分钟他能够感受到的这个价值最大的是什么你们期待用户在第一时间感受到的差异和价值然后从而能够留下来就这个highlight的点是什么We're probably going to start with a meetings prepand一个小时其实很重要的是你要 demonstrate to users一个匡量 of what your product can do you don't have to set expectation one thing for paperboy it gets better the longer you use it and so you just sort of need that initial period where the user trusts it to learn and so you can open it up you can see a chat box and not a chat box like a prompt box but a literal um chat window and once you give it permissions to say a calendar you know emails it's going to start reading where you get it and then it's going to kind of sort of be asking a little bit of a question about who you are from the context of reading value and it's going to start giving you a couple suggestions like hey i see this meeting coming up do you want to look into that for you. This is the way that you can do it by interaction. They sort of figured out the recipe here, which is, well, you just connect to the user's existing context and you need to show the user you are an agent that can actually engage with the personality and proactively in a non-annoying manner to help the user. So you get the user into this expectation that we are the agent that can actually text you in a way that makes sense. Yeah. Yeah. 你们二位或者整个团队用Paper Boy用了多久了? 在你们自己用的过程中有没有什么? 我可以分享的一些啊哈moment Yeah, so Vivian is also here. Hello. Yeah, Vivian is very funny. So she joined from小红书,她之前在红山的月. So we have Vivian's Paper Boy. It's called Mini Vivian. My paperboy is called AutoJone, and they exist in Slack right now. You know, all the time, teammates on paperboy will just ask AutoJone questions. So it's able to handle all the incoming questions and help teammates, product team, design team, find the help that they need. And for Mini Vivian, for example, Vivian does a lot of recruiting work. And so like Mini Vivian is the recruiting intern for her on the team. Because many of you actually understand everything that I have ever said to it across meetings, Slack, which includes my judgment and taste on what kind of candidates we're trying to hire and where we want to source from. It's able to a lot more actually help Vivian surface these candidates across GitHub, Songshu, Twitter. So I think that saved her a lot of time. I think Vivian since February has not used Cloud. she can't use Claude because it just doesn't know you can't use Claude to research candidates for you like you just there's so many things you would have to tell it about the judgment of the person 因为它有了更多的 context 所以你其实在给它 prompt的时候 你甚至可以不 prompt Yeah, I hate prompting 从现在开始 like I just did not want to prompt I think proompting is such a, I mean, you have to communicate. But people, we don't think in prompts. We send texts, you know, and we expect the other person to know what we're talking about. And we enjoy a relationship when the communication is high bandwidth. We also enjoy, I think the smart people, enjoy being told what we don't know. And especially what we don't know what we don't know. And today's models are, smarter than who we are So frankly I look forward to the day when I can just lay back and or John being the smarter higher IQ existence than I am Okay Jensen呢? You have some kind of aha moments in the paperboard process? First, there are many times with John with the auto-jump conversation better than with John. But you're with the auto-jump when he's agent-to-jump conversation you're worried that his and the way I look at it, not just because we are creators of this thing, but the user has to be responsible for your agent eventually. So with how Autogon gets set up, it's not just like one day, boom, you have this existence that you can bridge into Slack. There is an onboarding process where the agent is going to be able to do it. So the user has to be responsible for the agent. So the way I look at it, not just because we are creators of this thing, [20:00] This actually asks you questions. And it asks questions like, how much am I allowed to share to this specific person? Right? By default, it mirrors, like for example, I share a lot with Jet. Maybe I don't share as much with a new engineering hire. And the agent actually knows that from observing all my Jet. And I think that usually when you interact with someone, it's actually a lot of different. In the end, you're probably... If you're a person, I sometimes just like with a guy talking to me. Or if I need to do a thing that I don't have the rights, I need to approve a thing. 这些东西我觉得目前可能是就是我不会去和AutoJong说的但是实际上就是在工作场景中你很多时候和对方的一些communication是说这样他有整个对Payboy一个公司的context然后我作为一个工程师或者我作为一个IC就是我每天需要就是我如何能对这个公司产生最大价值我去做什么research或者说做什么engineering是最有用的然后这个时候就因为这个agent第一就是factually他有这样有的大部分context然后第二他通过观测这样工作的时候 the heuristic actually with the job is a bit similar so I was doing the job about context and heuristic the things that I think is more useful and the other aha moment actually I think I have a moment is when we did the text complete actually moment moment Complete就已经挺有用的因为我平常用的现在有很多AI Terminal很火但是就AI命令行很火但实际上就是那些命令行不如就是很多传统的命令行做的就是来流畅但是传统命令行那些APP很多时候并没有就是AI Integration然后很多时候你去写脚本的时候会很烦但是我们做出text completion的时候我完全可以就是说写完一堆代码然后我要去发个get commit的时候我直接就是说我就在命令行里面输入ats pb commits然后他就会自动把这个整个commit message写好然后我enter就可以发个commit这要不要稍微展开讲一讲这是一个什么样的feature因为刚开始我们没有介绍到OK OK我们PingWay就是开发流程大概是说我们先把收集操作系统这个用户数据到就是说有一个比较好的memory系统这一套做出来了然后我们做出这道系统出来之后我们其实在工程上就有一个类似就是framework你都会有一个就是比较好的一个markdown document这个markdown document它是会适时更新的包括这个用户的职业它包括用户就过去几天做了什么 Agent一直会有这个context然后我们有了这对context之后我们其实在做一件事情就是我们在寻找应用场景然后我们找到第一个就是说比较好的应用场景我们可以在操作系统任何一个地方去做一个类似自动补权autocomplete就比如说你在发微信的时候你可以就是说在你的文字框里面输入就是at pp这是个激活词然后后面就是输入一个比较简短的一个instruction或者说prompt就比如说你可以说也可以不输入也可以不输入他就会猜你在这个时候你at我就找我了对吧对你不输入他也会猜一猜你此刻找我是要我来干嘛对因为他有这个context比如说有一个同事过来可能我不需要对他说什么就一个眼神他就懂了为什么我在找他That's great对就比如说很多时候你和你的就是工程师你并不需要就是描述你只要点一下屏幕就你指下屏幕他就知道就是说看这儿对看这儿他一看就哦就这个问题对对然后当时Payrplay已经差不多达到这个效果OK所以说就不管你在回微信的时候做任何事情的时候他都会就是事实的有这个context description description实际上会比cursor或者说Hotcode传统的那些就是会好因为很多时候我开发一个就比如说比较大的feature或者说就是一会儿在和Cloudcode打交道一会儿我在微信里面和John去发什么消息然后一会儿我在浏览器里面去做research就是我也可以把这所有的这个context都聚合在一起然后并以一个PR的形式去给我做这个draft然后我会发现就他这个对我去做什么事情的这个理解程度会比就是任何机具单应用context的这个的这种agent或者AI会考很多还有吗我自我怀疑我有ADHD然后我在工作的时候很容易就是分心我经常就是在那个Cloud Code的时候旁边会看hacker news然后hacker news如果有什么比较有意思的article我可能就是点那个article然后点到时候我看了30分钟回来就是Cloud Code可能已经结束了十几分钟了其实对于这种情况就是我我记得我当时是我每天晚上就是会让Puribway就类似给我一个report就说我今天到底有多efficient我让他会去就是相当于骂我我什么时候就是不够高下我什么时候分神了我觉得对于我来说就是我平常工作的时候当我知道就是Puribway在盯着我工作的时候我会效率更高 [25:00] This is not Big Brother, is what I'm asking. the network effects businesses um you know sort of the successes and failures after the research i want to actually connect to that paperboy at that point i really have a bunch of just like things that's happening in my head and i need something to kind of like help me thread it through yeah it's like connecting the dots yeah yeah and then be able to tell me wait have you thought about this real quick you know you tried this you know maybe a couple months ago and this is the product form and these are the problems that you recognize the product right like i know about these things but they're when you're doing like that sort of thinking across different planes you can do it manually I should just send myself in front of the you know piece of paper I can sketch it out but it a lot faster to be able to have a very smart model that knows me to help me through that process this is the inspiration oh yeah uh i mean paperboy we started working on this new the latest interface two weeks ago it was um so i can talk a little bit about problems we had for example if you're shipping paperboy to vc and vc is definitely part of our ICPs. They want a personal CRM module. They want like meetings coming up module. They want like deals of the quarter or deals from module. They want to keep track of everything that's happening across all the portfolio companies. They want to keep track of their relationship with LPs, right? And so maybe you can ship like a sidebar where you have these like existing modules in place. Then the question is like, okay, we know this thing works for operators, for founders, for real estate salesmen. They all need a different sidebar. So what do we do? Do we ship these things as skills, as plugins, as recipes, right? And allow the user to like pick which one they want to add into their product? So you're thinking about this problem. And then Paperboy helps you. That doesn't make a lot of sense to me, right? So Paperboy pointed out to me that it was sort of like what application do we use that is well you obviously need a list but it an infinite list but it actually not annoying and then it came back to sort of the iam idea which is when you think about uh what's going on in our iMessage and we chats today we chat especially in china there are contacts and there are a bunch of group chats and then there are group chats where it's sort of like maybe you have like three people okay it's just three people, but like your three people can have four group chats for different topics. And it's actually a very intuitive way for people to organize their topics and things that are going on. Actually, we will get a new group and we will get a new group. Every group is a single group. Because there are several speakers in the same way to do the same thing. And then in the first place, it will be so混乱. So every time we open a new group, we will open a new group. Everyone will get a new group. And the great thing about IAM is, you don't have that group in the chat, it will be turned out. You can also choose the right key or the right key I do it all the time So my WeChat is sort of like this inbox So that was kind of the inspiration We know we also need an inbox feature So what if we don't design an inbox feature We just turn what is the thing that itself is an inbox It an IAM So that kind of how the latest interface came about So actually when we were talking about this if you haven used Paperboy it may need to be able to copy We've already explored a lot of Paperboy with different features and features, and unique communication and design. We'll also talk about this here. Actually, as we mentioned earlier, Capture and Context are a common theme. Everyone can do it. And what we mentioned about the new communication strategies or thinking about it I think if it really makes sense I think everyone will also follow up quickly So I want to ask the two how to fight against the competition Do you think the biggest opponent is who? And how do you keep the advantage and change in the competition? computer now and they have great distribution all we can pray for is we're like cursor you know where we have some edge in taste you know where we beat them to you know sort of this new interface and all of that is for is for individuals and product experience that's not going to go away but then also second thing is enterprise [30:00] Favor Boy definitely want to go into enterpriseI mean that's where the money isFavor Boy一开始其实想做的第一个产品是AI SlackThat was our answer initially to what to buildIf the best way to work with agentshaving been invented yet所以这也是现在非常热闻的一个赛道就是有很多的产品都在尝试解决当agent进入团队以后我们应该build一个什么样的产品去工作所以你怎么看现在市场上一些大家讨论比较多的产品比如说 Slack, Multica, Moxt,等等等等有没有你想讲的 Well first of all I love Slack I think Richard is brilliant he has a great background his co-founders are great and now they're building up a product team as well the hard part about AI Slack and this is from my personal POV how do you get enterprise to switch? AI Slack, the business model that makes sense is you have to sell it to a team it's the team that's paying for it and for enterpriseif there is a wayto exportall the datafrom slackand import itinto slackand it's a one to oneexperiencethen maybe it can workandbut you knowyou still have to builda bunch ofconnectorslike the integratorsfor all the otherdata the enterprisehasyeahso thatinfo workisn't going awaythe se second thing is that Slack is honestly not a great product. You know, like if you just try to build interface that's similar to Slack with channels and threads, to me, I don't enjoy using it. I still, well, you know, obviously at a scale, you kind of have to switch to it because nothing better exists right now. But it's not an enjoyable product to use. So that's all on the user side and getting adoption side. And then there's the agents. As Jed said, we don't believe that in the learning rates of the agents, if the only sources that they get for understanding how to work with people comes from the messages you send to them. People with jobs are busy. They do not have time to care about training agents. They expect things to work for them out of the box. They expect the product to keep getting better. So, and the reason we went away from Slack is that it's just like the agents in Slack is still We need more context for them to learn, you know, naturally Cool I think Slack actually has quite a lot of network effects Just like the John said, to stop They're being replaced by new players For example, Slack has a function called external connections Currently, all of the more transparent companies They actually use Slack And the communication between the complayer去替代掉的就比如说slack它其实还有一个功能叫external connections目前就是所有比较认真的公司其实都会用slack然后公司和公司之间的交流其实现在很大程度上并不是email而是通过external connections去进行然后这个是很难被替代的我觉得slack肯定还有就很多其他的这种integration方面的这些network effect就和现在微信一样让他们到一个就是某种程度上不可替代的一个方式然后相比就是如果你去把agent作为一个就是a layer above更加就是在OS层面或者说和Slack形成一个互补形式的一个东西的话我觉得反而会有更好的一个这个adoption story所以这是你们在做的事情吗就是尝试去和Slack有一些互补Yeah, we assume that initially if you try to go into enterprise there will be communicating on SlackIf you're building a Slack right now you can't really try to sell a thing to a team larger than maybe 50 peoplehow much it would take for them to switch off a Slackit would be a bit of work and it makes more sense again to bring the agents to where people already work instead of trying to replace and build everything from scratch我其实有注意到这个PaperBall目前的官网啊产品没有发布但是有放了一篇blog post然后这个标题叫做The Last Interface然后在那篇blog里面其实有提到这个5 kinds of speed就5种ive kinds of speed, so I can open it up a little bit. I understand this behind me, it seems like you're talking about how to understand the context layer and the memory system. Yeah, I don't want to go into too much detail, because actually the choice of using five isn't because we only have like five layers, it's just because that was like a sensible categorization. The important thing is like if you think about, Okay, so in SF, there is a nonprofit called the Langnao Foundation, and its founders do a brand that's published something called Pace Layers. So it's sort of like at the top, it's like fashion, and then there's like commerce, politics, or governance, and then infra, and then it's like civilization, it's like nature. And these are six places that changes at different velocities. So fashion obviously changes as fast as nature. Our understanding is that it doesn't really change physics. And the world is made up of these kind of different paces and sort of all have a relationship with each other. And they're reflexive relationships between every layer and largely the makeup of our society. I have been kind of fascinated with that since high school. And it's influenced definitely my worldview of what is the world that we live in, both the natural and social systems. [35:00] and you know when I think about what's actually efficient and what can scale for representing this world that we live in in the agent's world you need these different you know pace layers too yeah so it's quite interesting that what will do the same for nature? what will do the same for fashion? I think for the product to use if you use the task to make the task of the task to make a separate way 其实会有蛮多不同的种类 就比如说用户在微信上回一条消息 他只需要一秒钟或者说十秒钟 然后我觉得这是Spectrum的一端 然后Spectrum的另一端可能是说 用户去读十个非常非常长的一个report 然后去做一个business decision 去做一个决策 然后这个可能要花个几个小时 That's probably like closer to the left side too The long side is more like over a month Yeah like over a month Yeah 就basically有个Spectrum 然后我们认为就这个Spectrum I think it's every time they will be some kind of AI agent to augment or self-image But every time they need to do the things, it's not the same If you want to self-image, you can use the form factor You can use the form factor You can use the form factor You can use the form of the form This is what we have done But the time horizon is more and more Actually you have a lot of product Horizon你去自动化用户一个几个小时Task这个最好的form practice是什么这个其实目前还是一个非常值得被探索的一个区域我们也很感兴趣其实在录制一些播客之前我和Paperboy的团队也有一些交流然后发现团队里面好几个成员都有讲说他们认为每次和Jump沟通的时候感觉不到他是04年的就觉得他有超越年龄的成熟我实际上有这样的感觉我想问一下你觉得自己的这样的状态它是怎么来的是因为你过去做了什么或者看了什么或者被什么激发激励I think I'm still a pretty childish personespecially with chat aroundYou knowWe have a lot of fun togetherI think you're oldI think for the team at leastI definitely just have a passion for business我们要做什么很难的在很短的时间所以 clarity efficiency and focus这要怎么做到呢这个是一型难的那开始从我 define success job is to bring to the team define what success looks like and be able to make sure that the context every person has about their goals and how they actually operating are complete and accurate. Actually, even for me, the best part of being able to start a company is to get to learn so much of what I've always wanted to explore and just understand about the world. And that curiosity has probably been the biggest driver for me since high school you know between high school and college i took a couple internships and all of that are at different companies i just do different type of problem solving activities and then million obviously we started in the b2b business right selling yeah the web performance you know pr bots to large enterprises and then we learned that it's a difficult business to scale. We as 20-year-olds are not good at scaling up of enterprise relationships. So since then, I think I've been on this trajectory where I'm just trying to learn about, okay, what are the markets that actually make sense for different players? And the way I like to learn is not just for startups, but across different business scales to go with it. It like a founder market fit Yeah team Team market fit So I think market picking is one of the most important if not the most important trade of a founder early on It's making sure that you understand what you are going into, where are all the leverage points, where are all sort of the challenges coming down on you. And then you can actually go build a team, and then it's a product experience, you know, finding customers, technology. So here you have something to share with you, how to choose a market, the right market. Yeah, I think I'm about to say a bunch of common sense again. It has to be big enough. And this big isn't just dollar sign, but how sustainable is the market? And that scale has to keep increasing so your team can continuously develop your product and your market position across a decade. So when I look at the most successful products in history, it's never the single product. It's actually sort of like a product lineup where the expectation is when you build this thing, it's going to take maybe a decade for it to get to a form where it's really mass consumer or everybody's using it. Yeah, that's the first thing. You got to start with a problem close to you. It's all just sort of like a, to me, a method of understanding market. But then you need a lot of history to be able to understand if the business dynamics, you know, the economics are actually favorable and there have been success. [40:00] best cases in the past or not. Yeah, there's so many details, and I think I am just barely scratching the surface. Yeah, Paperboy is just my chance to kind of prove out what I know. Paperboy, you should be the first CEO. Because the company is a co-founder. So what do you think of the biggest change in your CEO? Man, it's fucking hard. I gotta own everything. I mean, as a co-founder, you definitely feel that too. I get frustrated when an engineer, for example, waits like an afternoon. But as CEO, no, I am actually the person that can cost the company the most amount of money because I have so much leverage, right? If I say we go do this and that is actually not a good idea, it's the position where literally all of your ideas can have such a large cost and reward. And then as the team scales, obviously, who do I choose to hire? Where do they come from? And then once they're hired, how do you continuously improve together for the individual and for the team? You know, making sure every person is obviously on the road that they deserve. I feel like these are basic management skills. This is basically my first time as a manager, too. So a lot of that I have to figure out on the spot. How do you give performance reviews How do you have one How do you make sure that you know sometimes I have to just talk to the team leader right and not to everyone and micromanage Before Paperboy, the one stint I had where I actually stayed at a larger company was Amanis. Amanis, man, Panpan is an amazing, amazing CTO. I mean, I haven't worked with any other, you know, real engineering managers, but he is a great engineering manager. And we've had the opportunity when I was a man is to have a couple one-on-ones where I just ask him all the questions I wanted to ask. How do you organize everything, man? And then I also spend time just like reading. I think the best management book I've ever written is still just like high output management by Andy Grove. And then Ben Horowitz, you know, he has the thing hard thing about the hard things. And then Bill Campbell, the trillion dollar coach, great biography. And I got myself a CEO coach. We meet weekly for like an hour. That's helped me a lot, especially like the first few calls, just helping me, having a space sort of to talk about all of the specific problems that I have. How did you find her? Investor intro. Okay Yeah It actually the same coach for the investor too Can you probably introduce her to her But then you can actually also talk about business You can talk about everything that's happening in the business And so you know it's confidential Also it's been really fun to use Paperboy With the coaching calls Because Paperboy listens to the calls And it can actually help me follow up On things that I committed to doing On calls and organizing everything Yeah So you know how do you see For example today Because you said there are 10 people But actually today Not every team has so many people You have no small team size. So I'm curious, in your opinion, in the situation of today, there are so many tools, AI agents, to build a team and to build a team and to build a team. There are some big changes that are happening. If you try to make a serious infra structure build out you need people who understand infra I think we hired two kinds of people on the engineering side One is like Jet who are like young, high IQ, creative, just prototypes of shit out of every problem that he sees. And then second kind is like, you got to be real solid at what you do. You got to understand the systems. You got to understand the OS. So we hired this guy out of AWS who worked on like Windows kernels for the AWS like infra for the running window. I don't think that's going to go away anytime soon The human experts其实这个Jet现在大一对吧对我们看到硅谷有一些公司比如Palantir直接给高中生offer让他们不要读大学了直接工作因为认为在AI时代不需要大学了那很显然其实Jet也是优秀的这个大一学生但你也在PaperBall是Funding Engineer那你为什么现在还要读大学啊He's got Chinese parents意义的话其实对大部分来说大学还是能提供非常大的意义因为 至少我在CMU这边看见就大部分其实和我同学的人他们其实并不是很确定未来想要做什么事情 然后你在不确定的情况下就是你可以做的是什么你可以提升你自己的就是technical能力上大学是个比较好的一个选项 就学业只会占你就相对比较少的一个时间你大部分其他时间就是说是你自己决定的然后相当于四年的时间 [45:00] 去做这个exploration然后这个四年时间其实是对大普普来说会是比较有用的但是同时就如果你在上大学的时候已经很确定你想要做什么事情然后并且就是说你做事情这个方面确实机会我觉得辍学也是一个理性的选择对这个Jump你做一个非常年轻的founder也是first time founder你怎么吸引到同学们愿意加入你的就是你要怎么说服大家这样什么方面吸引到我你关键到的因为对大家来说职业选择是非常重要的这个人生投资很多时候你选一个founder也是你有intercept你有slope然后很多时候slope比intercept重要很多然后我觉得John是一个就是high slope的founder怎么说就是他现在就如果你看他的这个track record的话他现在就差不多比我大所以相当于他就是在一个很小的时间内就是说实现了特别多比较厉害的事情然后就这一定程度上他是比较就比较有agency然后就是他这个可以很快的去学习然后并且可以去做非常多的新事情然后对于一个创业者来说这个arguably是最重要的一个quality就是说你得要能你头脑心心你得要能就是很快的去适应各种的情况首先你得要认为他是一个就是good founder对于我来说就首先我和张已经就是工作了比较久所以说就是我在和他合作我有比较高的confidence说就是我们可以就是比较顺畅的合作然后张他也有不错的research engineering甚至product的这个taste然后我觉得就是说和他在工作的过程中我可以就是进去很多这种经验然后让我个人也有更好的成长我个人觉得张还是就算比较就是charismatic的一个人大型表白现场 I appreciate it So how do you tell yourself Do you have some ways to summarize your抽象比如你现在去 approach一个新的 candidate你会有一些什么样的方法去说服他 I treat every candidate individually and there's not like a script I stick to It has to be mutual I never like to sell the company to a candidate like hard sell and recruiting is one thing what's more important是关于我的信息我认为我其实会负很多关注是在我会的我会叫做一个人我会把我送给你我会把我送给你可以把我送给你让我送给你我会送给你你给我送给你你给我一个人的你给我送给你你给别人的你给别人的你不要跟别人的你不要跟别人的你可以从从你的经济从你的经济从我的经济尤其是 You've got to pick people who are great, man. You can't talk to mediocre people. And you can tell that from conversations about their past work. And what's especially important is their past life decisions. I really like to learn about, you know, if they're older, they have a decade sort of decisions behind them. And you can really learn a lot. You can't fake that. Can you share your most of your AI products? Apart from Paperboy. Yeah, I still love Cursor, man. I still don't use Codex. I really like Codex. Cursor has always been a great inspiration to me. I'm really happy for them. I hope that whatever acquisition happens go through. This is John's first co-founder, when he was a billion, that was actually a purchase from Devin. That was from Devin's company, Cognition. Yeah, there were other offers too, like from Brussels and Century. Wow. So you never had these offers. Yeah. And at that time, you can tell us about how to purchase offers. 首先, these are aqua hires. You know, whatever offers for the talent, there's not going to be a lot of money. Okay. And you're, you know, you're joining the companies and sort of just like another employee. And you have to work on somebody else's ideas. I've never been interested in debt tools that much. So if you ask me to join Sentry or join Vercel or join Cognition as an individual, I think I wouldn't do it, right? So it doesn't really make sense. If you can stay independent and if you can achieve your dreams like by staying independent, you should stay independent, right? And that's what every founder wants. Let's say back to you. You mentioned the most favorite thing is Cursor. And then Codex. Can you tell us why Codex is codex而不是 Cloud Code Cloud Code它理念不一样就是它那个相当于以最ambitious的形式就是说你未来就是说这个soft engineer会是怎么work我觉得 Cloud Code它那个最重要的东西是体现Opus有多好不是说它那个命令行有多好我appreciate那个Opus的模型我不是很appreciate Cloud Code那个DLI本身Codex我喜欢它几个点一个就是说它核心的agent是开源的它的命令行还有那个整体的agent loop它实际上都放在Github上然后如果你用他们那个桌面端的app的话 把那个中边端的app去和就比如说高购那个中边的app比他那个整个app就是他那个craft的水平就是会非常非常好他们前面买了一个团队叫sky然后sky就是他们是做apple shortcuts的那个团队然后open 就是会还是这种人去做一个非常polished的产品然后你去看codex的话你会发现他们就比如最近出了一个叫codex test的一个东西 [50:00] 就非常polished然后也很好玩然后包括Codex的computer usebrowser use其实都做得非常polished然后我觉得Codex其实也是第一个就是高并行式的就是说你不同agent的同时去工作的一个东西当做主要UI的一个产品然后也push出来然后还有就是OpenAI在那个infra层面其实比anthropic优势大非常多所以说如果你用Codex的话模型大差不差但是稳定很多大意思就是OpenAI在infra上面其实可以subsidize更多的compute然后anthropic他们现在就是投资的不够所以他们没法subsidize然后导致了一系列风波就比如说你的repo里面有什么open cloud或者说hermes agent然后cloud code可能会直接收你十倍的价格反正就anthropic现在因为compute受限去做很多奇怪的操作如果可以买他们的secondary就可以买他们的股票你现在会买open AI还是买anthropic还是你会各三期开买还是怎么样我感觉我会买open AIAll in OpenAI可能就是比如说OpenAI 80%然后Antwerp的20%OK什么原因呢就是他们两个公司都会do very well但是我更喜欢OpenAI在做的事情我觉得Antwerp做的最好的事情是他们的interpretability还有他们的social impact那那两个部门做得非常非常好然后我特别喜欢那两个东西但是anthropic在就比如说很多模型我觉得他们过于opiniated就是说用户该怎么用这个language world会非常就比如说不管是道德上还是具体使用习惯上会非常opiniated然后相比之下open AI的理念是说就是在一个最小的一个局限性之下就是用户想要怎么用这个模型就怎么用然后我个人会比较libertarian我会喜欢就是OpenAI这种更加unapenient的这种values然后还有就是我觉得OpenAI在compute上面会占优势I'm not gonnaIf I'm making investment decisionsI'm not gonna buyeither of themat the current valuationBut I actually preferAnthrope'sI think safetyCommitment and safety那你们怎么看就是模型吞噬一切这个说法我觉得你完全可以argue就是很多公司会提供差不多的模型然后产品的差异性还是在产品公司里面就是这不一定会是真的但是我觉得这是一个possible的然后还有cursor我觉得是一个不错的一个example就是他们一开始产品公司但是现在他们既是产品公司又是模型公司他们现在可以用XAI的这个compute去就是frontier coding model所以我觉得就是公司不能把自己局限为就是模型公司还是产品公司it's usually both. If you can invest 300 million dollars, you can invest three people in the world. Slack is good. Just a bet on Richard. Robotics companies, I think that's definitely going to be big. And then Infra, people who are focused on Infra. And then I believe the biggest company, similar to Cursor, is going to come out of consumer. It's not going to come out of enterprise AI. It's going to come out of consumer. And obviously Paperboy is in that market because of all that belief. But yeah, consumers are such a big market. There's so many opportunities. I think robotics will be very helpful. Because I think in this kind of automation, The problem with that is how do you compete with Anthropic getting into that business? Anthropic OpenAI will have the best model. The problem is that you have a good design After the optimization layer, what is the best way to do? What is the best way to do? Is it a better way to harpec OpenAI肯定会有最好的模型问题是就是你有最好模型之后你下了一个optimization layer是什么你是做比较好的harness吗你是把人类security researcher的各种就是heoristic big到agent里面还是说你去做infra就比如说非常庞大的一个multi agent系统去不断的去挖这些漏洞我觉得这个探索空间会非常大就比如说就你这个产品挖的漏洞会比另外一个产品比如说多个10%那么你这个产品就是非常有用的这是一个非常 meritocratic的一个 market所以我觉得这是个不错的我们还没有说过Long Horizon emails yet但Harvey shipped this thingLong Horizon law然后我认为其他张杨阳 shipped this new sweet bench今天或最近 reproducing complete co-bases instead of stocks or specs那是不会走过我觉得安全能力对于国家安全是非常非常重要的一个事情但我觉得对于创业来说这也是非常好的一个 opportunity因为就是模型最强的人他有这个incentive去把这个模型说只有我们自己国家可以用这个东西那么相当于你其他国家怎么搞呢你其实很多很多不同的就是国家或者说力纪元都需要这种模型所以说这个market是非常大的我们最后问个问题你会期待就一年后的这个 [55:00] 此刻Paper Boy是一个什么样的状态? 你有一些什么样的期待? 或者你有一些什么样的害怕做错的事? Well, I hope we're not losing money every day anymore. I want to keep hiring the best people I can find. So the talent density needs to be higher than, you know, where we're at today. I mean, there's so much specifics we can talk about, but I think from a team and like business point of view, it's just that we actually need cash flow, and we need to keep building a better team. Okay,好,谢谢二位. 谢谢,非常开心. Bye bye