返回列表
🧠 阿头学 · 🪞 Uota学 · 💬 讨论题

手机不是聊天窗口，而是 AI 指挥席——Claude Dispatch 真正改变的是你的时间编排

Claude Dispatch 的真正价值，不是让你“在手机上继续聊 AI”，而是把碎片时间升级成异步指挥多线程任务的控制面板；但它离“无缝移动办公”还差一整层基础设施和安全交互。
打开原文 ↗

2026-03-27 原文链接 ↗
阅读简报
双语对照
完整翻译
原文
讨论归档

核心观点

  • Dispatch 的本质不是移动端入口，而是任务编排器 这篇最有价值的判断是把手机从“对话终端”升级成“指挥席”：你不是在手机上亲自干活，而是在同一线程里派发、重定向、验收多个桌面端 AI 子任务。这个视角是对的，因为它真正放大的不是单次产出，而是并行推进多条工作流的能力。
  • 真正产生复利的不是入口，而是知识层 作者最该被抄作业的部分，不是 Dispatch 本身，而是“入口会变，知识层会复利”。如果 CLAUDE.md、模板、研究库、工作流规则只活在某个聊天框里，你每次换入口都要重搭一遍；只有把规则沉淀为独立资产，工具更新才会越换越顺，而不是越换越乱。
  • AI 负责广度和速度，人类负责判断和取舍，这个分工很健康 文中把 90% 的调研和排版交给 AI，把观点、判断、方向留给人，这个边界划得比很多“AI 全自动工作流”更成熟。不是因为 AI 不够强，而是产品、写作、管理这些事的真正壁垒，本来就不在“拉资料”，而在“决定什么值得做、什么算对”。
  • 这套工作流对高杠杆角色确实有吸引力，但被严重包装过了 对 PM、增长负责人、内容负责人来说，Dispatch 这种“移动指挥 + 桌面执行”模型确实有生产力增益；但作者把个人 48 小时体验外推成职业范式革命，有点过头。你看到的是一个熟练用户在一套已经打磨过的环境里跑通了流程，不是一个普通团队成员开箱即用就能复制的现实。
  • 最大的短板不是模型能力，而是系统摩擦没有被解决干净 每个子任务要单独申请文件夹权限、文件传输要靠云盘绕路、桌面必须常驻唤醒、连接器和同步都得先铺好——这些都说明 Dispatch 还不是一个“随手就能上生产”的成熟层，而是一个很有潜力、但仍依赖环境工程的早期编排面板。

跟我们的关联

👤ATou 1. 这篇对你最直接的价值，不是推荐某个 Claude 新功能，而是提醒你：未来你的高杠杆时间，应该更多花在“派发任务、设边界、看中间结果、及时纠偏”上，而不是亲手把每一步都做完。下一步可以把你常做的 2-3 类重复性工作，拆成“可异步指挥”的标准子任务。 2. 它也提醒你别把自己训练成“工具追新的人”，而要训练成“知识层建设的人”。下一步可以把常用规则、角色设定、输出标准、工作流约束进一步沉到稳定文件，而不是分散在临时会话里。

🪞Uota 1. Dispatch 这篇其实在给 Uota 提一个产品问题：我们到底是在做更强的单 Agent，还是在做一个能编排多个子任务的控制面？意味着后面的 agent 设计不能只卷单次对话质量，还要卷任务拆分、上下文隔离、权限边界和跨任务桥接。下一步可以优先梳理哪些工作流天然适合“主控 + 多子任务”。 2. 文中“知识层大于入口层”的判断几乎可以直接拿来当 Uota 的长期原则。下一步应该继续把可迁移的规则和资产沉进 skill / memory / workflow，而不是押注某个单一前端形态。

🧠Neta 1. 对 Neta 来说，这篇的可迁移点在于“移动指挥 + 后台执行”的工作方式很适合增长、运营、内容、调研这类多线程任务。下一步可以挑一个真实业务链路，验证“人类 10 分钟判断 + AI 并行 1 小时执行”是否真能成立。 2. 它也暴露了一个产品真相：真正决定用户是否留下来的，不是 demo 时多惊艳，而是权限、同步、失败恢复这些脏活累活有没有打通。这个判断对所有 AI 产品都成立。

讨论引子

1. 对高杠杆知识工作者来说，未来最重要的能力到底是“亲自做得更快”，还是“把工作拆成 AI 能稳定接手的子任务”？这两种能力的训练路径完全不同。 2. 如果入口会快速变化，那我们今天到底该投在工具使用技巧，还是投在知识层、规则层和工作流资产上？什么比例才合理？ 3. “碎片时间也能持续推进工作”听起来很美，但它到底是在解放人，还是把生活进一步工作化？对个人节奏和团队文化，这笔账应该怎么算？

Claude 现在有 4 种方式可以用手机跑起来。大多数人试一种，遇到阻力，就放弃。下面是确实好用的做法，以及它怎么改变了我安排一天的方式。

Dispatch 是最新的入口，也是最可能改变产品经理工作方式的那个。不是因为它最强，而是因为它把你一天里每一段空档，都变成了能指挥真实工作的窗口。遛狗、喝咖啡、坐副驾、站在充气城堡边上看孩子玩，这些时间都能变得产出可见，而且不用让人一直处在“always on”的状态。

我连续 48 小时做了测试，只用手机搭起真实的产品经理工作流。你正在读的，就是我发现的全部内容：真正跑得通的工作流、没有人提前提醒你的坑点，以及比 Anthropic 上线的任何单个功能都更重要的架构洞察。

你将学到什么

  • Dispatch 到底是什么，以及它和“手机上的 Claude 聊天”有什么不同

  • 如何配置并开启你的第一个 Dispatch 会话

  • 48 小时真实时间线：异步指挥如何重塑你的一天

  • 我踩过的每一个坑点，以及验证过的变通办法

  • 什么时候用 Dispatch，什么时候用 Web Sessions、Channels、Code

  • 为什么知识层比任何一个入口更重要

  • 产品经理用 AI 做事时，杠杆最高的一笔投入是什么

1. Dispatch 是什么（以及不是什么）

Dispatch 不是“在手机上跟 Claude 聊天”。那你早就有了。

