Build a Self-Improving AI Second Brain with Claude Code and Obsidian in One Evening
Persistent AI memory that lives in local plain text sidesteps vendor lock-in and gives developers a knowledge base that outlasts any single model or tool. The permission-first security model is the practical difference between a toy and something safe enough to run unattended.
The system solves AI amnesia by storing personal context, projects, and daily inputs as plain-text Markdown files. Claude Code reads the vault directly, files new information, creates cross-note links, and answers questions without needing a re-introduction. A four-folder pipeline—Inputs, Process, Outputs, Feedback—keeps work flowing, while reusable skills automate repeat tasks.
Setup swaps Anthropic's model for DeepSeek via CC Switch to cut costs, then walks through building a personal profile, structuring projects, and hooking up a daily auto-organizer. The vault stays pure text, so switching models later requires no migration.
Security hinges on one rule: govern with permissions, not prompts. API keys stay in tool configs, Claude runs scoped to a single project directory, and Git provides a rollback net. Three open-source starter repos offer pre-built skeletons for those who want a faster start.
Plain-text vaults decouple the knowledge base from the model, which means the brain survives API deprecations and pricing changes that would kill a proprietary solution.
The permission-mode hierarchy—plan, acceptEdits, and the deliberately avoided bypassPermissions—is a practical security gradient that most agent workflows still lack.
Treating the vault as a Git repo is a cheap, universal safety net that works across operating systems and doesn't depend on any AI tool's built-in undo.
The interview pattern for building CLAUDE.md offloads self-documentation to the AI, which produces a more structured and queryable profile than a human would write unprompted.