obsidian-capturelisted

# Obsidian Capture Save an ad-hoc note, decision, or thought to the vault immediately. Captures always land in `Claude/captures/` (global, not project-specific) and are linked into the project's daily note automatically. ## Step 1 — Check configuration Read `OBSIDIAN_VAULT_PATH` from the environment: - Bash: `bash -c 'echo $OBSIDIAN_VAULT_PATH'` - PowerShell: `$env:OBSIDIAN_VAULT_PATH` If empty, stop and tell the user: > "OBSIDIAN_VAULT_PATH is not set. Re-run `install.sh` and provide your vault > path when prompted, or add it manually to `~/.claude/settings.json` under > the `env` key." Also read: - `OBSIDIAN_REST_API_KEY` (empty string if unset — key presence gates REST API use) - `OBSIDIAN_REST_API_PORT` (default `27124` if unset) - `OBSIDIAN_REST_API_HTTPS` (default `"true"` if unset) - `OBSIDIAN_PROJECTS_FOLDER` (empty string if unset — used for daily note routing) ## Step 2 — Collect content Ask the user: "What do you want to capture?" Accept a title and body, or just body text (title will default to the first line of the body if not provided separately). ## Step 3 — Write capture file (REST API if key present, filesystem fallback) ### 3a. REST API attempt (skip if `OBSIDIAN_REST_API_KEY` is empty) If the key is set, attempt to write the capture file via PowerShell. **Vault-relative capture path** (always): `Claude/captures/<YYYY-MM-DD>-<HHmm>.md` **Build the capture markdown** (same format obsidian-writer would produce): ```markdown --- type: claude/captu