Source: raw/Claude_Code_+_Obsidian_-_My_family_s_AI_brain.md + ai-research/sfxmath-scott-farrar-2026-11-11.md (guest’s site, fetched 2026-11-11, used only to confirm the name spelling)

Creator: Claire Vo, How I AI, with Scott Farrar (sfxmath.com; a math teacher, per the episode) · URL: https://www.youtube.com/watch?v=wdyOjcCj2hw · Duration: not recorded · Platform: YouTube (auto-captions, fetched 2026-11-11). Sponsors: WorkOS and Jira Product Discovery (Atlassian).

Scott Farrar runs his household from a folder of markdown files that Claude Code reads and writes, viewed in Obsidian. He moved from chat to a coding agent because he could not tell what a chat remembered about him; with files, every new session reads the same visible memory. It is the LLM-wiki pattern applied to a home: appliances and serial numbers, warranties, insurance quotes, a prioritized family to-do list, project files with checklists, a linter that keeps the agent’s writing short, and a wall display that shows what is due and what got done.

Key Takeaways

  • The problem is opaque memory. In a long chat about car insurance he could not tell whether to paste in all his documents, whether the conversation was drifting, or what it remembered. He wanted to be “confident that AI was grounded in my truth”.
  • The fix is files the agent reads and writes. Claude Code keeps the memory of each topic in markdown on his computer; a new session reads the same files. He can open any file to inspect the memory, but day to day he asks Claude Code loose questions (“what should I do next on this project?”, “what’s going on with the fridge?”) and it finds the relevant file.
  • Let the agent tell you what to collect. At setup he asked Claude what he should gather about the house. It told him to photograph every appliance; the photos (with serial numbers) are summarized in an appliances list file, and Claude enforces how it is organized. Later, asking about the fridge’s ice maker, it already knew the warranty ends in 2027.
  • Project files with checklists move work forward. The car-insurance project holds the quotes, coverage gaps and a checklist; asked what to do next, it named the blocker (email the agent with a specific question). He says it reminds him of overdue items (“you’ve been waiting since September 24th”) and that he has “run out of pending fires”: the ball is now usually in someone else’s court.
  • Ideas, projects and wins are separate states. New thoughts go to an ideas backlog (earthquake readiness, re-landscaping, peeling paint, mapping the circuit breaker labels from a photo). An idea is promoted to a project file when he starts it, and a finished project is closed and moved to a wins list. The rules for this live in the project’s CLAUDE.md.
  • One master to-do file, built from a brainstorm. He and his wife listed every household task, big and small; Claude compiled them with a priority, a cost estimate and a reference for each. This is the file he opens by hand most.
  • A linter keeps the agent from bloating the memory. A script checks that “verbose chat agents” have not made the to-do list too long. He added it after an early version started writing every update into the to-do table despite a CLAUDE.md instruction to keep it brief.
  • Scope is explicit. His setup constraints: shared with his wife, scoped to the household, no finances and no medical information.
  • Two-person sharing is a sync choice. First a shared Dropbox folder on both laptops; Claude warned about sync conflicts if both edit at once and suggested GitHub as the alternative. His wife thought GitHub was not worth it. They settled on a mix: GitHub for scripts (the linter, the wall-display export) and Dropbox for the rest, relying on not editing at the same time.
  • A wall display makes it visible to the family. He uses Dakboard, which can show a custom web page. A Claude-built script scrapes to-do items, upcoming trips and other data into a panel: current projects, trips, one small suggestion for today (his example: a $12 recaulking job), longer-term items, things for the kids, and a “recent wins” section (“you fixed the water heater in one day. Great job, Dad”).
  • The domain list, if you want one: repairs; insurance and comparison shopping; future planning (wills, guardianship, trusts, consolidating retirement accounts); IT and device management (for example which kids’ iPads lose iOS support); trip planning; emergency readiness.
  • He keeps agency on purpose. He contrasts his setup with agents that act for you (he names Muse and Instinct; Vo says she runs Grok Bot and Muse that way). He wants the AI to suggest and to “put me to work”, while he decides and sends the emails.
  • When it goes wrong, he checks the memory. He starts a new session, or asks “why did you think that? how did you get that idea?” to make sure a wrong belief has not been written into a file.

Try It

  1. Make a household folder and open it in both Claude Code and Obsidian. Ask Claude: “What information should I gather about my house?” and do what it says (photograph each appliance, serial plate included).
  2. Write a CLAUDE.md with your scope and states: what is in scope (household only), what is out (finances, medical, if you choose), and the idea → project → win lifecycle with one checklist per project.
  3. Do the brainstorm. Sit down with your partner, list every task, and have Claude turn it into one to-do file with priority, cost estimate and reference columns.
  4. Add a length linter for the files the agent edits most, so status updates go into project files and the to-do list stays short.
  5. Pick a sync method by how real-time your collaboration is. Light, rarely simultaneous editing: a shared Dropbox folder is enough. Scripts you change: put them in Git.
  6. Put one view on a wall or a shared screen with today’s small task and a wins list.
  7. Try Vo’s variant: record a video walking through your house and ask the model what you should be thinking about. She proposed it on air; it was not tested in the episode.

Implementation

Tool/Service: Claude Code (agent), Obsidian (viewer, graph view), Dropbox and GitHub (sync), Dakboard (wall display). Setup: A markdown folder with an appliances list, a master to-do file, an ideas file, project files and a wins list; CLAUDE.md holding the structure rules; a linting script; an export script that feeds a Dakboard custom web page. Cost: Not stated, apart from the example $12 recaulk suggestion. Integration notes: The same file-based pattern this vault uses for its own wiki; see where to host a second brain for other sync and hosting options.

Open Questions

  • The names of the linter and export scripts, and what exactly the linter checks beyond length, are not shown.
  • Whether the household folder and the Obsidian vault are the same directory is implied by the graph view but not stated.
  • The guest’s surname is captioned “Farrar” and “Fra”; his site sfxmath.com titles itself “Scott Farrar”.