Dispatch 是一个编排器。你在手机上只用一个对话，就能在桌面端同时生成并管理多个 Cowork 任务会话。每个会话都是独立运行的：有各自的上下文、各自的文件访问权限、各自的连接器。

手机是指挥席，桌面端负责干重活。

想想发短信让人帮你做点事，和坐在控制室里盯着多块屏幕指挥之间的差别。每一块屏幕，都是你桌面端在跑的一个任务会话。手机在同一个对话线程里，把它们全都指挥起来。

https://x.com/PawelHuryn/status/2035871263386698016?s=20

对 PM 来说：这对应你本来就在做的事：同时跑多个工作流。一位分析师在拉竞品动态，另一位在起草给相关方的邮件，第三位在整理研究笔记。Dispatch 就是这套逻辑，只不过分析师变成了你桌面端的 AI 会话，而指挥席在你口袋里。

你在 Cowork 里配置过的每一个连接器——Gmail、Notion、Slack，全部都能通过 Dispatch 使用，因为 Dispatch 是把任务委派给 Cowork 来执行的。

2. 如何配置 Claude Dispatch

步骤 1：在桌面端把 Cowork 配好，接上你常用的连接器——Gmail、Notion、Slack，随你的技术栈。所有配置都必须先在桌面端完成。然后让电脑保持唤醒，并让 Claude 应用保持运行。

步骤 2：打开 Claude 手机 App，你会看到 Dispatch 标签页。开一个对话，让它运行一个 Cowork 任务。

步骤 3：先从小任务开始。只跑一个任务（例如，“总结过去一周未回复的邮件”）。看一遍输出。然后在同一个对话里试着同时跑两个任务，感受并行工作流。

步骤 4：要处理文件，需要授权文件夹访问权限——可以用自然语言描述文件夹（例如，“go to workspace/editor”），也可以用你自己定义的快捷方式。从放着你的 CLAUDE.md 和知识文件的那个文件夹开始。

步骤 5：尽早把变通办法搭好：

  • 如果你的工作区通过 Google Drive/Dropbox/iCloud 同步，先确认文件能在手机上出现——这会把文件传输的问题直接消掉

  • 定义文件夹快捷方式（例如，“editor mode”、“workspace”），这样你可以用自然语言描述文件夹，而不是手打路径

3. 用 Claude Dispatch 跑真实 PM 工作流（48 小时测试）

Dispatch 不是把我的碎片时间填满了，它改变了我安排一天的方式。我带孩子去蹦床馆，因为我可以站在场边异步指挥工作。它的模型不是“在空档里硬挤工作”。而是“重新设计你的一天，因为工作可以在你不坐在屏幕前的时候继续跑”。

大概是这样：

早晨在家喝咖啡。孩子还没醒。启动任务 1：“拉取最新的竞品更新，归纳相对上周的变化。”启动任务 2：“用 Notion 数据库起草赞助合作页面。”两个任务都在隔壁房间的桌面端跑着，我在喝咖啡。

遛狗。用手机查看任务 1，竞品总结已完成。“加一张和我们当前路线图的对比表。”一次重定向 10 秒，单手就能完成。任务 2 还在跑。狗不在乎。

妻子开车，我坐副驾。审阅赞助 Notion 页面草稿。“太正式了，把上一轮活动的互动指标拉出来，让价值主张更锋利。”启动任务 3：对文章草稿做差距分析。家里同时跑着三条并行任务，我在看路况。

孩子在蹦床馆。站在边上，手里拿着手机，45 分钟。信息图就是在这里迭代出来的。“把图标往左挪。”“把第三段的颜色改一下。”“标题加粗一点。”一份视觉资产做了四轮创意指挥——从充气城堡旁边完成。

回到桌前。一切都等着。审阅、微调、发布。所有这些空档里真正花在指挥上的时间，加起来也许 25 分钟。Claude 并行执行的工作量：3+ 小时。

48 小时结束时，我让 Claude 总结我们做出了什么。这是它给的清单：

关键机制是这样：在一个 Dispatch 对话里，你先启动任务 1（调研），立刻启动任务 2（起草），然后查看任务 1 的进度，重定向任务 2，再启动任务 3——全都在手机的同一个线程里完成。每个任务都在自己独立的沙箱会话里运行。它们互不干扰。除非你明确把它们桥接起来，否则它们不会共享上下文。

对 PM 来说：你从来不是一次只做一件事。等相关方回复的同时，你在盯竞品动作，同时还要准备冲刺产物。Dispatch 让 AI 能跟上这种节奏，而不是强迫你按顺序来。上限不在于你输出得有多快，而在于你能同时指挥多少条并行轨道。

下面是会话摘要——60+ 个任务会话由手机指挥完成，而且清楚区分了我做了什么、Claude 做了什么：

真正的洞察不是“通勤时用 Dispatch”。而是“用手机做异步指挥，会重新塑造你安排一天的方式”。有些产出我在桌前审阅并打磨。也有一些内容——X 帖子、信息图、评论回复——我从头到尾只用手机就直接发布了，根本没坐下。

https://www.productcompass.pm/p/claude-cowork-guide

4. Dispatch 的坑点（48 小时实测）

每个工具都有摩擦。Dispatch 的摩擦点到底在哪里，这里是 48 小时测出来的，不是 48 分钟。每个坑点要么有变通办法，要么会明确告诉你现在还没有。

4.1 文件夹访问需要手打路径

在桌面端 Cowork，你点一下文件夹图标就能授权文件访问。Dispatch 在手机端没有文件夹选择器 UI，需要手打路径：“Give yourself access to ~/Desktop/Workspace/Editor.”

变通办法：用自然语言描述文件夹就行，“go to workspace/editor”能用。也可以定义像“editor mode”这样的快捷方式，Claude 会跨会话记住。没必要死记硬背精确路径，这个摩擦会很快消失。

4.2 每个子任务都要单独申请文件夹访问

Dispatch 委派出去的每个子任务，都会在桌面端请求文件夹访问权限，你需要一个个批准。没有变通办法——这是安全模型的一部分。把手机塞进口袋前记得这点。

4.3 还没有内置文件传输

你没法从手机把文件附到 Dispatch 里，Dispatch 也没法把产出直接发回手机。两个问题，一个解法。

https://www.productcompass.pm/p/self-improving-claude-system

