TL;DR — I've created agents. The orchestration has been challenging, but a whole lot of fun now that it is working. I'm building a SaaS/PaaS platform as a solo dev, so dev eats all my time and marketing / outreach always gets dropped. The challenge was keeping me, Claude Cowork, Claude Chat, Claude Code, and my agents on the same context. 1. I created a context.md file that lives on a Google Drive mirror on my local machine. Both during and at the end of each Cowork session, Cowork updates it — strategy, new DB table names, edge functions, anything needed to talk about the whole platform. 2. Claude Chat can't natively read md files in Drive, so I deployed the context file to the cloud with a token for authorized access, so Chat can fetch it when I start a new conversation on my phone. 3. I built two skills: an outreach agent (direct email to users) and a content agent (social media copy, blog posts, video scripts). At the end of each Cowork session, Cowork updates the context doc and Code pushes it to the cloud. When I start the next Cowork session, it's like getting a briefing from a Chief of Staff — recap, leftovers, backlog, and proposed work orders for the agents. 4. I review the proposed work orders and tell Cowork to create them. Work orders are written into the context.md file, which the agent skills can read. 5. I activate the skills; each agent reads the context doc, finds its work orders, produces output in assigned folders, updates status to complete, and notifies me in the same Cowork session for review. If approved, the agents schedule the content.
单人 SaaS 创始人：用 Cowork 协调 Chat / Code / Agents 的共享上下文架构
solo 开发者把 Cowork 当作 Chief of Staff：用 Google Drive 上的 context.md 作为单一真相源，让 Cowork、Chat、Code 和两个 skills（outreach / content agent）通过工单（work order）机制协同执行营销与推广任务
Solo founder building a SaaS/PaaS platform with Claude Cowork as control plane
使用场景
solo 开发者同时使用 Claude Cowork、Claude Chat（手机）、Claude Code（代码仓库）和多个 agent skills，痛点：每个上下文是孤岛，自己作为人类 + Claude 各形态 + agents 很难保持同步，导致营销与推广等「nice to have」任务永远拖延。
提示词
At the end of each working session, update context.md at /path/to/GoogleDriveMirror/ with: strategy changes, new database table names / edge functions, UX decisions, and any info needed to discuss the entire platform. When I start the next Cowork session, read context.md and brief me like a Chief of Staff would: last session recap, leftover items, backlog, and proposed work orders for my outreach and content agent skills. I'll review and tell you which work orders to commit; append approved ones to context.md so the agents can pick them up when I activate them.
预期结果
搭建一套 Chief-of-Staff 风格的编排体系： 1. **context.md**（Google Drive 本地镜像）= 单一真相源 2. **Cowork**：每次会话结尾自动更新 context.md；下次开启时提供「上次总结 + 剩余 + backlog + 建议工单」 3. **Claude Code**：把 context.md 推送到带 token 的云端，方便 Chat 读取 4. **Claude Chat（手机）**：通过 token 授权读取同一文件 5. **两个 skills**（outreach / content agent）：读 context.md → 找自己的工单 → 输出到指定目录 → 把工单状态置为 complete → 在当前 Cowork 会话中通知用户 **效果：** 每次打开 Cowork 就像获得参谋长简报，营销/推广不再被拖延，所有 agent 共享同一上下文。