I built my own interface for Claude. It only reads my folder.
AI finished the work. The decision I made with it is gone. ð The folder that I used to build this is free inside myICOR: https://www.myicor.com/?utm_source=yo... WATCH THIS NEXT The full tour of the folder this runs on. One folder of plain text, and Claude runs my whole life and business from inside it:    âĒ Everything I am fits in plain text. Here i...  ABOUT THIS VIDEO Three weeks ago you decided something with AI. Good work happened. Now try to say what the decision actually was. You cannot, and neither can anyone else. That is what this video is about. I have had a deliverables folder for months. Everything AI makes lands there. Images, reports, diagrams, scripts. That solved where the work goes and nothing else. I still had to read what AI was asking me inside a chat, find the matching folder, then explain myself again to get anything changed. Cowork organises progress and outputs on the side. Claude Code has an artifacts panel and a background task view. Both go the right direction. My objection is not that they cannot do it. It is that they live inside an app I do not control. So I kept building on the folder instead. Many versions, over months, none of them finished. This is where it stands today, and it is work in progress. Tell me in the comments what you would change. At 4:42 there is one piece you can take today: the decision warning system prompt from the AI Enhancement Hub inside myICOR. Copy it, paste it, and AI sets it up in your own folder. That is the visual decision indicator you watch me use in the terminal for the rest of the video. CHAPTERS 0:00 A year of thinking about one problem 0:30 Where everything AI makes already lands 0:52 Why the folder on its own gets messy 1:06 Cowork's progress panel, and where it stops 1:32 Claude Code's artifacts, and the app I do not control 1:54 Point any model at the folder and it still works 2:13 Following up on decisions away from the computer 2:52 For builders: the terminal, and why it is not scary 3:06 Who are you, and Larry answers 3:21 For builders: VS Code as a non-coder 3:56 For builders: the harness, and why I keep it raw 4:17 Emoji summaries and decision codes, not a wall of text 4:42 The decision warning system prompt, free to copy 5:12 Losing track of decisions once agents run in parallel 5:35 Several sessions open for days at a time 5:57 My real folder, and the archive back to February 6:24 Readable folders, and still not knowing where to look 6:55 Asking AI for an HTML page and opening it in Chrome 7:18 Nice to read, impossible to act on 7:41 Months of iterations, not one finished build 8:15 What I built, and why it is still work in progress 8:56 The list, and what is waiting on me 9:17 Opening one piece of work: a script I had to review 9:38 The audit trail: what changed, and who changed it 10:26 Calling Larry by voice when the ask is unclear 10:57 The recording of that call lands on the work 11:38 Agree, disagree, defer, or walk every open decision 12:31 A second piece of work, and reviewing what AI made 13:26 Who worked on this, and what they changed 13:46 Where this actually runs, and why Cowork works too 14:12 The media panel and the live timeline 14:39 Comparing what AI made against what the code made 15:07 Circling what is wrong instead of describing it 15:36 How AI picks the drawing up next session 16:04 The animated video it produced 16:21 Pointing at the exact frame that is wrong 16:57 Handing something new to the team from here 17:40 Selecting any paragraph and arguing with it 18:13 The supporting files that came with the work 18:56 Editing what AI wrote, and the edit stays tracked 19:39 For builders: how this works behind the scenes 20:37 For builders: canvas.json and the per-folder brief 21:07 For builders: the decisions, in plain markdown 21:19 For builders: where the tool itself lives 22:04 Why it looks polished: a year of training them 22:35 Independence, and the one thing to back up 22:53 The free scaffold, and the video to watch next WHAT I AM USING Claude and one local folder of markdown files. No database, no web application, no login. You can download your own myPKA folder for free here: https://www.myicor.com/?utm_source=yo... And the original build, from an empty folder to a working system in one sitting:    âĒ Claude just killed the note-taking app. He...  ABOUT Tom helps professionals build AI productivity systems that work, using the ICOR Methodology, courses, coaching, and the myICOR community. LinkedIn:   / tomsolid  X: https://x.com/TomSolidPM Podcast:    / @productivitylikeapro  All third-party marks and logos shown are the property of their respective owners and are used for identification in editorial commentary only. No partnership or sponsorship is implied. #ClaudeCode #ClaudeAI #AIProductivity #myPKA #ICOR