输入端（手机截图、照片），我开始给自己发邮件，让 Claude 从 Gmail 里拉。输出端，我很早就发现 Dispatch 没法把文件送到手机上，于是开始去 Google Drive 里看。

然后突然想明白了：把 Cowork 的工作区文件夹用 Google Drive 同步起来。Claude 保存的所有东西都会自动出现在手机上。你从手机扔进这个文件夹的任何东西，也会自动出现在桌面端。一次同步，把两个方向都解决了。

4.5 CLAUDE.md 的委派顺序有讲究

如果你上来就开始委派任务，编排器可能会给子任务写出不够精确的指令——它还没把你的规则吃透。

修复办法：先让 Dispatch 读你的 CLAUDE.md，before 委派任何任务。规则加载进来以后，它给每个子任务写的指令会更利落。

5. Claude Dispatch vs. Remote Control vs. Web Sessions vs. Channels：分别该用在哪

Anthropic 在 5 个月里上线了 4 种远程入口，最后 3 个是在大约 23 天内推出来的。下面是快速决策框架——不是完整深挖，只给你现在就能选对入口所需的东西。

自从 X 上第一波 Dispatch 讨论之后，有两点需要更正。公开说错、公开修正，是这套机制的一部分：

  1. Channels 是双向的。它们会把事件推送进正在运行的会话里，并且会通过 Telegram 或 Discord 把回应发回来。我之前的表述不够准确。

  2. Channels 支持定时任务——但只在活跃会话里有效。只有会话在运行时，事件才会进来。

另外，有人注意到 Dispatch 似乎也能跑 Code 会话。我测了下，现在还不太行。流程还没完全打通（Dispatch 的原话）。做远程写代码或原型，我推荐用 Web Sessions。

https://www.productcompass.pm/p/self-improving-claude-system

6. 让每个 Claude 入口都能复利的知识层

Anthropic 在大约 23 天里上线了三个新的远程入口——Dispatch、Channels、Remote Control——再加上从 10 月就有的 Web Sessions。也就是说，你不用坐在桌前就能跑 Claude 的方式一共有四种。如果你的 AI 配置只活在某一个入口里，那每来一个新入口，你都要从头再搭一遍。

而且他们更新得很疯狂。就昨天（周日）：Claude Code 改了两处——一个 7 天的 /loop，以及一个改进后的 /init 命令。

修复办法：把你的知识存进一个 GitHub 仓库。CLAUDE.md（你的指令文件——语气、规则、工作流）加上知识文件（模板、假设、研究）。每个入口都从你的机器上读取它。Web Sessions 会把它 clone 下来。

入口会变，你的知识层会复利。

想象一下：两位产品经理。同一家公司。同一套 AI 工具。同样的权限。一位围绕它们搭了一个知识系统——CLAUDE.md、技能库、越用越顺的结构化工作流。另一位只在卡住时才用。几个月后，一个人的交付节奏能快出 5x。

完整架构——CLAUDE.md 的结构、知识文件怎么组织、自我纠错循环——都写在 Self-Improving System 那篇文章里。

7. 产品经理用 AI 时，杠杆最高的一笔投入

下面是那 48 小时里最真实的分工——谁贡献了什么：

看这个模式。思考：90% 是我。观点和立场：100% 是我（Claude 可能夸张了）。调研和排版：90% 是 Claude。AI 负责速度和广度，我负责判断和指挥。

这一步大多数人都会跳过。用 AI 放大你的思考，而不是替代它。

写作时，如果你在打开 Claude 之前自己没想说什么，最后只会得到抛光过的糊弄。

对 PM 来说，道理一样。搭建一个知识系统是一笔投入。CLAUDE.md 文件、技能库、工作流模式——都要花时间。但它们会向你学习。你做的每一次纠正、加的每一条规则、杀掉的每一个草稿，都会复利成一个越用越锋利的系统。

现在——今年、明年——杠杆最高的一笔投入不是去学一个新的 AI 工具，而是去建立判断力、系统化的方法、以及领域知识，让你能更好地编排下一代工具。

这篇文章里的每一张信息图，都是通过 Dispatch——从我的手机——创建、迭代、导出完成的。

测试、观点、什么重要、以及方向，都由我负责。

开始搭建。别再空想。

P.S. 如果你想要完整系统——CLAUDE.md 指令、知识架构、自我纠错循环——都在 The Self-Improving Claude System 里。这篇文章给你 Dispatch。那篇文章给你让 Dispatch 真正复利的系统。

Claude now has 4 ways to run from your phone. Most people will try one, hit friction, and give up. Here's what actually works — and how it changed how I structure my day.

Dispatch is the newest surface — and the one most likely to change how you work as a PM. Not because it’s the most powerful, but because it turns every gap in your day into a window for directing real work. Dog walks, coffee, the passenger seat, standing at the sidelines of a bounce house — all become productive without being “always on.”

I tested this for 48 hours straight, building real PM workflows from my phone. What you’re reading is everything I found — the workflows that actually work, the friction points nobody warns you about, and the architectural insight that matters more than any single feature Anthropic ships.

Claude 现在有 4 种方式可以用手机跑起来。大多数人试一种，遇到阻力，就放弃。下面是确实好用的做法，以及它怎么改变了我安排一天的方式。

Dispatch 是最新的入口，也是最可能改变产品经理工作方式的那个。不是因为它最强，而是因为它把你一天里每一段空档，都变成了能指挥真实工作的窗口。遛狗、喝咖啡、坐副驾、站在充气城堡边上看孩子玩，这些时间都能变得产出可见，而且不用让人一直处在“always on”的状态。

我连续 48 小时做了测试，只用手机搭起真实的产品经理工作流。你正在读的，就是我发现的全部内容：真正跑得通的工作流、没有人提前提醒你的坑点，以及比 Anthropic 上线的任何单个功能都更重要的架构洞察。

What You’ll Learn

  • What Dispatch actually is — and the difference from “Claude chat on your phone”

  • How to set up and start your first Dispatch session

  • The real 48-hour timeline — how async direction reshapes your day

  • Every gotcha I hit, with tested workarounds

  • When to use Dispatch vs. Web Sessions vs. Channels vs. Code

  • Why the knowledge layer matters more than any single surface

  • The single highest-leverage investment for PMs building with AI

