Use this when
  • You use Claude Code for L&D projects and keep re-explaining the same project context.
  • You want session notes, decisions, source links, and working preferences to survive between Claude Code sessions.
  • You want Obsidian to act as a durable memory layer, not just another note archive.
What you should leave with
  • A Claude Code + Obsidian operating loop for before, during, and after each session.
  • A Mission Control note, MEMORY index, project index pattern, and daily-note handoff habit.
  • A maintenance rhythm that keeps documentation alive while the work is happening.
Three ways to set this up

Build the same operating pattern at the lightest level that works.

Manual setup
  1. Create a new Obsidian vault for learning work instead of mixing it with a general personal note vault.
  2. Create starter folders: 00-Start Here, 01-Projects, 02-Sources, 03-Field Notes, 04-Prompts, 05-Examples, 06-Decisions, and 99-Archive.
  3. Add one index note in 00-Start Here that explains what each folder is for and which notes an AI assistant should read first.
  4. Create a source-note template with title, source link, date captured, what it helps with, what it does not prove, useful quotes or facts, and related project.
  5. Create a project-index template with goal, audience, current decision, source notes, prompt notes, deliverables, open questions, and next action.
  6. Move only five high-value notes into the structure first. Do not migrate everything before the pattern is working.
  7. Turn on the core features you will actually use first: backlinks, outgoing links, templates, daily notes if helpful, and properties.
  8. Create one weekly review habit: update the Start Here note, archive stale notes, and summarize useful AI threads into reusable notes.
AI-assisted setup

Use Claude Code to read the Mission Control note and MEMORY index at the start of each session, then update project notes, decisions, and handoffs as the work changes. This version is focused on Claude Code and Obsidian only.

Recommended Obsidian plugins

Add plugins only when they solve a real workflow problem.

Community plugins can make the vault much more useful, but they also add risk and maintenance. Start with core Obsidian features, then add plugins intentionally.

Dataview

Turns Markdown notes and properties into queryable tables, lists, and task views. Use it to build dashboards for active projects, trusted sources, notes needing review, prompt briefs, and source coverage.

Templater

Creates reusable note templates with variables and automation. Use it for consistent source notes, project indexes, prompt briefs, decision logs, and weekly review notes. Keep templates simple because Templater can run JavaScript and system commands.

Tasks

Finds and manages tasks across the vault, including due dates, recurring tasks, filtering, and source-file updates. Use it when project indexes and source notes need follow-up actions that do not disappear.

Omnisearch

Adds stronger vault search with weighted results and PDF or OCR support. Use it when the vault grows and you need to quickly find source notes, project context, examples, or prior prompt work.

Local REST API & MCP Server

Creates a local authenticated REST API and MCP endpoint for tools that support it. Use it only when you intentionally want an AI assistant or automation tool to read, search, or update the live vault. Treat this as an advanced setup with security review.

Recommended fields or columns

Make the system visible enough to maintain.

Field Use it for Why it matters
Title Use a clear note title that says what the note is about. Keeps the setup tied to a decision instead of becoming another storage place.
Type Mark the note as source, project, prompt, example, decision, meeting, or evergreen note. Keeps the setup tied to a decision instead of becoming another storage place.
Status Draft, active, needs review, trusted, stale, or archived. Keeps the setup tied to a decision instead of becoming another storage place.
Summary Three to five lines explaining what the note is and when to use it. Keeps the setup tied to a decision instead of becoming another storage place.
Source Link to the article, document, meeting, tool page, SME input, or project artifact behind the note. Keeps the setup tied to a decision instead of becoming another storage place.
Audience The role, team, learner group, or project this context helps. Keeps the setup tied to a decision instead of becoming another storage place.
Related project The project index where this note may be reused. Keeps the setup tied to a decision instead of becoming another storage place.
Related prompts Prompt notes that depend on this source material or context. Keeps the setup tied to a decision instead of becoming another storage place.
Review date When the note should be checked for freshness. Keeps the setup tied to a decision instead of becoming another storage place.
Use with AI Yes, no, or approved-only so sensitive context is not accidentally pasted into tools. Keeps the setup tied to a decision instead of becoming another storage place.
Views or tabs to create
  • Start Here index.
  • Active projects.
  • Trusted source notes.
  • Prompt briefs.
  • Decisions and assumptions.
  • Notes needing review.
  • Archived projects.
Ownership and maintenance

The setup only works if someone owns the rhythm.

Ownership model

The individual L&D professional owns the vault. Team-owned decisions, policies, reports, and final deliverables should still live in the approved shared system. The vault is the working memory and context layer, not a replacement for official records.

Maintenance rhythm

Review active project indexes weekly. Review source notes monthly or when a tool, policy, platform, or standard changes. Archive project notes when the deliverable is complete, but keep the final summary and reusable decisions easy to find.

Common mistakes
  • Migrating every old note before the starter structure has proven useful.
  • Saving source links without a summary of why the source matters.
  • Using tags as a substitute for clear folders, note titles, and indexes.
  • Letting AI-ready context include sensitive material without an approved data path.
  • Treating Obsidian as the team source of truth when the team works in SharePoint, Google Drive, Asana, Jira, or another shared system.
  • Forgetting that sync is not the same as backup.
Copy-ready setup checklist

Claude Code + Obsidian setup

# Claude Code + Obsidian Memory Setup

