pi-obsidian-vault

Agent-safe Obsidian vault access for Pi: auto-detect, retrieve, validate, plan, write, edit, manage, and explicitly destroy Markdown with human approval.

Package details

← Back
extensionskill

Install pi-obsidian-vault from npm and Pi will load the resources declared by the package manifest.

npm repohome report
$ pi install npm:pi-obsidian-vault
Package
pi-obsidian-vault
Version
0.2.1
Published
May 4, 2026
Downloads
351/mo · 351/wk
Author
itscool2b
License
MIT
Types
extension, skill
Size
1.7 MB
Dependencies
0 dependencies · 3 peers
Pi manifest JSON
{
  "extensions": [
    "./src/index.ts"
  ],
  "skills": [
    "./skills/obsidian-research"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

Pi Obsidian Vault

Install it, point Pi at your Obsidian vault once, and then just ask for what you want.

pi install npm:pi-obsidian-vault

This is a Pi extension, not an Obsidian community plugin or desktop GUI. It lets Pi safely search, read, validate, plan, write, edit, move, trash, restore, copy, and explicitly destroy Markdown notes in your local Obsidian vault.

Quick start

  1. Install the package.
  2. Open Obsidian once, or tell Pi your vault folder path:
use this Obsidian vault: /home/me/Documents/My Vault
  1. After that, talk normally:
find my notes about the roadmap
make a note from this summary
append this to today's project note
move that note to Archive

Pi handles the tool calls for you.

What it takes care of

  • Finds or remembers your vault path (vaultPath).
  • Auto-opens Obsidian when a vault-touching tool needs it.
  • Uses read-only tools for research.
  • Shows previews before changing notes.
  • Asks for human approval before normal mutations.
  • Uses separate destructive approval for permanent delete/replace/empty trash.
  • Redacts local paths in user-facing output.

Most users do not need env vars, tokens, templates, or manual tool calls.

Useful commands

/obsidian-vault status
/obsidian-vault set-vault <path>
/obsidian-vault forget-vault
/obsidian-vault auto-open on|off|status
/obsidian-vault auto-write on|off|status
/obsidian-vault auto-destroy on|off|status

/obsidian vault also works as an alias.

What gets installed

Pi registers these tools for the agent:

  • obsidian_config
  • obsidian_retrieve
  • obsidian_validate
  • obsidian_plan
  • obsidian_write
  • obsidian_edit
  • obsidian_manage
  • obsidian_destroy

You normally do not call these yourself. The agent chooses the right one.

Safety, briefly

  • Read-only tools do not mutate your vault.
  • dryRun: true is preview-only.
  • Normal writes/edits/moves ask for human approval unless you enable session auto-write.
  • Permanent delete, folder delete, full-note replacement, and empty trash require separate destructive approval.
  • No overwrite-by-default, broad vault dumps, broad vault scans, automatic link rewriting, arbitrary CLI commands, shell/network actions, or GUI automation.
  • Tests use temporary or disposable vaults. Real-vault checks are manual/opt-in only.

If something is wrong

Check setup:

/obsidian-vault status

Use a different vault:

/obsidian-vault set-vault /path/to/vault

Turn off auto-open:

/obsidian-vault auto-open off

Turn prompts back on:

/obsidian-vault auto-write off
/obsidian-vault auto-destroy off

Version

Current package version: pi-obsidian-vault 0.2.1.

Security and issues

See SECURITY.md. Do not include private vault contents, secrets, or absolute local paths in public issues.