你将学到什么

  • Dispatch 到底是什么，以及它和“手机上的 Claude 聊天”有什么不同

  • 如何配置并开启你的第一个 Dispatch 会话

  • 48 小时真实时间线：异步指挥如何重塑你的一天

  • 我踩过的每一个坑点，以及验证过的变通办法

  • 什么时候用 Dispatch，什么时候用 Web Sessions、Channels、Code

  • 为什么知识层比任何一个入口更重要

  • 产品经理用 AI 做事时，杠杆最高的一笔投入是什么

1. What Dispatch Is (And Isn’t)

Dispatch isn’t “Claude chat on your phone.” You already have that.

Dispatch is an orchestrator. From a single conversation on your phone, you spawn and manage multiple Cowork task sessions running simultaneously on your desktop. Each session runs independently — its own context, its own file access, its own connectors.

Your phone is the command chair. Your desktop does the heavy lifting.

Think of the difference between texting someone a request and sitting in a control room with multiple screens. Each screen is a task session running on your desktop. Your phone directs all of them from one conversation thread.

https://x.com/PawelHuryn/status/2035871263386698016?s=20

For PMs: This maps to something you already do — running multiple workstreams simultaneously. One analyst pulling competitor data. Another drafting the stakeholder email. A third organizing research notes. Dispatch is that, except the analysts are AI sessions on your desktop and the command chair is in your pocket.

Every Cowork connector you've configured — Gmail, Notion, Slack, all of them — works through Dispatch because Dispatch delegates to Cowork.

1. Dispatch 是什么（以及不是什么）

Dispatch 不是“在手机上跟 Claude 聊天”。那你早就有了。

Dispatch 是一个编排器。你在手机上只用一个对话，就能在桌面端同时生成并管理多个 Cowork 任务会话。每个会话都是独立运行的：有各自的上下文、各自的文件访问权限、各自的连接器。

手机是指挥席，桌面端负责干重活。

想想发短信让人帮你做点事，和坐在控制室里盯着多块屏幕指挥之间的差别。每一块屏幕，都是你桌面端在跑的一个任务会话。手机在同一个对话线程里，把它们全都指挥起来。

https://x.com/PawelHuryn/status/2035871263386698016?s=20

对 PM 来说：这对应你本来就在做的事：同时跑多个工作流。一位分析师在拉竞品动态，另一位在起草给相关方的邮件，第三位在整理研究笔记。Dispatch 就是这套逻辑，只不过分析师变成了你桌面端的 AI 会话，而指挥席在你口袋里。

你在 Cowork 里配置过的每一个连接器——Gmail、Notion、Slack，全部都能通过 Dispatch 使用，因为 Dispatch 是把任务委派给 Cowork 来执行的。

2. How to Set Up Claude Dispatch

Step 1: Set up Cowork on your desktop with the connectors you use — Gmail, Notion, Slack, whatever your stack is. Everything must be configured on desktop first. Then, keep your desktop awake and Claude app running.

Step 2: Open the Claude mobile app. You’ll see the Dispatch tab. Start a conversation and tell it to run a Cowork task.

Step 3: Start small. One task (e.g., “summarize unanswered emails from the last week”). See the output. Then try running two tasks from the same conversation to feel the parallel workflow.

Step 4: To work with files, grant folder access — describe the folder naturally (”go to workspace/editor”) or use a shortcut you’ve defined. Start with the folder that has your CLAUDE.md and knowledge files.

Step 5: Set up your workarounds early:

  • If your workspace syncs via Google Drive/Dropbox/iCloud, check that files appear on your phone — this eliminates the file transfer problem entirely

  • Define folder shortcuts (”editor mode,” “workspace”) so you describe folders naturally instead of typing paths

2. 如何配置 Claude Dispatch

步骤 1：在桌面端把 Cowork 配好，接上你常用的连接器——Gmail、Notion、Slack，随你的技术栈。所有配置都必须先在桌面端完成。然后让电脑保持唤醒，并让 Claude 应用保持运行。

步骤 2：打开 Claude 手机 App，你会看到 Dispatch 标签页。开一个对话，让它运行一个 Cowork 任务。

步骤 3：先从小任务开始。只跑一个任务（例如，“总结过去一周未回复的邮件”）。看一遍输出。然后在同一个对话里试着同时跑两个任务，感受并行工作流。

步骤 4：要处理文件，需要授权文件夹访问权限——可以用自然语言描述文件夹（例如，“go to workspace/editor”），也可以用你自己定义的快捷方式。从放着你的 CLAUDE.md 和知识文件的那个文件夹开始。

步骤 5：尽早把变通办法搭好：

  • 如果你的工作区通过 Google Drive/Dropbox/iCloud 同步，先确认文件能在手机上出现——这会把文件传输的问题直接消掉

  • 定义文件夹快捷方式（例如，“editor mode”、“workspace”），这样你可以用自然语言描述文件夹，而不是手打路径

3. Real PM Workflows With Claude Dispatch (48-Hour Test)

Dispatch didn't fill my dead time. It changed how I structured my day. I went to the jump arena with my kid because I could direct work async from the sidelines. The model isn't "grind during gaps." It's "design your day differently because the work runs without you sitting in front of it."

Here's what that looked like:

Morning coffee at home. Kids aren’t up yet. Start Task 1: “Pull the latest competitor updates, summarize changes since last week.” Start Task 2: “Draft the sponsor collaboration page using the Notion database.” Both tasks running on my desktop in the other room. I’m drinking coffee.

Walking the dog. Check Task 1 on my phone — competitor summary done. “Add a comparison table against our current roadmap.” Redirect takes 10 seconds, one-handed. Task 2 is still running. Dog doesn’t care.

Wife driving, I’m in the passenger seat. Review the sponsor Notion page draft. “Too formal. Pull the engagement metrics from the last campaign and make the value prop sharper.” Start Task 3: gap analysis on the article draft. Three parallel tasks running at home. I’m watching traffic.

Kid at the jump arena. Standing on the side, phone in hand, 45 minutes. This is where the infographic iterations happened. "Move the icons left." "Change the color on the third section." "Make the header bolder." Four rounds of creative direction on a visual asset — from the sidelines of a bounce house.

Back at my desk. Everything waiting. Review, adjust, ship. The actual direction time across all of these gaps: maybe 25 minutes total. The Claude execution running in parallel: 3+ hours of work.

