🧠 Why Claude Code needs a second brain
The difference between a session that forgets everything and an agent with searchable external memory. Here you'll learn the vocabulary and the “why”—without any unexplained terms.
🤖 The agent and its "memory"
O Claude Code is an AI agent that lives in your terminal. Unlike a regular chat, it acts: reads project files, edits code, runs commands, and chains steps to complete a task. When we talk about its "memory," we mean everything it can see when it responds.
🔰 New here? What is an "agent"
A LLM is the AI model that runs behind ChatGPT/Claude. A agent is this model with tools: things it does on its own — open a file, run a command, edit a line. Claude Code is exactly that, inside your terminal.
The agent's memory has two sources: the current conversation (what you said and what it read in this session) and what you points for it to consult (files, rules, indexes). The problem: the conversation disappears when the session ends, and pointing it to “the entire repository” rarely fits. That’s the gap this course solves.
✓ Real memory
- ✓Persists across sessions.
- ✓It’s searchable: the agent finds what it needs.
- ✓Stores relationships, not just loose text.
✗ Just the session
- ✗Forgets everything when you close it.
- ✗Starts from scratch on large projects.
- ✗Relearns the same context every time.
🔑 Key concepts
🪟 The context window and its limits
A context window is how much text the model can read at once. It’s measured in tokens — word fragments (about 3 to 4 characters each). It’s large, and newer models can handle up to 1 million tokens, but it’s still finite: an entire repository, with hundreds of files, rarely fits all at once.
🔰 New here? What is a "token"
A token is the unit the model reads. The word “memory” can become 2 or 3 tokens. The more you pack into the window, the more it “pays” to read — and there’s a limit. That’s why choosing what reading matters just as much.
↑ Only a handful of files fit in the window; the entire repository overflows. That’s why the agent needs to choose well what to read — and a map helps with that choice.
🔑 Key concepts
🔍 Why text search (grep) isn't enough
When the agent doesn’t have a map, its tool is the grep: literal search for a word inside the files. It finds where the term appears — but it doesn't know what it relates with what or why. “Finding” isn’t “understanding.”
🔰 New here? What is "grep"
grep is a classic terminal command that searches files for a word and returns the lines where it appears. Useful, but dumb: it doesn’t know synonyms, context, or connections.
↑ Grep returns a pile of locations; the map returns the concept e your neighbors. It's the difference between a list of addresses and a neighborhood map.
🔑 Key concepts
🧩 What is a "second brain"
"Second brain" is a personal productivity term: a knowledge base external and organized that you consult instead of trying to remember everything. Here, we’ve adapted the idea for the agent: the second brain is the graph + o vault that preserve a project's understanding outside the temporary session.
💡 The central idea of the course
Take knowledge out of a conversation that disappears and put it somewhere persistent, navigable, and searchable — for you e by the agent.
- •Persistent: doesn't disappear when the session ends.
- •Navigable: concepts connected by links, not standalone files.
- •Queryable: the agent finds what it needs without scanning everything.
🔰 New here? What is "PKM"
PKM (Personal Knowledge Management) is the practice of storing and connecting what you learn. Obsidian is a PKM tool—and that's why it fits so well here.
🔑 Key concepts
📝 What Claude Code already has built in
Claude Code isn’t amnesiac by default. It already reads a file CLAUDE.md at the project root with instructions and preferences, and has its own memory. That’s great for rules ("always run the tests," "use Portuguese")—but it isn't a map of an entire repository.
# Projeto X - Sempre responda em português. - Rode os testes antes de dizer "pronto". - A documentação de referência está em ./docs.
Notice: the CLAUDE.md says “the docs are in ./docs,” but doesn’t say how the concepts in the docs connect. That's where Graphify comes in — it doesn't compete with the built-in tool; it complements: the native graph stores rules; the graph stores the map.
🔑 Key concepts
🎯 The promise of the Graphify + Obsidian stack
Putting it all together: the Graphify creates the map from a repository or documents; the Obsidian saves this map as navigable markdown; the Claude Code consult the map in your project context. Together, they’re the second brain.
Graphify creates the map
Extracts entities, relationships, and communities from a source. Output: the graph.
Obsidian stores the map
One markdown file per concept, with backlinks. Persistent and navigable.
Claude Code consults the map
Answers about the project in the right context, without rereading everything.
🔑 Key concepts
✋ Self-recovery (optional, non-blocking): why does a knowledge map help more than just grep?
📌 Module summary
Next module
1.2 · Knowledge graphs made simple — nodes, edges, communities, and god nodes.