Core loop:
- Before: Claude Code reads Mission Control and the MEMORY index.
- During: Claude Code updates project notes as decisions, facts, and changes emerge.
- After: Claude Code appends a session note and updates Mission Control.
- Next session: Claude Code starts with current context instead of a blank slate.

Starter notes:
- Mission Control
- MEMORY index
- Active project index
- Daily/session notes
- Decision log
- Source notes
- Archive

Mission Control should show:
- Current priorities
- Active projects
- What changed recently
- What Claude Code should read first
- What should not be touched
- Open questions
- Next action

Project index should show:
- Goal
- Audience
- Current decision
- Source notes
- Deliverables
- Open questions
- Next action

Weekly review:
- Update active project indexes
- Summarize useful Claude Code sessions
- Update Mission Control
- Archive stale project notes
- Check sensitive context before using notes with AI

Recommended plugins:
- Dataview: dashboards and queryable source/project views.
- Templater: reusable note templates and starter structures.
- Tasks: follow-up actions across the vault.
- Omnisearch: stronger search as the vault grows.
- Local REST API & MCP Server: advanced local AI/automation access with security review.
Prompt starters

Use AI to draft the setup, then verify the system with humans.

ChatGPT GPT-5 family

Use an outcome-first prompt with the job, approved source material, constraints, and the exact artifact you want back.

I am working on Set up Claude Code with Obsidian memory for L&D work for an L&D system problem.

Goal: Help me turn the notes below into a practical next move.

Context: Use this when an L&D professional wants Claude Code to use an Obsidian vault as persistent context and living project documentation.

Use these working fields: vault location, Mission Control note, MEMORY index, active projects, sensitive data boundaries, session handoff habit, review rhythm.

Rules:
- Use only the source notes I provide.
- Do not invent policy details, metrics, learner needs, compliance requirements, or business context.
- Separate known facts, assumptions, missing information, and next actions.
- Flag anything that needs requester, reviewer, leader, legal, compliance, LMS owner, or manager confirmation.
- Keep the output practical enough to review in a working meeting.

Source notes:
[paste approved notes here]

Return:
1. Claude Code session-start checklist
2. Mission Control note
3. MEMORY index
4. Project index template
5. Sensitive-context rules
6. Session handoff checklist
7. Weekly review checklist

Claude 4 family

Use XML-style sections so context, source material, task, constraints, and output format stay separate.

<context>
I am working on Set up Claude Code with Obsidian memory for L&D work for an L&D system problem.
Use this when an L&D professional wants Claude Code to use an Obsidian vault as persistent context and living project documentation.
</context>

<source_notes>
[paste approved notes here]
</source_notes>

<task>
Turn the source notes into a practical next move using these working fields: vault location, Mission Control note, MEMORY index, active projects, sensitive data boundaries, session handoff habit, review rhythm.
</task>

<constraints>
Use only the source notes provided.
Do not invent policy details, metrics, learner needs, compliance requirements, or business context.
Separate known facts, assumptions, missing information, risks, and next actions.
Flag anything that changes scope, ownership, evidence, risk, or decision rights.
</constraints>

<output_format>
1. Claude Code session-start checklist
2. Mission Control note
3. MEMORY index
4. Project index template
5. Sensitive-context rules
6. Session handoff checklist
7. Weekly review checklist
</output_format>

Gemini 3 family

Use a clear task, labeled input, and one example pattern. For Obsidian context, use approved excerpts, Drive exports, Google Docs, or NotebookLM source sets.

Task: Help me make progress on Set up Claude Code with Obsidian memory for L&D work from the notes provided.

Context: Use this when an L&D professional wants Claude Code to use an Obsidian vault as persistent context and living project documentation.

Working fields:
- vault location
- Mission Control note
- MEMORY index
- active projects
- sensitive data boundaries
- session handoff habit
- review rhythm

Example pattern:
Field: Missing information
Good answer: Name the specific information to confirm, who can confirm it, and why it affects the next decision.

Rules:
- Use only the source notes provided.
- If information is missing, write "Needs confirmation".
- Keep the output concise and reviewable.
- End with the next best action.

Source notes:
[paste approved notes here]

Output format:
1. Claude Code session-start checklist
2. Mission Control note
3. MEMORY index
4. Project index template
5. Sensitive-context rules
6. Session handoff checklist
7. Weekly review checklist

Microsoft 365 Copilot

Use goal, context, source, expectations, and output. For Obsidian context, use approved excerpts, Word summaries, OneDrive files, SharePoint pages, Teams context, or Outlook threads.

Goal: Help me make progress on Set up Claude Code with Obsidian memory for L&D work.

Context: Use this when an L&D professional wants Claude Code to use an Obsidian vault as persistent context and living project documentation.

Source: Use the selected document, meeting notes, spreadsheet, email thread, SharePoint file, or pasted notes as the only source.

Expectations:
- Work with these fields: vault location, Mission Control note, MEMORY index, active projects, sensitive data boundaries, session handoff habit, review rhythm.
- Mark uncertain items as "Needs confirmation".
- Do not add facts that are not in the source.
- Separate known facts, assumptions, missing information, risks, and next actions.
- Summarize the top review questions for the team.

Output:
1. Claude Code session-start checklist
2. Mission Control note
3. MEMORY index
4. Project index template
5. Sensitive-context rules
6. Session handoff checklist
7. Weekly review checklist
Sources behind this guide

The tool setup should serve the workflow.

Try this one thing today

Create the Mission Control note and MEMORY index before moving old notes into the vault.