Claude → Obsidian

claude-to-obsidian

Export Claude Code sessions to your Obsidian vault as readable Markdown.

Each session becomes one .md file named YYYY-MM-DD-<session-id>-<slug>.md, where the date is the session's start time and the slug is taken from the session title (/rename) or the first user prompt. Re-exports of the same session overwrite the same file.

Demo

An example exported session rendered in Obsidian:

What you get

• Automatic export on session end via a SessionEnd hook — triggers on /exit, /clear, /logout, and other graceful shutdowns.
• Manual export mid-session via /claude-to-obsidian:export — useful for snapshotting before a /compact or sharing work-in-progress.
• Obsidian-friendly rendering:
  • User and assistant turns shown as colored callouts (👤 question / 🤖 success)
  • Tool calls and results in collapsible callouts
  • Code blocks preserved with language hints
  • HTML tags inside content escaped so they don't break callouts

Install

/plugin marketplace add mohamed-osama-aboelkheir/claude-to-obsidian
/plugin install claude-to-obsidian@claude-to-obsidian
/plugin config claude-to-obsidian

When prompted by /plugin config, set vault_dir to an absolute path inside your Obsidian vault — e.g.:

/Users/you/Documents/MyVault/ClaudeSessions

The directory will be created if it doesn't exist.

Upgrading from a manual install

If you previously wired this script up by hand (custom slash command, hook entries in ~/.claude/settings.json), remove those before installing the plugin so the script doesn't run twice on session end.

How it works

hooks/hooks.json        ─► SessionEnd → scripts/export_session_to_obsidian.py
commands/export.md      ─► /claude-to-obsidian:export → same script
scripts/export_…        ─► reads JSONL transcript, writes Markdown to $vault_dir

The Python script:

1. Reads the JSON payload from stdin (hook mode) or finds the most recent transcript for the current working directory (manual mode).
2. Walks the JSONL transcript, rendering user, assistant, system, tool-use, and tool-result entries.
3. Writes the result to $CLAUDE_PLUGIN_OPTION_VAULT_DIR (set via plugin config). Falls back to CLAUDE_OBSIDIAN_VAULT if set.
4. Logs to $CLAUDE_PLUGIN_DATA/export.log.

Failures never block session end — the hook always exits 0.

Known limitations

• Obsidian Dataview plugin: if you have Dataview installed with "Inline Field Highlighting" enabled, it may decorate ==text== patterns inside code blocks. Workaround: in Dataview settings, disable "Enable Inline Field Highlighting" — or exclude claude_sessions/.* in the plugin's exclude regex.
• Not byte-identical to /export: Claude Code's built-in /export slash command isn't exposed as a CLI, so this plugin renders the JSONL transcript itself. The format is approximate, not exact.

Configuration via environment variable

If you prefer a shell-profile setting instead of plugin config:

export CLAUDE_OBSIDIAN_VAULT=/Users/you/Documents/MyVault/ClaudeSessions

Plugin config (CLAUDE_PLUGIN_OPTION_VAULT_DIR) takes precedence when both are set.

License

MIT — see LICENSE.