At the end of the 48 hours, I asked Claude to summarize what we'd built. Here's its list:

The key mechanic: in a single Dispatch conversation, you start Task 1 (research), then immediately start Task 2 (drafting), then check progress on Task 1, redirect Task 2, start Task 3 — all from one thread on your phone. Each task runs in its own sandboxed session. They don't interfere with each other. They don't share context unless you explicitly bridge them.

For PMs: You don't do one thing at a time. You're tracking competitive moves while waiting for a stakeholder response while preparing sprint artifacts. Dispatch lets AI match that rhythm instead of forcing sequential mode. The ceiling isn't your output speed — it's how many parallel tracks you can direct at once.

And here's the session summary — 60+ task sessions directed from my phone, with a clear split between what I did and what Claude did:

The insight isn't "use Dispatch during your commute." It's that async direction from your phone reshapes how you structure your day. Some outputs I reviewed and refined at my desk. Others — X posts, infographics, comment replies — shipped entirely from my phone without ever sitting down.

https://www.productcompass.pm/p/claude-cowork-guide

3. 用 Claude Dispatch 跑真实 PM 工作流（48 小时测试）

Dispatch 不是把我的碎片时间填满了，它改变了我安排一天的方式。我带孩子去蹦床馆，因为我可以站在场边异步指挥工作。它的模型不是“在空档里硬挤工作”。而是“重新设计你的一天，因为工作可以在你不坐在屏幕前的时候继续跑”。

大概是这样：

早晨在家喝咖啡。孩子还没醒。启动任务 1：“拉取最新的竞品更新，归纳相对上周的变化。”启动任务 2：“用 Notion 数据库起草赞助合作页面。”两个任务都在隔壁房间的桌面端跑着，我在喝咖啡。

遛狗。用手机查看任务 1，竞品总结已完成。“加一张和我们当前路线图的对比表。”一次重定向 10 秒，单手就能完成。任务 2 还在跑。狗不在乎。

妻子开车，我坐副驾。审阅赞助 Notion 页面草稿。“太正式了，把上一轮活动的互动指标拉出来，让价值主张更锋利。”启动任务 3：对文章草稿做差距分析。家里同时跑着三条并行任务，我在看路况。

孩子在蹦床馆。站在边上，手里拿着手机，45 分钟。信息图就是在这里迭代出来的。“把图标往左挪。”“把第三段的颜色改一下。”“标题加粗一点。”一份视觉资产做了四轮创意指挥——从充气城堡旁边完成。

回到桌前。一切都等着。审阅、微调、发布。所有这些空档里真正花在指挥上的时间，加起来也许 25 分钟。Claude 并行执行的工作量：3+ 小时。

48 小时结束时，我让 Claude 总结我们做出了什么。这是它给的清单：

关键机制是这样：在一个 Dispatch 对话里，你先启动任务 1（调研），立刻启动任务 2（起草），然后查看任务 1 的进度，重定向任务 2，再启动任务 3——全都在手机的同一个线程里完成。每个任务都在自己独立的沙箱会话里运行。它们互不干扰。除非你明确把它们桥接起来，否则它们不会共享上下文。

对 PM 来说：你从来不是一次只做一件事。等相关方回复的同时，你在盯竞品动作，同时还要准备冲刺产物。Dispatch 让 AI 能跟上这种节奏，而不是强迫你按顺序来。上限不在于你输出得有多快，而在于你能同时指挥多少条并行轨道。

下面是会话摘要——60+ 个任务会话由手机指挥完成，而且清楚区分了我做了什么、Claude 做了什么：

真正的洞察不是“通勤时用 Dispatch”。而是“用手机做异步指挥，会重新塑造你安排一天的方式”。有些产出我在桌前审阅并打磨。也有一些内容——X 帖子、信息图、评论回复——我从头到尾只用手机就直接发布了，根本没坐下。

https://www.productcompass.pm/p/claude-cowork-guide

4. The Dispatch Gotchas (Tested Over 48 Hours)

Every tool has friction. Here's where Dispatch's friction actually lives — tested over 48 hours, not 48 minutes. Every gotcha has a workaround or an explicit acknowledgment that none exists yet.

4.1 Folder access requires typing paths

On desktop Cowork, you click a folder icon to grant file access. On Dispatch, there’s no folder picker UI on mobile. You type the path: “Give yourself access to ~/Desktop/Workspace/Editor.”

Workaround: Describe the folder naturally — “go to workspace/editor” works. You can also define shortcuts like “editor mode” that Claude remembers across sessions. No need to memorize exact paths. This friction fades fast.

4.2 Each subtask requests folder access separately

Every subtask Dispatch delegates will request folder access on your desktop. You need to approve each one. There’s no workaround — it’s how the security model works. Just keep that in mind before putting your phone in your pocket.

4.3 File transfer isn’t built in yet

You can’t attach files from your phone to Dispatch, and Dispatch can’t send outputs directly to your phone either. Two separate problems, one solution.

https://www.productcompass.pm/p/self-improving-claude-system

For inputs (phone screenshots, photos), I started emailing them to myself and having Claude pull them from Gmail. For outputs, I noticed early that Dispatch couldn’t deliver files to my phone — so I started checking Google Drive.

Then it clicked: sync your Cowork workspace folder with Google Drive. Everything Claude saves appears on your phone automatically. Everything you drop into that folder from your phone appears on your desktop. One sync solves both directions.

4.5 CLAUDE.md delegation needs a specific order

If you just start delegating tasks, the orchestrator may formulate imprecise instructions for subtasks — it hasn’t internalized your rules yet.

The fix: ask Dispatch to read your CLAUDE.md before delegating any tasks. Once it has your rules loaded, the instructions it writes for each subtask are sharper.

4. Dispatch 的坑点（48 小时实测）

每个工具都有摩擦。Dispatch 的摩擦点到底在哪里，这里是 48 小时测出来的，不是 48 分钟。每个坑点要么有变通办法，要么会明确告诉你现在还没有。

4.1 文件夹访问需要手打路径

在桌面端 Cowork，你点一下文件夹图标就能授权文件访问。Dispatch 在手机端没有文件夹选择器 UI，需要手打路径：“Give yourself access to ~/Desktop/Workspace/Editor.”

