They Restricted Fable. I Switched Models in One Folder.
The creator explains why the removal of Claude Fable didn't disrupt his workflow, arguing that model-agnostic local folder setups with structured instructions make users resilient to AI changes. He uses an analogy of a dark room with a chair to explain how context and instructions guide AI behavior. The core message is that building robust local documentation and agent orchestration systems matters more than chasing the latest AI model.
Summary
The video opens with the creator addressing the ban of Claude Fable, expressing that he was largely unaffected because his workflow is not dependent on any specific model. He frames this resilience as a mindset and structural approach that others can adopt.
To explain how AI context works, he uses a 'dark room' metaphor: a person in a completely dark, silent room has no external input. When a light illuminates a chair, the brain instantly generates possibilities — sit on it, throw it, burn it. The chair represents context given to an AI model, and a note on the chair with instructions represents the system prompts or guidelines stored in a local folder. This analogy is used to show that any AI model — Claude, GPT, Gemini — will behave similarly when given the same contextual folder and instructions, which is why the creator can switch models without friction.
He then extends the analogy to professional use cases, noting that generic prompts yield generic outputs, while pre-loaded assets (company name, product images, brand guidelines) stored locally produce highly customized results. This local folder approach eliminates the 'starting from scratch' feeling with every new chat session.
The creator describes his multi-agent orchestration setup: an orchestrator agent acts as a single point of contact, reviews a 'team roster' of specialized agents, and delegates tasks accordingly. A quality assurance agent double-checks outputs. He notes that Anthropic is now building similar self-checking behavior natively into Claude, but he has been using this architecture for over a year already.
He draws a parallel between AI management and managing human teams in corporate environments, referencing standard operating procedures and work instructions. He describes 'firing' or 'retraining' AI agents by having them research improvements based on feedback and update their own documentation in the local folder.
On model selection, he explains that not every agent needs the most powerful (and expensive) model. A web researcher agent can run on Haiku, the orchestrator on Sonnet, and complex tasks like front-end development or database work on Opus. He criticizes the common tendency to run everything on the most expensive model out of fear of missing out.
Finally, he mentions local models as a growing area of interest, suggesting that when local models approach the capability of Opus 4.8, investing in dedicated hardware to run AI completely independently of external APIs may become worthwhile. He closes by encouraging viewers to stop chasing the next big AI release and instead focus on getting consistent value from what already works.
Key Insights
- The creator argues that storing context and instructions in a local folder makes any AI model — Claude, GPT, or Gemini — behave similarly, because they all 'read the same letter,' which is why he can switch models without disrupting his workflow.
- The creator describes a multi-agent system he has used for over a year: an orchestrator agent selects the right specialist from a 'team roster,' delegates the task, and a quality assurance agent double-checks the output — something he notes Anthropic is only now building natively into Claude.
- He claims that AI agents can 'retrain themselves' by researching how to improve based on user feedback and then updating their own documentation in the local folder, which he explicitly compares to sending a human employee to a training camp.
- The creator argues that most people run all AI tasks on the most expensive model out of fear of missing out, but once you clearly understand the expected output of a task, you can accurately determine which model tier is actually needed, significantly reducing costs.
- He suggests that local AI models running entirely on personal hardware are an emerging path to complete independence from external companies and APIs, and that when local model quality approaches Opus 4.8 levels, investing in dedicated hardware may become genuinely worthwhile.
Topics
Transcript
[0:00] So Claude Fable got banned and everybody is worried about the things. Well, I'm not happy, but I was much more worried about to pay API costs for Fable. I'm absolutely calm when it comes to this Because I'm not depending on the model. And if you watch this video to the end, you will understand That there is no need to be constantly on the hunt for the new best model And you will become much more resilient to these changes, not only for AI models, but new technology in general I want to give you this picture. [0:31] Think about you're in a room that's completely dark. You cannot see anything, you cannot hear anything, and you…
Full transcript available for MurmurCast members
Sign Up to AccessMore from ICOR with Tom | AI Productivity
I Can Build a $11 Billion Productivity App with AI (You Can Too)
The speaker demonstrates how modern AI models (Claude Sonnet 3.5) enable anyone to build sophisticated productivity applications without extensive coding knowledge, using the newly rebuilt myICOR membership platform as proof. He argues that pre-built platforms like Notion, Circle, and Mighty Networks are becoming obsolete as AI democratizes custom application development, and announces a live workshop teaching the conceptual and technical skills needed to build such apps.
I gave Claude 4 years of our work. It built this app.
A developer used Claude Sonnet 5.5 to build a fully functional ICOR-based productivity application in just one hour by providing the AI with four years of accumulated productivity knowledge and content. The resulting app successfully implements complex ICOR methodology concepts including inbox management, task prioritization, interruption handling, and life dimension tracking, though it needs UI/design refinement.
Claude just replaced every productivity app I use.
A content creator demonstrates how Claude's Sonnet 3.5 model with Code Interpreter can replace multiple productivity apps by building three fully-functional applications in under an hour with minimal prompting. The creator showcases a note-taking app with database features, a Mac application integrating their custom Obsidian plugins and ICOR life management methodology, and highlights the unprecedented speed and polish achievable without traditional development skills.
My AI team took 8 hours. Claude Sonnet 5.5 took 15 minutes.
A creator comparing an 8-hour AI team project with a 15-minute Claude Sonnet 5.5 solution reveals that excessive guardrails and restrictions paradoxically hindered the multi-agent system's performance. The speaker demonstrates how reducing constraints and context allows AI to produce more creative and functional results, though both approaches have significant limitations for production use.
Your knowledge should outlive every AI tool you use.
The speaker clarifies the distinction between the ICOR methodology (a tool-agnostic productivity framework) and its implementations like the ICOR for Life scaffold and myPKA AI team, emphasizing that users can adopt the core principles in any tool they prefer. They announce plans to restructure their membership platform by separating these components to reduce confusion and help users understand they're not locked into specific tools or systems.