Obsidian CLI

Use the installed official Obsidian CLI for authorized vault work. Confirm its version and command help; app state and CLI behavior can differ by release.

Resolve the target

1. Use the caller's explicit vault.
2. Otherwise read an existing project vault binding such as .obsidian-vault.
3. If the current directory is inside a vault, verify that identity.
4. Resolve remaining ambiguity before writing.

Current official help supports vault=<name> and vault=<id>, placed before the command. Prefer a verified ID when names collide. Do not assume a universal environment variable selects a vault.

Check availability

Inspect whether the app and CLI are available. Use a read-only command against the intended vault before writing.

Empty output alone does not prove that a vault is closed or empty. Check command status, installed help, app state, and a known existing note. A historical silent-output defect is not a permanent CLI contract.