How to Build a Claude That Never Forgets You

Every session with Claude starts the same way. You open a new tab. You explain who you are. You rebuild the context you already built last week. You get a useful answer. You close the tab. Tomorrow you do it again.

You are not using an AI assistant. You are repeatedly hiring someone with no memory of yesterday. There is a fix. It takes one evening. And once it is set up, you never start from zero again.

Here is exactly how to build it.

What you are building

Two tools. Two jobs.

Obsidian holds everything. A free notes app that stores your knowledge as plain text files on your own machine. Not in a company's cloud. Not locked to any subscription. Files you own forever.

Claude thinks on top of it. It reads your vault, connects new information to what is already there, and answers questions across everything you have ever written. The whole system is plain text. Point a different model at the same folder next year and it still works. You own the brain. The tool is replaceable.

Step 1: Install Claude Desktop

• Go to claude.com/download and install the desktop app. You need a paid Claude account - Pro is $20 a month. The free tier will not work here.
• At the top you will see three tabs: Chat, Cowork, and Code. Click Code. This is Claude Code - the version that can read and write files directly on your computer.

Step 2: Install Obsidian and create your vault

• Go to obsidian.md and download Obsidian. It is free. Click Create new vault, name it "brain," pick a folder, and click Create. That folder is now your second brain. Everything Claude writes will land here as plain text.
• Type two square brackets around any word - like [[goals]] - and it becomes a link to another note. Claude handles this linking automatically once connected.

Step 3: Open the connection inside Obsidian

• In Obsidian, click the Settings gear at the bottom left. Go to Community plugins and turn them on. Click Browse, search for Local REST API, install it, and enable it.
• Open the plugin settings. You will see an API Key - a long string of characters. Copy it. Keep Obsidian open. The connection only works while the app is running.

Step 4: Connect Claude to your vault

• In the Claude Code tab, paste this command. Replace PASTE-YOUR-KEY-HERE with the key you just copied:

> claude mcp add-json obsidian-vault '{ "type": "stdio", "command": "uvx", "args": ["mcp-obsidian"], "env": { "OBSIDIAN_API_KEY": "PASTE-YOUR-KEY-HERE", "OBSIDIAN_HOST": "127.0.0.1", "OBSIDIAN_PORT": "27124" } }'

• Obsidian shows the key with the word "Bearer" in front. Do not include that word. Paste only the string of characters after it. To confirm it worked, type: "list every file in my Obsidian vault." If Claude reads your notes back, you are connected.

Step 5: Load yourself into the brain

Claude can read your vault now. But it knows nothing about you. Do not type your life story out by hand. Let Claude ask.

• Paste this: You are setting up my second brain. Interview me one question at a time. Ask about who I am and what I do, my goals this year, how I want you to communicate with me, my strengths and weaknesses, and my current projects. Wait for each answer before moving to the next. When finished, save everything into a file called CLAUDE.md at the vault root, organized with clear headers, so you load it automatically every session.
• Answer like you are briefing someone who will work with you every single day. When it finishes, open CLAUDE.md. Your context is saved. You never explain yourself again.

Step 6: Build a project structure

CLAUDE.md is your permanent context. Projects are where the work actually happens. Have Claude build one. Paste this:

• Create a project folder called youtube-channel. Inside it, create four folders: Inputs, Process, Outputs, Feedback. Then write a CLAUDE.md inside that project describing what it is, its single goal, and your specific role in helping me reach it.
• Swap youtube-channel for whatever you are building. Ideas land in Inputs. Claude works in Process. Finished work moves to Outputs. Results go to Feedback. Repeat for every area that matters.

Step 7: Work inside one project at a time

Do not open the giant vault when you sit down to work. Open just the project.

> In Obsidian, click the vault name at the bottom left, then: Manage vaults → Open folder as vault → pick your project folder → Trust.

Claude now reads only that project's context. The big vault holds your entire life. A single project ships the work.

Step 8: Turn repeated work into skills

A skill is a saved workflow Claude runs on command. Anything you do more than once should become one. Inside a project, paste:

> I want to turn this into a reusable skill. Here is how I do it, with an example: [paste your steps]. Save this as a skill file in this project's skills folder with a clear name and a description of when to use it.

Next time, you say: run the [name] skill. It executes your way, instantly.

Step 9: Connect live data

Static notes are half the brain. Connect what changes every day. To add Google Calendar, run this in Claude Code:

> claude mcp add google-workspace uvx workspace-mcp --tools calendar

Follow the sign-in flow and grant read access. Add Gmail, Slack, or Notion the same way. One rule you never break: grant read-only access wherever possible. Control access at the permission level, not with words.

Step 10: Put it on autopilot

In Claude Desktop, open the Schedule tab, click New task, and fill this in:

> Frequency: Daily, 7:00am. Prompt: Check my vault. File anything sitting in Inputs folders into the right place and link it to related notes. Flag anything that has gone stale. Write me a 3-line summary of what changed overnight.

You wake up to a brain that organized itself while you slept.

What you have after one evening

Before this, Claude forgot you the moment you closed the tab. Every Monday felt like the first day. You were the one holding all the context, and you lost most of it between sessions.

After this, every session starts where the last one ended. Every note you have ever written is connected. Every decision you have made is linked to the reasoning behind it.

One month from now you will search for something you half-remember thinking about, and the vault will surface it - connected to three other ideas you had forgotten were related. That is the moment it stops feeling like a notes app and starts feeling like a second mind. Same subscription. Completely different machine.

Bookmark this. Build it this week. The version of you who starts today will not recognize how you were working six months ago.