Video summary
Claude just killed ALL Note-Taking, Planner, and Health Apps. Here is proof.
Main summary
Key takeaways
Summary of the video (technological/product concepts & features)
The speaker argues that a “local folder” PKM (Personal Knowledge Management) approach, paired with Claude (AI) running via the local filesystem, can replace (or eliminate reliance on) many subscription-heavy note-taking, planning, health, and document apps. The key claim is that they “killed” tools by making everything local-first, interlinked, and AI-interactable.
1) Tool stack history → “local folder” approach
The creator describes migrating through many PKM/note tools over the years, including:
- Apple Notes
- Notability / GoodNotes
- Evernote
- Roam / Obsidian
- Notion
- Mem / Tana
- Heptabase
They emphasize the final architecture:
- Everything lives in one downloadable local folder (distributed via “myICOR”).
- The folder is structured as wiki-linked Markdown files, allowing easy compatibility with Obsidian.
- Their workflow is presented as a repeatable “scaffold” approach for community members.
2) New interface built on top of the local folder (free via myICOR)
A major feature is a custom web/GUI “hub” they built that:
- Launches a local server and opens a UI in the browser
- Is local-only (no sign-up, no subscription for the interface)
- Can be accessed on phone via the same network (remote access via VPS/web app is mentioned, though the demo is local)
What the interface provides
A) “PKM cockpit” / PKM system visualization
The local folder’s contents become viewable through an interface that includes visual hubs for:
- My Life
- Key elements
- Goals
- Habits
- Projects
- Topics
- Journal
It also includes:
- “Today’s actions”
- A “today’s calendar” view
B) Action + planning merged into one tool
They claim they replaced Sunsama and planning workflows with their own planner view inside the hub.
Planner functionality shown:
- Pulls in calendar events and Todoist tasks
- Clicking tasks supports “Open in Todoist”, with changes syncing back to the planner view
- Time-blocking UI:
- Morning/afternoon split
- Lunch break
- Work hours configuration
- Remaining time indicators in the afternoon block
- “Highlight of the day” and “weekly goals” determine what gets done
C) “Central place” across tools
They argue the hub is necessary because life planning isn’t only Todoist:
- Mentions ClickUp for business/project management alongside personal tasks
- Described as tool-agnostic in principle, using APIs where available
3) AI integration: “Personal Knowledge Assistance (PKA)”
Instead of forcing AI into third-party PKM plugin systems, they build an AI layer that works directly with the folder.
Key points:
- Notes are readable and editable locally (Markdown + attachments stored in the folder)
- AI is used to:
- Automatically create/edit wiki links (reducing manual PKM friction)
- Provide “Discuss with AI” per note using Claude with full folder context
- Use “terminal”/Claude calls to answer questions grounded in local data
- They also argue this avoids paywalls/token costs common in other PKM tools that charge extra for AI
4) Knowledge graph + navigation improvements over Obsidian graph
The interface includes a knowledge graph described as more useful than Obsidian’s for their navigation style.
It supports:
- Viewing connections/cross-links
- Clicking nodes to open linked notes
- Displaying metadata
- Running AI discussion with context from the selected note
5) Visual deep thinking (“whiteboards”) + fleeting notes
Two creative-thinking features are showcased:
A) Whiteboard-like visual workspace
- Supports node/edge connections between concepts
- Clicking/creating notes from within the visual canvas
- Connections can be expanded to reveal contextual meaning
- AI discussion can be invoked with the selected connection/context
B) Fleeting notes
A fast capture editor that includes:
- Markdown styling + headings via hashtags
- Collapsible headers (triggered via command shortcuts)
- Attachments (e.g., screenshots) stored locally
- Pinning key fleeting notes to bring them quickly to the hub
Everything is stored as local files and cross-linked back into the Markdown knowledge base.
6) Journal + cross-linked meeting insights
- The journaling section is shown as cross-connected to:
- People/contacts
- Key elements
- Other notes and documents
- Mentions long-term journaling sources, including:
- Backfilled from tools like Day One (used for over 10 years)
- Includes images/attachments tied into entries, with navigable backlinks
7) Health tracking and workout tracking (local-first; “replaces health apps”)
The video strongly claims the same local-folder + AI context approach can replace health apps.
Highlights include:
- Health data:
- 15 years backfilled weight, nutrition entries, and workouts (demo account)
- Blood test/lab values included locally
- Updates:
- An “auto export app” exports health data into the local folder
- Each day when launching Claude, data is pulled/updated in the local database
- AI-driven insights:
- Detects patterns from journal entries and health logs
- Shows habit tracking tied to goals
- Example: “Run 10K under 55 minutes” → habit “morning run”
- Habit tracking:
- Visual progress for individualized habits
- Meal logging via photos (example: Claude creates entries from images)
- Workouts:
- Route/map view similar to Strava-style tracking
- Safety caveat:
- Positioned as not a replacement for a doctor, but helpful for contextual symptom awareness
8) Document library + Team Inbox for scanned files
- Mentions external scanner hardware feeding into a Team Inbox folder on the local filesystem
- Document ingestion:
- PDFs/images stored locally
- AI organizes into a document library
- Each document includes notes/context and sometimes related files (e.g., GPX data)
- Work-in-progress / deliverables:
- A deliverables area lists active projects with timestamps/titles
- Clicking deliverables opens formatted Markdown with backlinks and AI-driven editing/review
9) Integrations & secrets: API keys stored locally
- The interface supports connecting other services (e.g., Linear, ClickUp, Todoist)
- API keys handling:
- Uses local
.envfiles stored inside the folder - Keys are not pushed to GitHub
- AI reads the folder and can “wire up” integrations referencing local env variables
- Uses local
10) Backups and remote access
Backups
- Uses Time Machine to back up the local folder
- Cloud backup options are mentioned, with warnings against syncing setups that can cause failures
Cloud sync warning (important)
- If using iCloud, ensure “Keep Downloaded” to avoid offloading that creates “ghost” files and breaks AI/context consistency
Remote usage
- Can upload the folder or access via VPS
- Mentions using Claude app with commands like:
/remote/desktopto continue working with the same folder
11) Claude tooling preference: Claude Code over Cowork
- The speaker recommends Claude Code for professionals due to multi-agent workflows and deeper coding/automation control
- They explicitly say they would not use “Cowork” due to efficiency/feature limitations
Overall “product thesis” in the video
A local, wiki-linked Markdown knowledge base + a custom local UI + Claude AI with full filesystem context can unify:
- Notes / PKM
- Planning (actions + calendar + time blocking)
- Journaling
- Knowledge graphs
- Visual deep thinking
- Health tracking and habit management
- Documents and deliverables
…and reduce dependency on multiple subscription apps.
Main speakers/sources
- Tom (primary speaker; frequently referenced as “Tom”)
- Paco Cantero (mentioned as co-founder; also demonstrates/creates related planning interface behavior)
- Claude (AI system used throughout)
- Third-party tools referenced for integration: Todoist, ClickUp, Calendar, Apple Watch, Day One, Obsidian, Heptabase, Sunsama, and scanning hardware (unnamed)