Claude finished the work. Then I lost it in the chat.
A creator demonstrates a comprehensive local-folder-based system for managing AI-generated deliverables asynchronously, featuring an interactive browser interface that tracks decisions, changes, and conversations without relying on external databases or web applications. The system enables collaborative editing, visual annotations, and automatic context preservation across multiple parallel AI projects.
Summary
The speaker presents a year-long iterative development of a workflow system designed to solve the core problem of losing control and context when working with AI across multiple projects. Rather than remaining tethered to continuous chat sessions, the system uses a local folder structure as a 'single source of truth' where all AI outputs, decisions, and conversations are stored and tracked.
The fundamental architecture leverages a folder-based approach with specific subfolders: a deliverables folder containing AI-generated work (images, reports, diagrams), a team inbox for new tasks, and structured markdown files documenting decisions and context. This structure works with any AI model (Claude, Gemini, etc.) because it relies on local files rather than proprietary platforms.
The interface built on top of this system provides a visual, browser-based dashboard that displays all deliverables with thumbnail previews, decision markers, and status indicators. Users can hover over items to see additional information, including how many open decisions require attention. The key innovation is enabling asynchronous work: users can review outputs, make decisions, add annotations (including drawings on images and timestamp-specific comments on videos), and create follow-up notes without maintaining active chat sessions.
The system tracks comprehensive audit trails showing which agents/sessions worked on each deliverable, what changes were made, and when. It automatically updates in real-time as new work is completed. Users can enter 'focus mode' on individual deliverables to handle one project at a time with full context, and can call the AI orchestrator (named 'Larry') for clarification without disrupting the workflow. The speaker emphasizes this represents true asynchronous collaboration: AI can pick up work from recorded context (including audio from calls) without losing progress if sessions terminate.
Behind the scenes, the system is remarkably simple—just an app created through conversation with AI that reads from local JSON files and markdown documents in the folder structure, serving the data to a frontend interface. The speaker built this entire system by talking to AI while iterating on design decisions, with styling and branding guidelines developed over months of parallel work. The solution maintains complete user independence from external services, requiring only folder backups to prevent data loss.
Key Insights
- The speaker describes sitting in chat sessions waiting for AI to respond and then manually finding relevant outputs as a significant productivity drain, which motivated designing a system that eliminates the need to keep sessions active.
- The system uses a 'decision warning' visual prompt system with emojis and brief code snippets instead of scrolling through long-form text, allowing users to quickly identify what decisions are blocking AI progress without information overload.
- The speaker demonstrates that by keeping multiple terminal sessions open for days working on complex parallel projects, tracked through a single deliverables folder, they achieve better organization than traditional chat-based approaches which lose context across sessions.
- The system enables direct inline annotation on generated content (including drawing on images and timestamped comments on videos) which then automatically translate into actionable follow-up instructions for AI in subsequent sessions without manual explanation.
- The speaker argues that reaching the level of polish and autonomous improvement shown in their system is impossible with standard chatbot interfaces because the AI learns and refines its own processes based on accumulated work patterns, not from explicit instructions alone.
Topics
Transcript
[0:00] I showed you on this channel already so many things you can do with AI that is actually useful, and how we organize everything using just a local folder and Claude. And today, I will show you something I've been thinking about for, well, a whole year to how to best work with AI, so whatever it creates for me, I don't have to sit in a session to keep control of it, keep tracking what it's doing, and then follow up the chat, and then go through the chat and find the things, and all this is confusing. [0:30] And in order to compensate that and make it clearer if I work on different things in parallel, inside…
Full transcript available for MurmurCast members
Sign Up to AccessMore from ICOR with Tom | AI Productivity
Claude writes better weekly reports than I did. Here is proof.
The speaker demonstrates how AI-powered weekly reports can automatically synthesize journal entries, notes, and captured content into personalized insights without manual review. Two different implementations are shown—one dashboard-style and one essay-style—proving the same underlying system can be customized to individual preferences and consumption habits.
I stopped doing my weekly review. The AI does it now.
The speaker has replaced traditional weekly reviews and manual note-linking with an AI-powered system built on a local folder structure called a 'scaffold.' This approach eliminates the time-consuming review ritual while enabling the AI to automatically connect notes and surface meaningful patterns that humans would miss.
I Made Opus and Fable Grade Each Other. Opus Admitted It Lost.
The creator demonstrates real-world AI applications in their productivity business using Claude Fable and Opus, showing how Fable excels at comprehensive analysis of complex systems while comparing its performance to Opus on specific tasks. The key finding is that Fable's holistic understanding justifies its higher cost for business-critical audits and optimizations.
Our AI invented the numbers. We caught it.
The hosts discuss the importance of double-checking AI outputs and validating information, emphasizing that this is not a new problem but rather a longstanding practice required with any information source. They explore how AI tools can be customized to individual workflows and contexts, arguing that understanding foundational methodology matters more than specific tools.
An AI Just Handed Me a Fake $67B Statistic
The speaker shares how an AI confidently generated a completely fabricated $67.4 billion statistic while researching AI hallucinations, then explains his systematic approach to combating AI misinformation: using dual independent search engines to cross-check answers and identify where hallucinations occur.