Tool
Hermes Obsidian: built-in skill or separate plugin?
Use the built-in Obsidian skill for Markdown vault access. Compare it with a separate chat plugin, understand memory boundaries, and verify the first note safely.
Quick answer
Hermes includes a filesystem-first Obsidian skill for reading, searching, creating and editing Markdown notes. You do not need an Obsidian community plugin or MCP server for that workflow. Set OBSIDIAN_VAULT_PATH in the active Hermes profile, resolve it to an absolute path, and verify one disposable note. A chat panel installed inside Obsidian is a separate plugin, not the same feature.
Choose by where you want to work. If you already use Hermes in a terminal or gateway and want it to maintain notes, start with the skill. If you want a chat interface inside Obsidian, evaluate a specific plugin and its backend separately. Neither choice automatically synchronizes your vault or turns every note into Hermes memory.
Setup steps
- 1Confirm Hermes works before adding notes: run hermes doctor and check hermes skills list for the Obsidian skill. Use the same named profile for setup and everyday work.
- 2Run hermes config env-path to locate the active profile environment file. Set OBSIDIAN_VAULT_PATH to the absolute path of your existing vault; do not print other environment values or paste credentials into notes.
- 3Restart or reload the intended process after changing its environment. Ask Hermes to resolve the vault path first: file tools do not expand a literal $OBSIDIAN_VAULT_PATH.
- 4Choose a dedicated Hermes-Agent subfolder, back up existing notes, and ask for one new disposable Markdown note. Stop if the chosen filename already exists.
- 5Read the test note back from disk, inspect it in Obsidian, then read it from a fresh Hermes session. Test remote devices separately; a local write does not prove synchronization.
Command map
hermes skills listCheck the Obsidian skill available in your installed Hermes version.
This is a Hermes skill, not an instruction to install an unnamed Obsidian community plugin.
hermes config env-pathLocate the environment file for the current profile before setting the vault path.
For a named profile, use the same -p selector you use to run the agent. Never share the full file contents.
hermes -p work config env-pathExample for an existing profile called work. Confirm that the gateway uses this profile too.
Replace work with your actual profile name; do not create or switch profiles accidentally.
What you can verify
Features
- ✓Search filenames and Markdown content with Hermes file tools
- ✓Read selected notes without loading the whole vault
- ✓Create notes and make targeted edits after reading existing content
- ✓Add Obsidian wikilinks between related notes
- ✓Use a concrete vault path on the machine where tools execute
- ✓Keep project documents separate from bounded Hermes memory
Why this tool matters
The built-in skill is a set of instructions for Hermes file tools. It is not a background synchronization service and does not install a chat panel in Obsidian. Its documented path convention is OBSIDIAN_VAULT_PATH; when unset, the skill uses ~/Documents/Obsidian Vault. Explicit paths make multi-profile and server setups easier to diagnose.
Obsidian itself stores notes as Markdown files in a vault folder and refreshes when those files change. That makes the filesystem workflow possible without the Obsidian desktop app running on the Hermes host. A server must still have the files: opening its dashboard from a laptop does not mount the laptop vault.
A community chat plugin has a different trust boundary. Identify its maintainer, repository, supported runtime and credential storage before installing it. Obsidian warns that community plugins inherit its access levels, including file and network access. A feature name or marketplace listing is not proof that a plugin is official or isolated.
Local notes do not guarantee offline processing. A configured cloud model can receive passages Hermes reads, and sync tools or optional plugins can send data elsewhere. Limit the documents supplied to each task and verify the actual provider route before using sensitive material.
Built-in MEMORY.md and USER.md are bounded, profile-specific context stores, separate from the vault. Writing a project note does not modify them. Their system-prompt snapshot loads at session start, so test a saved fact in a fresh session rather than assuming an already-running session has reloaded it.
Self-hosted browser chat exists: the current Web Dashboard includes TUI Chat via PTY/WebSocket. The managed-versus-self-hosted choice is about who maintains runtime, credentials, networking, backups and gateways. Managed access does not imply automatic access to your private Obsidian vault.
Best use cases
How this fits with Hermes Agent
Start with the built-in skill
Use it when the desired outcome is file work: finding a note, creating a research summary or editing a project brief. Follow the step-by-step connection guide below for the disposable-note prompt and missing-path checks.
Evaluate a separate plugin only for its extra interface
Use a community plugin when its documented in-app chat experience solves a need the file workflow does not. Check the backend host and exposed folders, then test with a disposable vault before using personal notes.
Keep remote sync separate
Choose explicitly where the authoritative vault lives and how another device receives approved files. Avoid simultaneous writers to the same note, inspect conflict copies, and keep a backup that can restore an unwanted edit.
Related Hermes Agent guides
Connect Hermes to your vault
Follow the full setup, disposable-note prompt and fresh-session readback test.
Plan remote vault access
Separate local files, runtime location and device synchronization.
Troubleshoot memory persistence
Diagnose failed saves and wrong profiles instead of copying the vault into prompts.
Back up Hermes state
Keep a restorable backup without putting credentials in synced notes.
Compare self-hosted and managed operation
Choose who maintains the runtime without assuming hosted access includes local files.
FAQ
The filesystem-first Obsidian skill needs neither. It uses Hermes file tools to read and write Markdown at a resolved vault path. A separate in-Obsidian chat plugin is a different integration with its own installation and trust requirements.
Set it to the absolute vault path in the active Hermes profile environment file. Use hermes config env-path, with the same profile selector as your notes workflow, to locate that file. Restart or reload the relevant process after changing its environment.
Check the path from the actual runtime, not only your desktop. File tools do not expand $OBSIDIAN_VAULT_PATH. Resolve it to an absolute path, verify the correct profile, and check remote filesystem access or container mounts before retrying.
No. A vault setting and a prompt are not an operating-system permission boundary. Use restricted filesystem permissions or an appropriately isolated container mount when access must be enforced.
No. A Markdown note is separate from built-in MEMORY.md and USER.md. Hermes must perform an actual memory write for that store to change; its system-prompt snapshot is refreshed at the start of a new session.
Only after you provide an explicit, authorized file-transfer, sync or mounted-storage path. A hosted browser interface does not automatically grant the remote runtime access to local laptop files.
No. Notes remain local files, but content read into Hermes prompts can go to the configured model provider. Sync services and optional community plugins can also use the network. Verify every data path if offline processing is required.