Claude Code + Obsidian
Give Claude a Standing Memory with Claude Code and Obsidian
Obsidian is a separate, independent note-taking app. This guide is independent and not affiliated with or endorsed by Anthropic or Obsidian.
Every new chat with Claude starts from nothing. It doesn't remember your job, your current projects, or the decision you made with it yesterday, unless you type it all out again. That's a real limit for anyone who wants to use Claude as a standing assistant rather than a one-off question box. This guide sets up a fix that sticks: a plain-text vault Claude reads and writes to every time you work with it, so it picks up where you left off instead of starting over. The two pieces are Anthropic's Claude Code, Anthropic's command-line coding tool, and Obsidian, a free note-taking app that stores everything as ordinary text files in a folder you control. Neither product was built with the other in mind, and nothing here requires you to write a line of code. You'll install Claude Code, create a small Obsidian vault, give it a folder structure and a couple of rules files Claude reads automatically, then set up two or three recurring tasks that keep that memory current on their own, on a schedule, without you opening a chat window every day to do it by hand.
To give Claude a standing memory, install Claude Code, Anthropic's command-line coding tool, then create a small Obsidian vault with a folder structure plus a CLAUDE.md and STATE.md file that Claude reads at the start of every session. Those files hold the facts worth remembering: your role, your current projects, the people you work with, and where things stand. From there, the Claude desktop app's local scheduled tasks run a morning brief and a weekly review inside that vault on a schedule, on your own computer, so the memory stays current without you updating it by hand every day.
Published
Free lesson · no account neededMeet ClaudeWhy Claude?6 minStart the free lessonKey Takeaways
- Claude Code, Anthropic's command-line coding tool, has no memory between chats on its own. A plain-text Obsidian vault it reads and writes to every session is what makes a standing memory actually stick.
- A CLAUDE.md rules file and a STATE.md status file, both read at the start of every session, do more for continuity than re-explaining your situation in the chat ever will.
- The Claude desktop app's local scheduled tasks run only on your own computer, only while the app is open and the computer is awake, and do exactly one catch-up run for anything missed within the last 7 days.
- Claude Pro costs US$20 a month and includes Claude Code. Obsidian is free. No separate purchase is required to set this whole system up.
- Three small habits keep the system honest: dump into the Inbox without sorting, ask Claude to find things instead of searching yourself, and fix a wrong memory once in the rules file instead of re-explaining it each session.
Copy and Paste
Prompts You Can Use Today
Set up the vault's folder structure and files
I've created an Obsidian vault called Brain in my Documents folder. Open it and build this folder structure inside it: Inbox, Projects, People, Decisions, Daily, Reviews, Archive, and a memory folder. Then create a CLAUDE.md file with starting rules for how you should work with me, a STATE.md file under 80 lines for where things currently stand, and a memory/MEMORY.md index file. Before you write any of it, interview me with ten questions, one at a time, covering my role, my main projects, the people I work with most, how I make decisions, how I want daily notes captured, and anything else that would help you understand how I work. Use my answers to write CLAUDE.md and STATE.md so they actually reflect me, not a generic template.
Paste this as your first message in the vault's folder, after you've installed Claude Code and created the Brain vault in Obsidian.
Morning brief scheduled task (weekdays)
Read today's and yesterday's Daily notes, everything currently sitting in Inbox, and STATE.md in this vault. Write a short morning brief at the top of today's Daily note: what's outstanding from yesterday, what's new in the Inbox that needs a decision, and what's on deck today based on Projects and Decisions. Keep it under 15 lines. If it's after 5pm when this runs, skip the brief format entirely and just post one line noting that today's window was missed, so I'm not reading a stale morning brief in the evening.
Use this as the instructions for a local scheduled task set to run on weekday mornings, pointed at your vault folder.
Weekly review scheduled task (Fridays)
Read every Daily note from this week in this vault. Update STATE.md so it reflects where things actually stand, keeping it under 80 lines by rewriting rather than endlessly appending. Move anything fully resolved this week from Projects or Decisions into Archive, dated. Flag, in a short list at the end of your summary, anything in Decisions or Projects that hasn't been touched in three weeks or more, so I know what's gone stale and needs a real decision instead of just sitting there.
Use this as the instructions for a local scheduled task set to run Friday afternoons, pointed at your vault folder.
The Problem
Why Claude Needs a Memory System
A chat with Claude is, by default, a clean slate. Close the window and open a new one, and whatever you explained about your job, your team, or the project you're mid-way through is gone. For a quick question that's fine. For anyone trying to use Claude the way they'd use a capable assistant who sticks around, it means re-explaining your whole situation over and over, which gets old fast and quietly discourages you from using it for the bigger, ongoing stuff.
The fix isn't a feature Claude ships with. It's a habit, built on files. Claude Code, Anthropic's command-line coding tool, can read and write plain text files in a folder on your computer, and it reads certain files automatically at the start of a session. If those files hold the facts worth remembering, written in plain language, Claude effectively remembers them too, every time, without you retyping anything.
Obsidian is the other half. It's a free note-taking app built around one idea that matters a lot here: everything you write in it is stored as ordinary text files in a folder, not locked inside a proprietary database somewhere. That's exactly the shape of thing Claude Code can open, read, and edit directly, which is why the two pair so naturally even though neither was designed with the other in mind.
What follows is the whole setup: installing Claude Code, creating an Obsidian vault, building a small folder and file structure Claude reads every session, and then handing the upkeep to a couple of scheduled routines so the system stays current without becoming a new chore on your list.
Step 1
Install Claude Code
The fastest way in is the native installer. Go to Anthropic's Claude Code setup page at code.claude.com/docs/en/setup and run the one-line command it lists for your system; the page covers Mac, Linux, and Windows separately, so just copy the line under your platform. If you'd rather use Homebrew on Mac or Linux, `brew install --cask claude-code` does the same job. Either way, you don't need to understand what the command is doing; you're just running a script that puts the claude command on your computer.
Once it's installed, check it worked by running `claude --version` in the same terminal window. If you want a fuller check of your setup, `claude doctor` runs a short diagnostic and tells you about anything that needs attention before you go further.
Next, run claude by itself and follow the browser prompt it opens to sign in. You'll need a Claude Pro, Max, Team, Enterprise, or Console account; the free claude.ai plan does not include Claude Code. Claude Pro is US$20 a month and includes Claude Code, so this is the plan most people on this guide will already have or will want.
Last, install the Claude desktop app from `claude.com/download`. You won't need it for the install or the vault itself, but Step 4 of this guide runs the scheduled routines that keep your memory current through the desktop app's own local task scheduler, so get it onto your computer now and sign in there too.
Step 2
Create an Obsidian Vault Named Brain
Obsidian is free to download and use, and setting up a vault, which is just Obsidian's word for a folder it manages, takes under a minute. Download it from its own site if you haven't already, then open the vault switcher. That's the small icon in the bottom-left corner of the app, or you can reach the same menu through the command palette by searching for "Open another vault."
Choose "Create new vault." You'll be asked for a name: type Brain. Then use the Browse button to pick where it lives on your computer; choose your Documents folder, so the vault sits somewhere you'd find it without thinking. Click Create, and Obsidian opens the new, empty vault.
That's the whole setup on Obsidian's side. The vault is, underneath the app's interface, nothing more than a folder named Brain inside Documents, full of plain .md text files once you start adding to it. That plainness is the entire point: Claude Code can open that same folder directly and treat it as any other project folder on your computer, reading and editing the files inside it the same way it would code in a software project.
Keep the vault open in Obsidian while you work through the rest of this guide, so you can see the folders and files appear as Claude Code creates them in the next step.
Step 3
The Memory System: Folders and Files
Four pieces, all plain text, all inside your Brain vault. Claude Code builds these for you from the setup prompt below; this is what each one is for.
The Folder Structure
Inbox, Projects, People, Decisions, Daily, Reviews, Archive, and a memory folder. Each one is just a place for a specific kind of note, so nothing you capture has to be sorted on the spot.
CLAUDE.md
A rules file Claude Code reads at the start of every session in this folder, the same standing-instructions idea a software project's own CLAUDE.md serves, just pointed at your life instead of a codebase.
STATE.md
A short "where things stand" file, kept under 80 lines on purpose. It gets rewritten as things change, not endlessly appended to, so it never becomes a scroll of outdated status updates.
memory/MEMORY.md
An index file inside the memory folder that points to where specific facts live, so Claude can find the right note fast instead of re-reading the whole vault every time you ask something.
Setting It Up
Building the Structure with One Prompt
You don't have to build any of this by hand. With the Brain vault open in Obsidian and a terminal open in that same folder, run claude to start a session, then paste the setup prompt below as your very first message. It tells Claude Code exactly which folders and files to create, and instructs it to interview you first rather than guessing at the details.
The interview matters more than the folder structure does. A CLAUDE.md written from a template is generic; one written from ten honest answers about your role, your main projects, the people you work with, how you make decisions, and how you want daily notes captured is actually useful from day one.
Answer plainly and specifically. "I manage a five-person support team and report to the VP of Ops" does far more for Claude than "I work in management." The more concrete your answers, the less Claude has to guess later, which is the entire reason this setup exists in the first place.
Step 4
Build Routines with the Claude Desktop App
Files that only update when you remember to update them drift out of date fast. The fix is the Claude desktop app's scheduled tasks, which run Claude Code against your vault on a timer, with no chat window to open. In the app's Code tab sidebar, look for "Scheduled." If your version still shows the older "Routines" label instead, click Routines, then "New routine," which opens the same dialog.
Click "New task" to open it. If you're offered a choice between "Create with Claude" and "Set up manually," choose "Set up manually" so you're writing the instructions yourself rather than describing the task in a sentence and hoping it's interpreted the way you meant.
Name the task and write its instructions, using one of the two prompt examples further down this guide as a starting point. Then expand "Advanced settings," go to the General tab, and turn on "Only on this computer." That's what makes it a local task: it gets direct access to your vault's files and runs only on this machine, only while the desktop app is open and the computer is awake. Pick your Brain vault as the local folder, set the schedule using the Daily, Weekdays, or Weekly presets in the Trigger card, choose a permission mode and model, and click Create.
Right after creating it, click "Run now" once, and when Claude asks for permission to read or write a file, choose "always allow" each time rather than "allow once." Skip this and every future scheduled run can stall at the same permission prompt with nobody there to answer it, which defeats the point of scheduling it in the first place.
One behavior worth planning around: these tasks only fire while the desktop app is open and the computer is awake, and if a run is missed, the app does exactly one catch-up run for the most recently missed time, covering anything missed within the last 7 days, and discards anything older than that. If timing matters to a task, write the guardrail into the prompt itself, the way the morning brief example below checks the clock before deciding what to post, rather than assuming the schedule will always fire exactly on time.
The Daily Habit
Three Rules That Keep the System Honest
The files and the schedule do most of the work. These three habits keep the whole thing from quietly drifting.
Dump, Don't Sort
When something crosses your mind, put it straight into Inbox and move on. Deciding where it belongs can wait for the weekly review; sorting in the moment is how capturing things stops happening at all.
Ask, Don't Dig
Need to know what you decided about a project last month? Ask Claude to find it rather than scrolling through old Daily notes yourself. That's the entire reason the vault and the index file exist.
Correct It Once
If Claude's memory of something is wrong, fix CLAUDE.md or STATE.md once, in the file, rather than correcting it in conversation every session. A wrong fact left in the chat only gets fixed for that one chat.
Why This Holds Up
What a Plain-Text Memory Buys You
None of this depends on a feature that could change or disappear. It's a folder of text files you fully own.
Plain Text, Forever
Markdown files open in any editor, on any computer, for as long as computers open text files. Nothing here locks your memory inside one app's database.
Local and Private
The vault lives on your own computer. A local scheduled task reads and writes it directly, with nothing about your notes required to pass through a server to make the system work.
Scales With You
Start with a handful of notes; the same Inbox, Projects, and Daily structure holds up whether you're tracking one project or a dozen, without a redesign.
Nothing Extra to Pay For
Claude Pro at US$20 a month includes Claude Code, and Obsidian is free. The entire system described in this guide costs nothing beyond a plan most readers already have.
Keep Building With Claude
Setting up Claude's memory is one skill among many for getting real, repeated use out of Claude Code. Nightschool AI's free signup gets you into the curriculum, and the Build Your First Claude Code Project kit is the natural next step once your vault is up and running.
Frequently Asked Questions
What does it actually mean to "give Claude a memory"?
It means setting up files Claude reads automatically at the start of every session, so facts about your role, projects, and decisions persist across chats instead of resetting each time. Claude itself doesn't gain a new capability; you're giving it a place to keep notes it checks every time, the same way a person would.
Do I need to know how to code to set this up?
No. Installing Claude Code is running one copy-pasted command, creating the Obsidian vault is a few clicks, and the folder structure and rules files are built for you when you paste the setup prompt in this guide. Everything you write into CLAUDE.md or STATE.md is plain language about your own work, not code.
How much does this cost?
Claude Pro is US$20 a month and includes Claude Code, so if you already have Claude Pro, Max, Team, Enterprise, or a Console account, there's nothing extra to buy. Obsidian is free to download and use. The free claude.ai plan on its own does not include Claude Code, so you'd need to upgrade for this specific setup.
Why use Obsidian instead of a plain folder of text files?
You could use a plain folder, and the underlying idea would still work, since Obsidian vaults are just folders of markdown files. Obsidian adds a readable interface for browsing and linking your own notes, which makes the vault pleasant to use directly, on top of the files Claude Code reads and writes the same way either way.
What's the difference between CLAUDE.md and STATE.md?
CLAUDE.md holds standing rules: who you are, how you want Claude to behave, and context that rarely changes. STATE.md holds current status: what's active right now, kept under 80 lines and rewritten rather than appended to, so it stays a snapshot of today rather than a growing log.
What's a "local" scheduled task, and why does it matter here?
Turning on "Only on this computer" under Advanced settings makes a scheduled task local: it gets direct access to a folder on your machine, your Brain vault, and runs only on that computer, only while the Claude desktop app is open and the computer is awake. A non-local task has no file access to a folder like this, so local is the setting this guide's routines need.
What happens if my computer is asleep when a scheduled task is due?
The Claude desktop app does exactly one catch-up run for the most recently missed time, covering anything missed within the last 7 days, and discards anything older. If timing matters, write a check into the prompt itself, such as skipping the normal format and posting a short note instead if the run is happening much later than planned.
Is this guide affiliated with Anthropic or Obsidian?
No. This is an independent educational guide, not published or endorsed by Anthropic or by Obsidian. Claude, Claude Code, and Obsidian are named here only to describe them accurately; they are Anthropic's and Obsidian's own products and trademarks respectively.
Can I use this for personal life, not just work?
Yes. The folder structure (People, Decisions, Daily notes, and the rest) works just as well for personal projects, family logistics, or anything else you'd want remembered across sessions. Nothing about the setup assumes a work context specifically; it's a general memory system you point at whatever you want Claude to track.
What if Claude's memory of something is wrong?
Fix it once, in CLAUDE.md or STATE.md, rather than correcting it inside a chat. A correction typed into one conversation only fixes that conversation; the next session reads the files fresh and would repeat the same wrong fact until the file itself is updated.
Turn This Setup Into Your First Claude Code Project
Your CLAUDE.md file is the same habit this free lesson teaches, just applied to a vault instead of a codebase.