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.
Solo SaaS Founder's Orchestration Stack: Shared Context Across Cowork, Chat, Code, and Agents
A solo dev uses Cowork as a Chief-of-Staff layer: a single context.md on Google Drive acts as source of truth, and Cowork hands off work orders to agent skills (outreach + content) while Chat (mobile) and Code (repo) read the same file
Solo founder building a SaaS/PaaS platform with Claude Cowork as control plane
Scenario
A solo dev uses Claude Cowork, Claude Chat (mobile), Claude Code (repo), and multiple agent skills in parallel. Pain: each surface has its own context silo, and keeping the human + all Claude surfaces + agents in sync is nearly impossible — so marketing and outreach work keeps getting dropped.
Prompt
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.
Expected Result
Built a Chief-of-Staff–style orchestration stack: 1. **context.md** (local Google Drive mirror) = single source of truth 2. **Cowork** — updates context.md during and at the end of each session; at the start of the next session it briefs the user like a Chief of Staff (recap, leftovers, backlog, proposed work orders) 3. **Claude Code** — pushes context.md to a token-gated cloud endpoint so Chat can fetch it 4. **Claude Chat (mobile)** — reads the same file via authorized token 5. **Two skills** (outreach + content agent) — read context.md, locate their work orders, drop output in assigned folders, mark work-order status complete, and notify the user in the same Cowork session **Outcome:** every new Cowork session opens with a Chief-of-Staff briefing; marketing/outreach no longer gets dropped; every agent shares the same source of truth.