The Task List Should Read the Work Before It Plans the Day
maps to joelclaw's Vault, email, Granola, gateway, and task loops as a concrete peer pattern for ambient planning
A public Tella video from the creator account me@brennandunn.com, likely Brennan Dunn, walks through a personal knowledge base built around Claude Code, slash commands, a JSON Lines task store called BEADS, and human-readable Markdown files. The Tella source title says “Cloud Code,” but the transcript talks about running Claude Code headlessly with -p.
The clever part isn’t another Obsidian clone. It’s a task system that watches Help Scout tickets, personal email, calls, GitHub, Discord, Linear, newsletters, podcasts, and YouTube transcripts, then turns that mess into a daily plan, daily review, status check, call prep, coaching log, and content idea inventory.
A todo list that has already read the room is a different animal.
This lands close to joelclaw because the shape is familiar: ambient capture, structured memory, operator brief, action loop. The stack is less important than the contract: daily plan in, daily review out, every input tied back to source evidence. That’s the useful bit to steal without copying the whole damn pile.
Key Ideas
- Ferndesk is the inspiration: a support-docs system that reads Help Scout, Discord, GitHub, and Linear so support knowledge can be written from actual support/code context.
- The personal system joins a
BEADSJSON Lines task database with Markdown notes, giving agents both structured task state and readable context. - Slash commands like daily plan, daily review, status, call prep, and content planning make the folder feel like an operating interface instead of a passive archive.
- Calls are transcribed and analyzed with Otter.ai style summaries, then rolled into a coaching log so sales/demo improvement becomes a tracked loop.
- Ingestion uses n8n, AssemblyAI, YouTube transcripts, and headless Claude Code, keeping the workflow automation dumb while the agent does the reading and filing.
- For joelclaw, the transferable pattern is ambient capture → daily operator brief → review log → content idea inventory, not the specific app stack.