obsidian

Operate on the user's Obsidian vault as plain Markdown files. Obsidian itself does not need to be running — the vault is just a directory tree of .md files.

Setup check (lazy — resolve path once, don't re-probe)

The vault path resolves as $OBSIDIAN_VAULT_PATH env var → fallback ~/Documents/Obsidian Vault. Resolve it once when you first need it this conversation; do not re-probe printenv on every turn. Operate on the resolved path directly and map failures:

• os.fs.list / read errors with ENOENT / "no such file or directory" → Setup playbook → "Vault path does not exist".
• the path exists but holds no .md files → Setup playbook → "Resolved path is not a real vault".

Vault paths often contain spaces — pass them through os.fs.* tools verbatim, no quoting needed.

Setup playbook (when prerequisites are missing)

When a check fails, the agent's job is to OFFER concrete help and EXECUTE the fix itself — not to dump setup instructions on the user. Use this dialogue shape: