Should Hermes Agent write directly into my main Obsidian vault?
Start with a dedicated drafts folder, then manually review before moving notes into the main vault.
Second-brain workflow
Hermes Agent Obsidian workflow
An Obsidian workflow can help Hermes Agent produce durable Markdown notes that humans can inspect. It should not become a vague personal-knowledge-management dump or a place to store secrets.
Agent Guide is an independent editorial resource. It is not affiliated with, endorsed by, or sponsored by Nous Research, Hermes Agent, or Hermes/Hermes brand owners. Product names and marks belong to their respective owners.
Intent
hermes-agent-obsidian-workflow
Sources
5
Schema
2
Links
4
Direct answer
Use Obsidian with Hermes Agent when you want a human-readable layer for project notes, daily summaries, research briefs, and reviewable memory. Keep the workflow practical: folders, templates, daily notes, review rules, and clear private-data boundaries.
Do not treat a vault as a safe secret store. Notes can be indexed, synced, copied, or read by future agent sessions if folder boundaries are too broad.
Best for
- Daily notes and weekly review drafts.
- Research summaries that need human editing.
- Project logs, decisions, and source ledgers.
- Memory hygiene: moving stable notes out of transient chat context.
Avoid if
- Your vault contains secrets, private client data, or legal/medical material without boundaries.
- You want Hermes to rewrite your full vault unattended.
- You cannot separate read-only source notes from writable output folders.
- You expect Obsidian to replace Hermes memory-provider decisions.
What this page covers
- Obsidian, Markdown notes, second-brain, vault, project notes, and knowledge-base workflow intent.
- Folder structure, daily notes, project notes, memory hygiene, and what not to store.
What this page does not cover
- A plugin recommendation list.
- A first-hand Obsidian automation benchmark.
- A replacement for the Hermes memory page.
Quick steps
- Create a dedicated Hermes output folder inside the vault.
- Use read-only source folders and a separate writable drafts folder.
- Define daily-note and project-note templates.
- Run one manual research or review workflow before scheduling.
- Promote only reviewed notes into long-term memory or canonical project docs.
Known breakpoints
| Breakpoint | Why it happens | Safer response |
|---|---|---|
| Vault clutter grows quickly | Agent writes too many unreviewed notes | Use drafts and scheduled review/delete rules. |
| Private notes become reachable | Broad vault mounted into agent workspace | Mount only needed folders or use read-only boundaries. |
| Stale summaries become memory | Drafts promoted without source checks | Keep source links and reviewed dates in notes. |
| Conflicts with sync tools | Concurrent writes from sync and agent | Use a draft folder and review before moving notes. |
Security notes
- Do not store API keys, customer secrets, or private credentials in notes.
- Use folder-level boundaries and review generated notes before syncing or sharing.
- Treat generated meeting/client notes as sensitive until reviewed.
- Separate personal, work, and client vaults or profiles.
Changelog
- 2026-06-02: Added as canonical Obsidian workflow page.
Agent Guide judgment
Obsidian works best as a human-readable review layer, not as an uncontrolled memory dump. Hermes should write drafts that a person promotes into durable notes.
The boundary is the vault. If the entire vault is readable and writable, private notes, stale decisions, and client context can leak into future work.
Obsidian smoke test
- Create a dedicated Hermes drafts folder.
- Mount or expose only the folders needed for the first workflow.
- Generate one note with source links and a reviewed date.
- Manually promote or delete the note; do not let drafts become memory by default.
Profile-aware vault boundary
Official profile docs describe separate config, API keys, memory, sessions, skills, cron jobs, gateway state, and state database per profile. An Obsidian workflow should follow the same mental model: personal, client, research, and coding notes should not all share one writable vault boundary.
| Profile | Vault rule | Why |
|---|---|---|
| Personal | Separate personal notes from work automation. | Prevents private context from leaking into work drafts. |
| Client | Dedicated client folder or vault with review-only promotion. | Keeps generated notes from mixing across clients. |
| Research | Writable drafts plus source links and dates. | Makes stale summaries easier to delete or update. |
| Coding | Project-local notes, not a whole home vault. | Limits accidental access to unrelated repositories. |
Official sources reviewed
| Source | Used for | Last checked | Confidence |
|---|---|---|---|
| Hermes Agent memory providers docs | Memory-provider options, persistent-memory framing, and privacy caveats. | 2026-06-05 | high |
| Hermes Agent profiles docs | Profile isolation, multi-profile operation, and future team-routing context. | 2026-06-05 | high |
| Hermes Agent security guide | Approval modes, gateway authorization, Docker terminal backend hardening, and credential cautions. | 2026-06-05 | high |
| Hermes Agent Kanban docs | Kanban and task-state concepts folded into the workflows hub. | 2026-06-05 | high |
| Reddit Hermes Agent Obsidian workflow discussion | Community friction signal around Obsidian versus built-in memory and note-curation value; not used as product truth. | 2026-06-05 | low |
Known caveats: This workflow is source-backed and inferred from documented memory/workflow capabilities; it was not first-hand tested in this batch.
FAQ
Is Obsidian a memory provider?
Not in the same sense as Hermes memory providers. Obsidian is better treated as a human-readable note and workflow layer.
Operator checklist
Get the Agent Guide launch checklist
Receive the smoke-test order for install path, sandbox boundary, provider setup, source review, and production checks.