Setting up Claude
Code with Obsidian is the easy
part. The harder — and far more valuable — part is building daily habits
around the integration so it actually changes how you work.
Most people connect the two, run a few impressive prompts, then drift
back to manual note-taking within a week. The fix is to bake Claude Code
into specific recurring moments in your day. Here are the five workflows
we recommend starting with. Each one solves a problem that vault owners
have always struggled with — and each one becomes habit-forming once
you’ve used it three times.
If you haven’t set up the integration yet, start with our Claude Code +
Obsidian guide. For graph-aware operations, see our Obsidian
MCP server setup. Then come back here.
Workflow #1:
Morning Triage — Inbox to Action List
The problem. Your /Inbox/ accumulates
faster than you process it. Things you captured last week are buried
under things you captured yesterday. By the time you get to them,
they’re stale.
The workflow. First thing in the morning, open
Claude Code in your vault and run:
“Read every note in
/Inbox/from the last 7 days. Pull
out anything that’s an actionable task — something I committed to or
something that needs a decision. Create a single note called ‘Today —
[date]’ with three sections: Must do, Should do, Could do. Sort tasks
across them based on urgency and importance. Don’t ask before creating —
just do it.”
Why it works. You stop opening 30 inbox notes
manually. You start your day with a single, prioritized action list
pulled from material you already captured. Total agent runtime: under a
minute.
How to make it stick. Add a line to your CLAUDE.md:
“When triaging the inbox, anything tagged #urgent goes into
Must do. Anything mentioning client names goes into Should do at
minimum.” The more your CLAUDE.md teaches the agent your priorities, the
better triage gets.
Workflow
#2: Pre-Meeting Brief — Vault Context On Demand
The problem. You walk into a meeting unprepared
because reading your prior notes manually takes 20 minutes you don’t
have.
The workflow. Five minutes before any meeting,
run:
“I have a meeting with [name/company] in five minutes. Read
everything in/Clients/[name]/(or
/Projects/[name]/, or wherever the relevant notes live).
Give me a one-page brief: current state of the relationship/project,
last three things we discussed, anything I committed to that I haven’t
done yet, anything urgent I should flag. Keep it tight — I’ll read it on
the way to the call.”
Why it works. You walk into meetings with the
context of someone who just spent 20 minutes prepping — but you spent 60
seconds. The compounding effect across a week of meetings is
enormous.
How to make it stick. Maintain a consistent folder
structure (/Clients/{name}/,
/Projects/{name}/) so the agent always knows where to look.
Add a 00-README.md to each folder with a one-paragraph
“what this is” so Claude Code can ground the brief without you having to
explain.
Workflow
#3: End-of-Day Journal — Capture What You Won’t Otherwise Remember
The problem. The valuable stuff that happens during
a workday — what you learned, what you got stuck on, what you decided —
evaporates by the next morning.
The workflow. Last 5–10 minutes of your workday,
open Claude Code and run:
“I’m wrapping up. Open today’s daily note (or create it if it doesn’t
exist). Ask me four questions, one at a time: (1) What did I work on
today? (2) What did I learn or figure out? (3) What did I get stuck on?
(4) What’s the one thing I want to carry into tomorrow? Take my answers,
write them up cleanly into the daily note under proper headings, and tag
anything that should resurface later.”
Why it works. The interview format works
dramatically better than a blank note. Claude Code asks; you answer; the
agent writes. You spend 5 minutes total and capture context that
compounds for weeks.
How to make it stick. Pair this with workflow #5
(Weekly Review). The journal is only valuable if something looks at it
again — and the weekly review is what does.
Workflow #4: Friday Sweep
— Vault Hygiene
The problem. Your vault rots over time. Orphan notes
pile up. Broken internal links accumulate. Duplicate notes proliferate.
Manually fixing this takes hours and nobody does it.
The workflow. Once a week, end of day Friday,
run:
“Audit the vault. Find: (1) all orphan notes (notes with no backlinks
and no incoming links from the last 30 days), (2) all broken internal
links, (3) all near-duplicate notes (titles or content that overlap
heavily). Don’t delete or move anything yet — write a report to
/Maintenance/sweep-[date].mdwith three sections: orphans,
broken links, duplicates. Suggest a disposition for each one.”
Then on Monday morning, open the sweep report, accept or reject each
suggestion, and ask Claude Code to execute the cleanups you
approved.
Why it works. You finally do vault hygiene, because
the agent does the boring 80% (finding the issues) and you only do the
20% that requires judgment (deciding what to do).
How to make it stick. Treat the sweep as
non-negotiable. Put it on your calendar. The first sweep will surface a
lot of debt; subsequent sweeps stay small.
Workflow #5:
Weekly Review — From Notes to Direction
The problem. You have a vault full of evidence about
what you’ve been working on, but no compounding insight from it. Without
periodic synthesis, your notes are just storage.
The workflow. End of week (Friday afternoon or
Sunday evening), run:
“Read every daily note from this week. Read any new notes in
/Projects/and/Clients/. Write a weekly
review to/Reviews/week-of-[date].mdwith five sections:
(1) What I shipped, (2) What I learned, (3) What I got stuck on, (4)
Themes I notice across the week, (5) Carry-forwards into next week. Be
specific — pull direct quotes and examples from my notes wherever they
sharpen the review. Don’t be generic.”
Why it works. The “themes I notice” section is where
the real magic happens. Claude Code is genuinely good at spotting
cross-note patterns that you’d miss reading the same notes manually.
Over months, these reviews become a record of how your thinking is
changing.
How to make it stick. Read the review. Don’t just
generate it. The point isn’t the artifact — it’s the moment of
reflection it forces.
The CLAUDE.md Rules
That Make These Stick
None of these workflows work consistently without a strong
CLAUDE.md in your vault root. The minimum your CLAUDE.md
should specify for daily workflows:
- Folder conventions. Where daily notes live, where
clients live, where projects live, where the inbox is, where archives
go. - Tag conventions. What
#urgent,
#followup,#idea,#research/...
mean to you. - Voice rules for generated content. Otherwise the
agent’s output won’t sound like your notes. - Things to never touch. Folders that are off-limits,
notes that should never be edited, files the agent should treat as
read-only. - Default to action, not asking. If you want the
agent to do triage and routing without asking permission for every move,
say so explicitly. (Pair with git so you can always roll back.)
For the deeper “why” of CLAUDE.md and what to put in it, see the Claude
Code + Obsidian pillar guide.
Frequently Asked Questions
Can I run all five workflows in one day? You
probably shouldn’t on day one. Pick one, run it for a week, then add the
next. The point is habit, not volume.
What if I’m not in Obsidian — does this still work?
Yes. Anything that stores markdown in folders works. The folder
structure references (/Inbox/, /Daily/, etc.)
are conventions, not Obsidian-specific. Adapt them to your setup.
Do I need an MCP server to run these workflows?
No. All five workflows above run on file access alone. An MCP
server makes some operations cleaner (especially backlink and
tag-aware queries) but isn’t required.
How long does each workflow take in agent runtime?
Most run in under a minute on a vault with a few hundred to a few
thousand notes. The Friday sweep on a large vault may take longer
because it’s doing graph analysis across the whole vault — that’s the
one to plan around.
Won’t this make me dependent on Claude Code?
Possibly. But your notes stay in plain markdown on disk, so you can
always go back to manual processing or switch agents. The vault is the
durable artifact; the agent is replaceable. That’s why we build
workflows around markdown, not around any specific tool.
Do these workflows compose with each other? Yes. The
end-of-day journal feeds the weekly review. The weekly review surfaces
themes that change how you triage your inbox the next week. The Friday
sweep keeps the vault clean enough that all the other workflows stay
fast. They reinforce each other.
Where to Go Next
If you want the broader integration setup, see our Claude Code +
Obsidian pillar guide. For the workflow philosophy underneath these
patterns — capture, process, compose, polish — see our Claude
Code markdown workflow guide. For graph-aware operations, see our Obsidian
MCP server setup.
If you’d like help building these workflows — and the broader AI
knowledge system around them — into your business or team, let’s design
your system.