Obsidian Memory Sync

Capture this Claude Code session's work into the shared Obsidian vault at ~/obsidian-vault. This vault syncs bidirectionally with a partner agent via Obsidian Sync.

When to Use

• End of every session (MANDATORY — invoke before closing)
• When user says "sync", "save", "remember this", "update obsidian"
• After completing a significant piece of work (feature shipped, decision made, lesson learned)

The Process

Step 1: Determine today's date and file path

VAULT = ~/obsidian-vault
DAILY_NOTE = {VAULT}/memory/YYYY-MM-DD.md
MEMORY = {VAULT}/MEMORY.md

Step 2: Create or append to daily note

If the file doesn't exist, create it with this template:

---
title: 'YYYY-MM-DD'
type: note
tags: [daily, YYYY]
---

# YYYY-MM-DD Session Notes (Day of Week)

## Summary
<!-- End-of-day summary goes here -->

## Conversations & Decisions

## Projects Worked On

## Leads & Opportunities

## Blockers & Issues

## Action Items / Next Steps

## Personal Notes

If the file exists, append under the correct section headings — never overwrite.

Step 3: Fill in what happened this session

Under the appropriate sections, capture:

• Conversations & Decisions: What user asked, what was decided, key context. Use ### HH:MM - Topic subheadings.
• Projects Worked On: Which projects, what progress, what changed. Include status updates.
• Leads & Opportunities: Business leads, market opportunities, ideas mentioned.
• Blockers & Issues: What's stuck, what failed, what needs attention.
• Action Items / Next Steps: Explicit next steps, promises made, deadlines. Use - [ ] checkboxes.
• Personal Notes: Anything personal the user shared.

Step 4: Update long-term memory (if significant)

If this session included any of these, update {VAULT}/MEMORY.md:

• New project started or major status change
• Key decision that affects future work
• Lesson learned (especially expensive ones)
• Infrastructure/tool change
• New API/credential setup

Also update the Claude Code memory at ~/.claude/projects/<project>/memory/ to keep both systems in sync.

Step 5: Confirm to user

After writing, tell the user what was synced. Keep it brief:

Synced to Obsidian: [1-2 sentence summary of what was captured]

Rules

• Be comprehensive — capture everything, curation happens later
• Use wiki-links for cross-referencing: [[MEMORY]], [[2026-04-01]], [[lessons-learned]]
• Timestamp entries with ### HH:MM when timing matters
• Never write secrets/credentials into daily notes unless explicitly asked
• Convert relative dates to absolute (e.g., "Thursday" -> "2026-04-10")
• Don't overwrite existing content — always append

What NOT to Capture

• Trivial back-and-forth ("yes", "ok", "thanks")
• Tool output that's already in files
• Debugging steps that led nowhere (only capture the resolution)