Two weeks ago I started daily-driving a personal assistant I've been building on Claude Cowork. The whole system runs on Claude Cowork, with Google Workspace (email, calendar, Drive, Chat) and Notion (tasks, projects, GTD) as the surrounding data layer. I upgraded to Claude Max 20x ($200/month) once the architecture outgrew the lower tier — the system now runs 15 scheduled background tasks around the clock, plus the interactive sessions I have through the day. The agent is active 6–7 hours every day. Roughly 2–3 of those hours are development — debugging, iterating on skills, refactoring prompts, reviewing audit outputs. The other 4–5 hours are real work: inbox triage, draft reviews, research delegations, decision support, report generation, meeting prep. What it is now: - A persistent, file-based memory system with ~200 curated markdown entries, indexed by semantic topic — not a vector DB - 11 specialized sub-agents (legal, finance, research, sales, operations, real estate, etc.) with a delegation matrix - A development constitution: a versioned governance doc for how the system evolves — which structural changes it can make autonomously vs. which require my approval - A distributed architecture: always-on background sentinel (inbox scans, health checks, nightly closeouts, conflict scanning) + interactive node - A self-improvement loop that audits instruction files, researches new techniques, proposes a change plan, waits for approval, implements The agent lives inside a Dropbox folder — not as a UI feature, as its actual substrate. Everything is organized first by project, then by artifact type. When a new project starts, the agent spins up the folder skeleton. When a project closes, it moves to cold storage. On one side, multiple inboxes: my work email + a dedicated shadow email for the agent itself, Google Chat, a Notion GTD inbox, a file dropzone, a daily working folder, a general triage inbox, and — the one I haven't seen anyone talk about — my Downloads folder on every computer I use is redirected straight into the agent's inbox folder.
A 2-Week-Old Executive Chief-of-Staff on Claude Cowork: 15 Scheduled Tasks, 11 Sub-Agents, a File-Based Memory
A mid-sized-company exec runs Claude Cowork as his chief of staff: 15 scheduled background tasks around the clock, 11 function-specific sub-agents (legal, finance, research, sales, ops, real estate, etc.) dispatched through a delegation matrix, ~200 curated markdown memories living inside a Dropbox project tree (not a vector DB), and a versioned "development constitution" defining which structural changes the system may make autonomously vs. which need human approval. His Downloads folder on every machine is redirected into the agent's inbox. The system is live 6–7 hrs a day, with 4–5 of those on real work. Built in 2 weeks on Claude Max 20x
Executive at a mid-sized company; daily-drives a personal chief-of-staff built on Claude Cowork
Scenario
The author is an executive at a mid-sized company. Every commercial AI assistant he tried was amnesiac — each session started from zero context. He wanted something closer to an actual chief of staff: persistent, opinionated, aware of what he's working on. So over two weeks he built a system on Claude Cowork: Google Workspace + Notion as the data layer, Dropbox as the file substrate, 15 scheduled tasks running around the clock, 11 specialized sub-agents handling domains like legal and finance, and a self-improvement loop that evolves the system itself.
Prompt
Act as my chief of staff in Claude Cowork. Load the development constitution at /agent/constitution.md and the active project index at /projects/_index.md. Every morning, scan all inboxes (work email, shadow email, Google Chat, Notion GTD inbox, shared file dropzone, Downloads folder) and produce a triage brief: urgent decisions needed, drafts awaiting my review, new items routed to each sub-agent (legal, finance, research, sales, operations, real estate). For each active project, report status, blockers, and the next human-in-loop step. End with conflict scans across calendar and commitments. Delegate execution to the sub-agent whose domain matches; escalate only decisions the constitution marks as requiring my approval.
Expected Result
The author has a steady "human exec + AI staff" system running on Cowork: - **15 scheduled background tasks** covering inbox scans, health checks, nightly closeouts, and calendar-conflict sweeps - **11 specialized sub-agents** (legal, finance, research, sales, operations, real estate…) dispatched through a delegation matrix - **~200 curated markdown memories**, indexed by semantic topic — no vector DB - **Dropbox as the substrate**, not a UI feature — one folder per project, cold-archived on close, skeletons auto-generated on project start - **Downloads redirected**: every machine's Downloads folder is aliased to the agent's inbox - **Development constitution**: a versioned doc defining which structural changes the system can make autonomously vs. which need his sign-off - **Self-improvement loop**: audits its own instruction files, researches new techniques, proposes a change plan, waits for approval, then implements **Outcome:** the system is live 6–7 hours every day. Roughly 2–3 hrs still go to development, but 4–5 hrs are real work — inbox triage, draft review, research delegations, decision support, report generation, meeting prep. He expects the dev/work ratio to tip further toward work over time, and judges the 30–40% overhead worth it while the system matures. Built in 2 weeks on a Claude Max 20x ($200/mo) subscription.