变通办法：用自然语言描述文件夹就行，“go to workspace/editor”能用。也可以定义像“editor mode”这样的快捷方式，Claude 会跨会话记住。没必要死记硬背精确路径，这个摩擦会很快消失。

4.2 每个子任务都要单独申请文件夹访问

Dispatch 委派出去的每个子任务，都会在桌面端请求文件夹访问权限，你需要一个个批准。没有变通办法——这是安全模型的一部分。把手机塞进口袋前记得这点。

4.3 还没有内置文件传输

你没法从手机把文件附到 Dispatch 里，Dispatch 也没法把产出直接发回手机。两个问题，一个解法。

https://www.productcompass.pm/p/self-improving-claude-system

输入端（手机截图、照片），我开始给自己发邮件，让 Claude 从 Gmail 里拉。输出端，我很早就发现 Dispatch 没法把文件送到手机上，于是开始去 Google Drive 里看。

然后突然想明白了：把 Cowork 的工作区文件夹用 Google Drive 同步起来。Claude 保存的所有东西都会自动出现在手机上。你从手机扔进这个文件夹的任何东西，也会自动出现在桌面端。一次同步，把两个方向都解决了。

4.5 CLAUDE.md 的委派顺序有讲究

如果你上来就开始委派任务，编排器可能会给子任务写出不够精确的指令——它还没把你的规则吃透。

修复办法：先让 Dispatch 读你的 CLAUDE.md，before 委派任何任务。规则加载进来以后，它给每个子任务写的指令会更利落。

5. Claude Dispatch vs. Remote Control vs. Web Sessions vs. Channels: When to Use Each

Anthropic shipped 4 remote access surfaces in 5 months, the last 3 in ~23 days. Here's the quick decision framework — not the full deep dive, just what you need to pick the right surface right now.

Two corrections since the first wave of Dispatch coverage on X. Getting things wrong publicly and fixing them publicly is part of how this works:

  1. Channels are bidirectional. They push events INTO a running session AND send responses back via Telegram or Discord. My framing was imprecise.

  2. Channels support scheduled tasks — but only within active sessions. Events only arrive while the session is running.

Also, someone noticed that Dispatch allows you to run Code sessions too. I tested it and it doesn’t really work yet. The flow isn’t fully wired up (Dispatch’s words). For remote coding/prototyping, I recommend Web Sessions.

https://www.productcompass.pm/p/self-improving-claude-system

5. Claude Dispatch vs. Remote Control vs. Web Sessions vs. Channels：分别该用在哪

Anthropic 在 5 个月里上线了 4 种远程入口，最后 3 个是在大约 23 天内推出来的。下面是快速决策框架——不是完整深挖，只给你现在就能选对入口所需的东西。

自从 X 上第一波 Dispatch 讨论之后，有两点需要更正。公开说错、公开修正，是这套机制的一部分：

  1. Channels 是双向的。它们会把事件推送进正在运行的会话里，并且会通过 Telegram 或 Discord 把回应发回来。我之前的表述不够准确。

  2. Channels 支持定时任务——但只在活跃会话里有效。只有会话在运行时，事件才会进来。

另外，有人注意到 Dispatch 似乎也能跑 Code 会话。我测了下，现在还不太行。流程还没完全打通（Dispatch 的原话）。做远程写代码或原型，我推荐用 Web Sessions。

https://www.productcompass.pm/p/self-improving-claude-system

6. The Knowledge Layer That Makes Every Claude Surface Compound

Anthropic shipped three new remote surfaces in ~23 days — Dispatch, Channels, and Remote Control — on top of Web Sessions from October. That's four ways to run Claude without sitting at your desk. If your AI setup lives inside a single surface, every new one means starting over.

Also, they are shipping updates like crazy. Only yesterday (Sunday): two changes to Claude Code — a 7-day /loop and an improved /init command.

The fix: store your knowledge in a GitHub repo. CLAUDE.md (your instructions file — voice, rules, workflows) plus knowledge files (templates, hypotheses, research). Every surface reads it from your machine. Web Sessions clone it.

The surfaces change. Your knowledge layer compounds.

Picture this: Two PMs. Same company. Same AI tools. Same access. One builds a knowledge system around them — CLAUDE.md, skill libraries, structured workflows that improve with every use. The other uses them when stuck. Within months, one is shipping at 5x the pace.

The full architecture — CLAUDE.md structure, knowledge file organization, the self-correction loop — is in the Self-Improving System post.

6. 让每个 Claude 入口都能复利的知识层

Anthropic 在大约 23 天里上线了三个新的远程入口——Dispatch、Channels、Remote Control——再加上从 10 月就有的 Web Sessions。也就是说，你不用坐在桌前就能跑 Claude 的方式一共有四种。如果你的 AI 配置只活在某一个入口里，那每来一个新入口，你都要从头再搭一遍。

而且他们更新得很疯狂。就昨天（周日）：Claude Code 改了两处——一个 7 天的 /loop，以及一个改进后的 /init 命令。

修复办法：把你的知识存进一个 GitHub 仓库。CLAUDE.md（你的指令文件——语气、规则、工作流）加上知识文件（模板、假设、研究）。每个入口都从你的机器上读取它。Web Sessions 会把它 clone 下来。

入口会变，你的知识层会复利。

想象一下：两位产品经理。同一家公司。同一套 AI 工具。同样的权限。一位围绕它们搭了一个知识系统——CLAUDE.md、技能库、越用越顺的结构化工作流。另一位只在卡住时才用。几个月后，一个人的交付节奏能快出 5x。

完整架构——CLAUDE.md 的结构、知识文件怎么组织、自我纠错循环——都写在 Self-Improving System 那篇文章里。

7. The Highest-Leverage Investment for PMs Using AI

Here's the actual split from those 48 hours — who contributed what:

Look at the pattern. Thinking: 90% me. Takes and opinions: 100% me (Claude may have exaggerated). Research and formatting: 90% Claude. The AI handled speed and breadth. I handled judgment and direction.

This is the part most people skip. Use AI to amplify your thinking, not to replace it.

In writing, if you have nothing to say before you open Claude, you get polished slop.

For PMs, the implication is the same. Building a knowledge system is an investment. CLAUDE.md files, skill libraries, workflow patterns — they take time. But they learn from you. Every correction you make, every rule you add, every draft you kill compounds into a system that gets sharper with use.

