AI Is Quietly Taking Your Memory
AI companies are racing to own users' context and memory through integrated tools like Claude in Slack and ChatGPT's auto-memory features, creating a lock-in trap. The speaker argues users should own their context (expensive, irreplaceable) in local plain text files while renting the AI model (cheap, replaceable), and demonstrates his personal knowledge assistant system built on markdown files that work with any AI model.
Summary
The speaker outlines a critical industry pattern where AI companies are simultaneously launching tools designed to capture and retain user context and memory. Claude Tag (launched June 23rd) integrates into Slack as a persistent teammate, while ChatGPT (June 4th) introduced auto-memory that builds profiles of users across conversations without manual curation. Andrew Karpathy called this the third major redesign of AI interaction, after websites and apps—now AI agents are self-contained entities living within organizational tools.
The speaker identifies the underlying incentive: since AI models have become commodities with better versions shipping every few weeks, companies can no longer lock users in through the model itself. Instead, they're racing to own the context layer—the decisions, history, relationships, and operational memory that make each organization unique. This creates a trap that feels like pure convenience on day one (a tool saves 20 minutes, remembers team decisions, learns shorthand) but becomes dangerous over six months when users realize their entire operational memory and decision-making context lives inside a vendor's system. The speaker uses the example of note-taking apps (Roam, Obsidian, Notion, Mem, Tana) where shutdowns or pivots meant losing not just notes but the thinking structure built within them.
The critical distinction is that the AI model is the cheap, rentable part (billions to train, but costs users only token-by-token, constantly improving, impossible to own), while context is the expensive, irreplaceable part (years to build, specific to each organization, impossible to recreate if lost). Most users are inadvertently trading away their expensive context to rent the cheap model—exactly backwards.
The solution is to own the context layer in your own infrastructure and let AI models compete to be the brain running on top. The speaker demonstrates his own system: a local folder of plain text markdown files containing projects, people, decisions, and cross-connected information, with AI agents running as contracts (also plain text) on top. This architecture is inspectable (readable plain text), portable (just files on a disk), and model-neutral (can swap Claude, ChatGPT, Codex, or Gemini without changing anything). He deliberately turns off auto-memory features in both Claude and ChatGPT, controlling what gets saved in his folder based on his own rules rather than the AI's decisions.
The speaker calls his system myPKA (personal knowledge assistant) and offers the entire scaffold freely. He notes he uses the command-line interface rather than the pretty chat app specifically for more control—control over what the agent reads, which model runs, and what can touch the folder. While this seems technical, he argues it's not intimidating for non-coders; it's just typing what you want and having it done.
Key Insights
- Every major AI company (Claude, ChatGPT, Codex, Gemini) is simultaneously launching persistent context-capture tools because models have become commoditized—companies can no longer lock users in through the model itself, so they're racing to own the memory and context layer instead
- The trap springs after three to six months when users have stopped writing things down anywhere else because the AI already knows everything, and only then do they realize their operational memory and decision-making context lives entirely within one vendor's system
- The AI model is the cheap, replaceable part that users are renting by the token while giving away the expensive part—their context—for free; this is exactly inverted from how it should be
- Clem Delangue at Hugging Face stated that the peak of proprietary API lock-in has been reached and the industry is moving toward a more balanced world where open models and owned infrastructure will get a much bigger share
- A model-neutral architecture where context lives in plain text files with AI agents as contracts allows instant model-switching without losing any operational memory—demonstrated by swapping Claude to ChatGPT to Gemini while pointing at the same folder
Topics
Transcript
[0:00] if you follow me on this channel, you know my whole life and business runs through this one local folder. plain text files on my own disk, and on top of it, I run a whole team of AI agents. Right now, Claude is the engine. Now look at this. I swap Claude with Codex. Same folder, same agents, same contracts. I just swapped the brain on top, and I could d-do the same again to Gemini, GLM, and whatever you like to use. Now, here's why I'm showing you this today. Two days ago, Anthropic put Claude inside Slack, a team communication tool. [0:32] so look at what they actually said. a new way for teams to work…
Full transcript available for MurmurCast members
Sign Up to AccessMore from ICOR with Tom | AI Productivity
Claude alone took 3 minutes. With Jev, 21 seconds.
A demonstration comparing AI slide deck creation using Claude alone versus Claude integrated with Jev, showing that the hybrid approach completed the task in 21 seconds for $8 with proper formatting, while Claude-only took 3+ minutes and cost $49 with poor formatting.
Why I stick to Claude for work (most of the time)
The creator demonstrates why Claude is their preferred AI for work by comparing it with ChatGPT across multiple tests, showing that Claude better adheres to custom instructions and agentic workflows defined in local folder structures. The key advantage lies in using organized, LLM-agnostic folder systems with agents.md files rather than relying on auto-memory features.
You are using the wrong Claude for work! (Here is proof)
A video demonstrating that Claude Code is significantly more powerful than Claude Cowork for professional knowledge workers, showing how Claude Code better understands folder context, enforces safety rules, orchestrates sub-agents with different models, and creates persistent file outputs rather than temporary artifacts.
Obsidian is the tool I teach in. Keep the one you have.
The creator addresses criticism about switching to Obsidian after previously promoting other tools, clarifying that his tool-agnostic ICOR methodology remains unchanged and that Obsidian is simply an interface layer for his folder-based system. He emphasizes that the underlying folder structure, AI automation, and productivity principles are identical regardless of which tool visualizes the content.
Claude sucks. And here is why.
This video explores why Claude and other AI models produce inconsistent results, examining how model selection (Haiku vs Sonnet vs Opus vs Claude 3.5 Fable), effort levels, prompt clarity, and system context dramatically affect output quality. The speaker demonstrates these differences through a Venn diagram creation task and advocates for using organized folder systems with documented SOPs and code-based solutions to ensure consistent AI performance.