obsidian-vault-manager

You can manage multiple Obsidian vaults by discovering, registering, and switching between them using a local registry script. It tracks an active vault and a working folder to constrain edits and searches within the project.

To constrain Obsidian note searches, set a default working folder within an active vault. This isolates fast text search and edits to a specific directory, preserving frontmatter integrity and preventing modifications outside the designated area.

Yes, you can automate Obsidian vault registration and notes scripting by executing local Python commands. The script allows adding vault paths, merging discovered directories, and setting active environments without manual GUI interaction.

Yes, editing markdown notes through this method preserves frontmatter integrity. It safely handles refactoring, organizing tags, links, and attachments while maintaining the original metadata structure at the top of your files.

The local registry enforces strict isolation to the skill root and project data directory. Operations are constrained to registered paths, meaning editing or searching outside the active vault's working folder is restricted by design.

To discover and register existing Obsidian vaults, run the discovery command with a merge flag to scan for directories. You then add specific paths to the local registry to activate them for note management.