Right now — this year, next year — the single highest-leverage investment isn't learning a new AI tool. It's building the judgment, the systems, and the domain knowledge that make you a better orchestrator of whatever tool comes next.

Every infographic in this post was created, iterated, and exported via Dispatch — from my phone.

Tests, opinions, what matters, and direction are mine.

Start building. Stop theorizing.

P.S. If you want the full system — CLAUDE.md instructions, knowledge architecture, the self-correcting loop — that’s in The Self-Improving Claude System. This post gives you Dispatch. That post gives you the system that makes Dispatch actually compound.

7. 产品经理用 AI 时，杠杆最高的一笔投入

下面是那 48 小时里最真实的分工——谁贡献了什么：

看这个模式。思考：90% 是我。观点和立场：100% 是我（Claude 可能夸张了）。调研和排版：90% 是 Claude。AI 负责速度和广度，我负责判断和指挥。

这一步大多数人都会跳过。用 AI 放大你的思考，而不是替代它。

写作时，如果你在打开 Claude 之前自己没想说什么，最后只会得到抛光过的糊弄。

对 PM 来说，道理一样。搭建一个知识系统是一笔投入。CLAUDE.md 文件、技能库、工作流模式——都要花时间。但它们会向你学习。你做的每一次纠正、加的每一条规则、杀掉的每一个草稿，都会复利成一个越用越锋利的系统。

现在——今年、明年——杠杆最高的一笔投入不是去学一个新的 AI 工具，而是去建立判断力、系统化的方法、以及领域知识，让你能更好地编排下一代工具。

这篇文章里的每一张信息图，都是通过 Dispatch——从我的手机——创建、迭代、导出完成的。

测试、观点、什么重要、以及方向，都由我负责。

开始搭建。别再空想。

P.S. 如果你想要完整系统——CLAUDE.md 指令、知识架构、自我纠错循环——都在 The Self-Improving Claude System 里。这篇文章给你 Dispatch。那篇文章给你让 Dispatch 真正复利的系统。

Claude now has 4 ways to run from your phone. Most people will try one, hit friction, and give up. Here's what actually works — and how it changed how I structure my day.

Dispatch is the newest surface — and the one most likely to change how you work as a PM. Not because it’s the most powerful, but because it turns every gap in your day into a window for directing real work. Dog walks, coffee, the passenger seat, standing at the sidelines of a bounce house — all become productive without being “always on.”

I tested this for 48 hours straight, building real PM workflows from my phone. What you’re reading is everything I found — the workflows that actually work, the friction points nobody warns you about, and the architectural insight that matters more than any single feature Anthropic ships.

What You’ll Learn

  • What Dispatch actually is — and the difference from “Claude chat on your phone”

  • How to set up and start your first Dispatch session

  • The real 48-hour timeline — how async direction reshapes your day

  • Every gotcha I hit, with tested workarounds

  • When to use Dispatch vs. Web Sessions vs. Channels vs. Code

  • Why the knowledge layer matters more than any single surface

  • The single highest-leverage investment for PMs building with AI

1. What Dispatch Is (And Isn’t)

Dispatch isn’t “Claude chat on your phone.” You already have that.

Dispatch is an orchestrator. From a single conversation on your phone, you spawn and manage multiple Cowork task sessions running simultaneously on your desktop. Each session runs independently — its own context, its own file access, its own connectors.

Your phone is the command chair. Your desktop does the heavy lifting.

Think of the difference between texting someone a request and sitting in a control room with multiple screens. Each screen is a task session running on your desktop. Your phone directs all of them from one conversation thread.

https://x.com/PawelHuryn/status/2035871263386698016?s=20

For PMs: This maps to something you already do — running multiple workstreams simultaneously. One analyst pulling competitor data. Another drafting the stakeholder email. A third organizing research notes. Dispatch is that, except the analysts are AI sessions on your desktop and the command chair is in your pocket.

Every Cowork connector you've configured — Gmail, Notion, Slack, all of them — works through Dispatch because Dispatch delegates to Cowork.

2. How to Set Up Claude Dispatch

Step 1: Set up Cowork on your desktop with the connectors you use — Gmail, Notion, Slack, whatever your stack is. Everything must be configured on desktop first. Then, keep your desktop awake and Claude app running.

Step 2: Open the Claude mobile app. You’ll see the Dispatch tab. Start a conversation and tell it to run a Cowork task.

Step 3: Start small. One task (e.g., “summarize unanswered emails from the last week”). See the output. Then try running two tasks from the same conversation to feel the parallel workflow.

Step 4: To work with files, grant folder access — describe the folder naturally (”go to workspace/editor”) or use a shortcut you’ve defined. Start with the folder that has your CLAUDE.md and knowledge files.

Step 5: Set up your workarounds early:

  • If your workspace syncs via Google Drive/Dropbox/iCloud, check that files appear on your phone — this eliminates the file transfer problem entirely

  • Define folder shortcuts (”editor mode,” “workspace”) so you describe folders naturally instead of typing paths

3. Real PM Workflows With Claude Dispatch (48-Hour Test)

Dispatch didn't fill my dead time. It changed how I structured my day. I went to the jump arena with my kid because I could direct work async from the sidelines. The model isn't "grind during gaps." It's "design your day differently because the work runs without you sitting in front of it."

Here's what that looked like:

Morning coffee at home. Kids aren’t up yet. Start Task 1: “Pull the latest competitor updates, summarize changes since last week.” Start Task 2: “Draft the sponsor collaboration page using the Notion database.” Both tasks running on my desktop in the other room. I’m drinking coffee.

Walking the dog. Check Task 1 on my phone — competitor summary done. “Add a comparison table against our current roadmap.” Redirect takes 10 seconds, one-handed. Task 2 is still running. Dog doesn’t care.

Wife driving, I’m in the passenger seat. Review the sponsor Notion page draft. “Too formal. Pull the engagement metrics from the last campaign and make the value prop sharper.” Start Task 3: gap analysis on the article draft. Three parallel tasks running at home. I’m watching traffic.

Kid at the jump arena. Standing on the side, phone in hand, 45 minutes. This is where the infographic iterations happened. "Move the icons left." "Change the color on the third section." "Make the header bolder." Four rounds of creative direction on a visual asset — from the sidelines of a bounce house.

