obsidian-save — Claude Code command: what it does, how to install
obsidian-save extracts decisions, tasks, ideas, and contacts from a Claude Code session directly into an Obsidian vault. Useful for archiving working context without manual note-taking.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat obsidian-save does
The /obsidian-save command parses the chat history and spins up parallel subagents for distinct categories: people, projects, tasks, decisions, and ideas. If the vault contains a social-media/ folder, a content agent routes hooks, stats, and swipe-file entries into dedicated files. When a conversation involves coding or project fixes, the project agent automatically logs a dev journal entry and links it to today's daily note.
Every subagent must search the vault before writing to prevent duplicate files. Notes follow the schema in references/ai-first-rules.md, enforcing wikilinks, metadata headers, and TBD flags for missing details. If that rule file cannot be located, the command stops before making changes.
What it helps with
- Extract project decisions and tasks from a conversation into Obsidian notes
- Record a developer session log linked to the daily note
- Route social media ideas, data points, and hooks to their respective files
- Keep track of mentioned contacts and interactions without orphaned pages
Example prompts for the agent
- /obsidian-save
- Save everything worth keeping from this conversation to the vault
- Archive this chat session and update relevant Obsidian notes
How to install obsidian-save
1Plugin marketplace
/plugin marketplace add eugeniughelbur/obsidian-second-brain/plugin install obsidian-second-brain@obsidian-second-brain2Manually: put the files in place
.claude/commands/obsidian-save.mdCall it with /obsidian-save. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/obsidian-save.mdCall it with /prompts:obsidian-save. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/obsidian-save.prompt.mdManually: put the files in place
.gemini/commands/obsidian-save.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about obsidian-save
How to install obsidian-save in Claude Code?
Register the marketplace repository with /plugin marketplace add eugeniughelbur/obsidian-second-brain, then run /plugin install obsidian-second-brain@obsidian-second-brain.
What does the obsidian-save command do?
It identifies keepable items in the chat, groups them by topic, and launches parallel subagents to update Obsidian notes and daily logs.
When does obsidian-save run the content agent?
The content agent only activates when a social-media/ directory is present in the vault. If the folder is missing, the agent skips it entirely.
Source text
obsidian-save.md · MIT
---
description: Save everything worth keeping from this conversation to the vault
category: vault
trigger-mode: proactive
triggers_en: ["save this", "save the conversation", "save to vault", "obsidian save"]
triggers_de: ["speichere das", "speichere die Unterhaltung", "in meinem Vault speichern", "Obsidian speichern"]
triggers_es: ["guarda esto", "guarda la conversación", "guarda al vault", "guarda todo esto"]
triggers_pt: ["salve isto", "salve a conversa", "salve no vault", "obsidian save"]
triggers_zh: ["保存这段对话", "把值得保留的内容存进知识库", "把刚才聊的整理进笔记", "保存到我的知识库"]
---
Use the obsidian-second-brain skill. Execute `/obsidian-save`:
1. Read `_CLAUDE.md` first if it exists in the vault root
1b. **Keep the raw chat (opt-in, Claude Code only for now).** Run `uv run --directory "SKILL_ROOT" scripts/session_archive.py --latest --cwd "${CLAUDE_PROJECT_DIR:-$PWD}" --json` (the skill root was given at session start as **Skill root**; substitute it for `SKILL_ROOT`). With `OBSIDIAN_SESSION_ARCHIVE` on, it writes a redacted copy of this conversation to `raw/sessions/` (what was said, without tool output, cut into linked parts of about 7,000 characters) and prints their paths. Add the part that holds each item as a wikilink in the `sources:` of the note it lands in, so a later agent can follow a note back to the full chat. The steps below still pick what is worth a note; the raw copy keeps what they skip. With the flag off it prints `"status": "off"` and writes nothing: carry on. On other agents, skip this step.
2. Scan the entire conversation and identify all vault-worthy items: decisions, tasks, people mentioned, projects started, ideas, learnings, deals, mentions/shoutouts, AND content-worthy items (hooks, data points, swipe-file material, research findings)
3. Group items by type: people, projects, tasks, decisions, ideas, deals, content
4. Spawn parallel subagents - one per group - so all note types are handled simultaneously:
- **People agent**: search for each person, create or update notes, log interactions
- **Projects agent**: search for each project, create or update notes. If the conversation was a substantial dev/work session (code written, problems solved, decisions made on a project), also write a dev-log note for it - the same artifact `/obsidian-log` produces - to the logs folder (resolved per `references/folder-map.md`: wiki-style `wiki/logs/`, Obsidian-style `Dev Logs/`), named `YYYY-MM-DD - Project Name.md`, and link it from the project's Recent Activity and today's daily note. This is why `/obsidian-save` absorbs `/obsidian-log`: a full save already captures the work, so you do not need to run both. If a dev-log for this project and date already exists, update it rather than creating a second.
- **Tasks agent**: parse tasks, add to the right kanban columns
- **Decisions agent**: find relevant project notes, append to Key Decisions sections
- **Ideas agent**: search Ideas/ for related notes, create or append
- **Content agent** (if a `social-media/` folder exists in the vault): scan for content-worthy items and route them:
- **Hooks, angles, contrarian takes** → append to `social-media/ideas.md` (dated bullet)
- **Specific numbers, stats, reusable data points** → append to `social-media/data-points.md` (with source)
- **External posts that hit + why** → append to `social-media/swipe-file.md` (link + reason)
- **Research findings, frameworks, methodologies** → create `social-media/research/YYYY-MM-DD - topic.md`
5. After all agents complete: update today's daily note with links to everything saved
6. Report back: a clean list of what was saved and where
Search before creating anything - duplicate notes are vault rot. Propagate every write to boards, daily note, and linked notes. Never create an orphaned note.
The content agent only runs if `social-media/` exists in the vault. If it doesn't exist, skip silently - don't create the folder unprompted.
---
**AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future agent` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent retrieval - not human reading.
**Anti-fabrication:** Search exhaustively before claiming any note, person, or file is absent - false absence is the most common failure mode - and never invent facts, entities, or dates (mark unknowns as `TBD`). See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain