v0.2.3 — markdown write-out safety + filename guard; hard advisor ban

Highlights

• Markdown write-out safety for the obsidian-vault agent. Composed note bodies no longer collide with Dataview/Obsidian rendering: :: inline fields, bare <word> HTML tags, $=/```dataview fences, and ===/`---` setext separators are now handled so summaries (e.g. Done backlogs) render correctly instead of garbled.
• Filename guard. The agent strips forbidden characters (/ \ : * ? " < > | # ^ [ ]) from note names/titles before creating/renaming — no more accidental subfolders from a / in a title.
• Hard advisor ban. The agent never consults the advisor (no exceptions); it asks the user instead, cutting the biggest source of latency.
• Recording pipeline mirror. The same Dataview/rendering-safety rule is applied to both session-summary.sh summarization prompts, so auto-recorded session notes get the same protection.

Full changelog: v0.2.2...v0.2.3

v0.2.2 — Faster obsidian-vault agent (no advisor on routine work)

Highlights

• The obsidian-vault agent is faster. It no longer consults the advisor on routine note operations (create / edit / append / read / search / move / organize). The advisor guidance is injected globally into every agent, so the vault agent had been making a slow advisor round-trip on every edit — the single biggest source of latency. An explicit override now tells it to skip the advisor for routine, reversible vault work and to prefer a concise user question even for high-stakes cases.

Full changelog: v0.2.1...v0.2.2

v0.2.1 — SessionStart config injection + delegation

Highlights

• New SessionStart hook (hooks/session-context.sh): resolves the obsidian-chronicle config once per session start and serves two consumers from the single result.
  • Main session — injects the resolved vault paths + a rule to delegate all vault work (read/search included, not just writes) to the obsidian-chronicle:obsidian-vault agent, via additionalContext.
  • obsidian-vault agent — subagents don't receive SessionStart context, so the hook also writes the resolved config to a cwd-keyed cache file that the agent reads instead of re-running resolve-config.sh.
• Fires on startup / resume / clear / compact, so the injected snapshot also refreshes after compaction.
• Fail-safe: recursion guard for the claude -p summarizer child, silent exit + stale-cache removal when no vault is configured, never blocks session start.
• agents/obsidian-vault.md reads the cache first (falls back to the resolver).
• /obsidian-chronicle:setup clears the cache after writing config.

Full changelog: v0.2.0...v0.2.1

v0.2.0 — auto-record Claude Code sessions to Obsidian

obsidian-chronicle auto-records every Claude Code session to your Obsidian vault — a structured note + a Daily Note line. No clicks.

Highlights

• 🪝 Hook-triggered recording on SessionEnd / PreCompact / /done
• 🗂️ Structured note (Goal / Key Decisions / Files Changed / Result callout) + one linked Daily Note line
• 🔁 Resume-aware — resuming appends to the same note (matched by session_id), no duplicates
• 🌐 Output language configurable (e.g. "language": "Japanese") — title, headings, callouts localized
• 🪟 Experimental Windows support
• 🛠️ Pure bash + jq — no daemon, no build step

Install

/plugin marketplace add takashito/claude-obsidian-chronicle
/plugin install obsidian-chronicle@obsidian-chronicle
/obsidian-chronicle:setup