Back at my desk. Everything waiting. Review, adjust, ship. The actual direction time across all of these gaps: maybe 25 minutes total. The Claude execution running in parallel: 3+ hours of work.

At the end of the 48 hours, I asked Claude to summarize what we'd built. Here's its list:

The key mechanic: in a single Dispatch conversation, you start Task 1 (research), then immediately start Task 2 (drafting), then check progress on Task 1, redirect Task 2, start Task 3 — all from one thread on your phone. Each task runs in its own sandboxed session. They don't interfere with each other. They don't share context unless you explicitly bridge them.

For PMs: You don't do one thing at a time. You're tracking competitive moves while waiting for a stakeholder response while preparing sprint artifacts. Dispatch lets AI match that rhythm instead of forcing sequential mode. The ceiling isn't your output speed — it's how many parallel tracks you can direct at once.

And here's the session summary — 60+ task sessions directed from my phone, with a clear split between what I did and what Claude did:

The insight isn't "use Dispatch during your commute." It's that async direction from your phone reshapes how you structure your day. Some outputs I reviewed and refined at my desk. Others — X posts, infographics, comment replies — shipped entirely from my phone without ever sitting down.

https://www.productcompass.pm/p/claude-cowork-guide

4. The Dispatch Gotchas (Tested Over 48 Hours)

Every tool has friction. Here's where Dispatch's friction actually lives — tested over 48 hours, not 48 minutes. Every gotcha has a workaround or an explicit acknowledgment that none exists yet.

4.1 Folder access requires typing paths

On desktop Cowork, you click a folder icon to grant file access. On Dispatch, there’s no folder picker UI on mobile. You type the path: “Give yourself access to ~/Desktop/Workspace/Editor.”

Workaround: Describe the folder naturally — “go to workspace/editor” works. You can also define shortcuts like “editor mode” that Claude remembers across sessions. No need to memorize exact paths. This friction fades fast.

4.2 Each subtask requests folder access separately

Every subtask Dispatch delegates will request folder access on your desktop. You need to approve each one. There’s no workaround — it’s how the security model works. Just keep that in mind before putting your phone in your pocket.

4.3 File transfer isn’t built in yet

You can’t attach files from your phone to Dispatch, and Dispatch can’t send outputs directly to your phone either. Two separate problems, one solution.

https://www.productcompass.pm/p/self-improving-claude-system

For inputs (phone screenshots, photos), I started emailing them to myself and having Claude pull them from Gmail. For outputs, I noticed early that Dispatch couldn’t deliver files to my phone — so I started checking Google Drive.

Then it clicked: sync your Cowork workspace folder with Google Drive. Everything Claude saves appears on your phone automatically. Everything you drop into that folder from your phone appears on your desktop. One sync solves both directions.

4.5 CLAUDE.md delegation needs a specific order

If you just start delegating tasks, the orchestrator may formulate imprecise instructions for subtasks — it hasn’t internalized your rules yet.

The fix: ask Dispatch to read your CLAUDE.md before delegating any tasks. Once it has your rules loaded, the instructions it writes for each subtask are sharper.

5. Claude Dispatch vs. Remote Control vs. Web Sessions vs. Channels: When to Use Each

Anthropic shipped 4 remote access surfaces in 5 months, the last 3 in ~23 days. Here's the quick decision framework — not the full deep dive, just what you need to pick the right surface right now.

Two corrections since the first wave of Dispatch coverage on X. Getting things wrong publicly and fixing them publicly is part of how this works:

  1. Channels are bidirectional. They push events INTO a running session AND send responses back via Telegram or Discord. My framing was imprecise.

  2. Channels support scheduled tasks — but only within active sessions. Events only arrive while the session is running.

Also, someone noticed that Dispatch allows you to run Code sessions too. I tested it and it doesn’t really work yet. The flow isn’t fully wired up (Dispatch’s words). For remote coding/prototyping, I recommend Web Sessions.

https://www.productcompass.pm/p/self-improving-claude-system

6. The Knowledge Layer That Makes Every Claude Surface Compound

Anthropic shipped three new remote surfaces in ~23 days — Dispatch, Channels, and Remote Control — on top of Web Sessions from October. That's four ways to run Claude without sitting at your desk. If your AI setup lives inside a single surface, every new one means starting over.

Also, they are shipping updates like crazy. Only yesterday (Sunday): two changes to Claude Code — a 7-day /loop and an improved /init command.

The fix: store your knowledge in a GitHub repo. CLAUDE.md (your instructions file — voice, rules, workflows) plus knowledge files (templates, hypotheses, research). Every surface reads it from your machine. Web Sessions clone it.

The surfaces change. Your knowledge layer compounds.

Picture this: Two PMs. Same company. Same AI tools. Same access. One builds a knowledge system around them — CLAUDE.md, skill libraries, structured workflows that improve with every use. The other uses them when stuck. Within months, one is shipping at 5x the pace.

The full architecture — CLAUDE.md structure, knowledge file organization, the self-correction loop — is in the Self-Improving System post.

7. The Highest-Leverage Investment for PMs Using AI

Here's the actual split from those 48 hours — who contributed what:

Look at the pattern. Thinking: 90% me. Takes and opinions: 100% me (Claude may have exaggerated). Research and formatting: 90% Claude. The AI handled speed and breadth. I handled judgment and direction.

This is the part most people skip. Use AI to amplify your thinking, not to replace it.

In writing, if you have nothing to say before you open Claude, you get polished slop.

For PMs, the implication is the same. Building a knowledge system is an investment. CLAUDE.md files, skill libraries, workflow patterns — they take time. But they learn from you. Every correction you make, every rule you add, every draft you kill compounds into a system that gets sharper with use.

Right now — this year, next year — the single highest-leverage investment isn't learning a new AI tool. It's building the judgment, the systems, and the domain knowledge that make you a better orchestrator of whatever tool comes next.

Every infographic in this post was created, iterated, and exported via Dispatch — from my phone.

Tests, opinions, what matters, and direction are mine.

Start building. Stop theorizing.

P.S. If you want the full system — CLAUDE.md instructions, knowledge architecture, the self-correcting loop — that’s in The Self-Improving Claude System. This post gives you Dispatch. That post gives you the system that makes Dispatch actually compound.

📋 讨论归档

讨论进行中…