obsidian-log — Claude Code command: what it does, how to install
obsidian-log logs your current development session into an Obsidian vault. It figures out the project from conversation context and formats notes for agent retrieval.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat obsidian-log does
The command parses your conversation, identifies the active project, and drafts a session log in your Obsidian vault. It checks for _CLAUDE.md in the root folder to map paths, then looks for templates like Templates/Dev Log.md or Templates/Work Log.md. When templates are missing, it builds four sections: context, changes, decisions, and next steps.
The resulting file is saved as YYYY-MM-DD - Project Name.md inside Dev Logs/ or wiki/logs/. The command injects links into the Recent Activity section of your project note and the Work section of today's daily note. Unverified facts stay marked as TBD to prevent hallucinations.
Vault notes follow references/ai-first-rules.md, using ## For future agent preambles, [[wikilinks]], and rich frontmatter. If the rule file cannot be located, Claude Code stops and reports the issue before writing anything.
What it helps with
- log active coding sessions directly to an Obsidian vault
- link dev notes into daily notes and project files automatically
- retain technical decisions and context for future AI sessions
- record unverified entities as TBD instead of guessing
Example prompts for the agent
- /obsidian-log
- log this dev session
- log this work to the obsidian vault
How to install obsidian-log
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-log.mdCall it with /obsidian-log. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/obsidian-log.mdCall it with /prompts:obsidian-log. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/obsidian-log.prompt.mdManually: put the files in place
.gemini/commands/obsidian-log.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about obsidian-log
How to install obsidian-log in Claude Code?
Run /plugin marketplace add eugeniughelbur/obsidian-second-brain first, then execute /plugin install obsidian-second-brain@obsidian-second-brain.
What does obsidian-log do?
It gathers context from your current session, writes a structured dev log into Obsidian, and links it to both your project note and daily note.
Who is the target audience for these vault notes?
The notes are structured for future retrieval by AI agents rather than human reading. They rely on ## For future agent preambles, frontmatter metadata, and dense [[wikilinks]].
Source text
obsidian-log.md · MIT
--- description: Log this work or dev session to the vault - infers project from context category: vault trigger-mode: proactive triggers_en: ["log this work", "log this session", "log this dev session", "obsidian log"] triggers_de: ["diese Arbeit protokollieren", "diese Sitzung festhalten", "diese Entwicklungssitzung protokollieren", "Obsidian-Log"] triggers_es: ["registra este trabajo", "registra esta sesión", "registra esta sesión de desarrollo", "obsidian log"] triggers_pt: ["registre este trabalho", "registre esta sessão", "registre esta sessão de desenvolvimento", "obsidian log"] triggers_zh: ["记录这次工作", "把这次开发过程写进知识库", "记录当前工作会话", "保存这次开发日志"] --- Use the obsidian-second-brain skill. Execute `/obsidian-log`: 1. Read `_CLAUDE.md` first if it exists in the vault root 2. Infer the project from conversation context - search the vault if needed to find the right project note 3. Read `Templates/Dev Log.md` (or `Templates/Work Log.md`) if either exists; if neither does, write the sections directly: Context, What changed, Decisions, Next steps 4. Fill in: date, project, what was worked on, problems encountered, decisions made, next steps - all inferred from the conversation 5. Save to the dev-log folder resolved per `references/folder-map.md` (read the vault's `_CLAUDE.md` Folder Map first; wiki-style `wiki/logs/`, Obsidian-style `Dev Logs/`), named `YYYY-MM-DD - Project Name.md` 6. Inject a link into the project note's Recent Activity section 7. Inject a link into today's daily note Work section --- **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