Turn Hermes Conversations into Obsidian Notes Automatically

Every long chat with an AI agent produces insights: a debugging trick, a project convention, a half-formed idea, a book recommendation. Most of it stays trapped in the conversation window and disappears when the session ends. Hermes Agent is different — it already persists what matters through persistent memory and FTS5 cross-session recall. The next logical step is to turn that captured knowledge into real notes inside Obsidian, your local-first knowledge base.

This post shows how to build a hands-free pipeline that moves valuable fragments from Hermes conversations into an Obsidian vault, organized and searchable, without manual copy-paste.

Hero image: Writing notes while using a laptop at a desk by Shixart1985, CC BY 2.0, via Wikimedia Commons.

Why Hermes + Obsidian

Hermes is built around the idea that an agent should remember and improve over time. Its memory layer stores two compact files in ~/.hermes/memories/:

  • MEMORY.md — environment facts, project conventions, lessons learned.
  • USER.md — your preferences, communication style, identity.

That is useful context inside Hermes, but it is still agent-centric. Obsidian gives you a human-centric second brain: markdown files, wikilinks, graph view, full-text search, and plugins. Wiring the two together means your agent’s learning becomes your personal knowledge base.

If you are new to Hermes, start with the installation guide and the v0.19.0 release notes to get the latest memory, MCP, and cron features.

The pipeline: capture, distill, sync

A reliable auto-notes workflow has three stages:

Stage What happens Hermes feature
Capture Conversations and decisions are preserved Persistent memory + session history
Distill Raw fragments are turned into clean notes LLM summarization, skills, or cron jobs
Sync Notes land in the right Obsidian folder File tool, MCP Obsidian server, or custom skill

You can mix and match these stages. Below are three practical patterns, from simplest to most automated.

Pattern 1: Instant capture with a custom /memo skill

The fastest way to start is a slash-command skill that appends a short note to your Obsidian inbox. Create ~/.hermes/skills/memo/SKILL.md:

---
name: memo
description: Append a short note to the Obsidian inbox.
---

When the user runs `/memo [text]`, append the text to
`~/Documents/Obsidian Vault/Inbox.md` with a timestamp heading,
then confirm the line count.

After installing the skill, you can type:

/memo The postgres migration failed because the enum type already existed. Fix: drop type first.

Hermes writes the snippet to your vault immediately. It is not fully automatic, but it is faster than switching apps and keeps the inbox flowing during a conversation. For more on skills, see the Skills System docs.

Pattern 2: Nightly digest with cron + file output

For automatic summaries, schedule a cron job that reads recent sessions, distills the non-ephemeral insights, and writes a dated markdown file. Hermes has a built-in cron system that can run with skills attached.

Example CLI creation:

hermes cron create "0 22 * * *" \
  "Review today's Hermes sessions, extract lessons, decisions, and open questions, then write a dated digest to ~/Documents/Obsidian Vault/Daily/$(date +%Y-%m-%d).md" \
  --skill memo

The cron job runs in a fresh Hermes session with the memo skill loaded. Because it has access to the file tool, it can create the dated note under Daily/. You can also use --deliver local if you prefer the file to be written silently and only alerted on errors.

Key tips for cron digests:

  • Filter out ephemeral chatter. Tell the prompt to ignore greetings, tool retries, and half-baked speculation.
  • Use frontmatter. Ask Hermes to write YAML frontmatter with date, tags: [hermes-digest], and source: hermes-session so Obsidian dataview queries can surface the entries.
  • Keep it bounded. Limit the digest to the top 5–7 insights so the note stays readable.

Pattern 3: MCP Obsidian server for structured note operations

The deepest integration uses Hermes’ MCP support and an Obsidian MCP server. Once the server is registered, Hermes gains tools to read, search, create, append, and edit notes inside a specific vault. Recent Hermes work (see PR #73006) improves multi-vault selection by letting you set OBSIDIAN_VAULT_PATH or pass an explicit vault name.

A typical MCP configuration block in config.yaml looks like this:

mcp:
  servers:
    obsidian:
      command: npx
      args:
        - "-y"
        - "obsidian-mcp-server"
      env:
        OBSIDIAN_VAULT_PATH: "~/Documents/Obsidian Vault"

Exact package names and arguments depend on the Obsidian MCP server you choose. Treat the server’s README as the source of truth for command and environment variables.

With the server enabled, you can ask Hermes in plain language:

Create a note called "Auth Refactor Decisions" in my project folder and summarize the key points from our last three sessions.

Hermes calls the MCP tools to search sessions, synthesize the content, and create the note. This pattern shines when you want structured note operations — moving content between folders, updating project docs, or maintaining a Zettelkasten.

Organizing the vault

A good folder structure prevents the auto-generated notes from becoming noise:

Obsidian Vault/
├── Inbox/              # raw snippets from /memo
├── Daily/              # cron digests (YYYY-MM-DD.md)
├── Projects/           # per-project distilled notes
├── People/             # user preferences, decisions, context
└── Sources/            # external links and references

Use Obsidian templates or the Templater plugin to normalize frontmatter. A simple digest template:

---
date: {{date}}
source: hermes-digest
tags: [hermes, daily-notes]
---

# {{date}} — Hermes Digest

## Key decisions

## Lessons learned

## Open questions

## Raw snippets

When Hermes writes the file, ask it to fill each section. The result is a note you can review in minutes instead of scrolling through hours of chat history.

A complete daily workflow

Here is how the pieces fit together over a typical day:

  1. Morning: You ask Hermes to plan the day. It writes tasks to your project note and remembers your priorities in MEMORY.md.
  2. During work: You drop quick /memo captures into the Inbox while debugging or researching.
  3. Evening: A cron job runs at 22:00, reads the day’s sessions, and writes a dated digest to Daily/2026-07-31.md.
  4. Weekly review: A second cron job on Sunday compiles the week’s digests into Weekly/2026-W31.md and surfaces recurring themes.

The weekly job can be as simple as:

hermes cron create "0 20 * * 0" \
  "Read ~/Documents/Obsidian Vault/Daily/2026-*.md, summarize the week, and write Weekly/2026-W31.md" \
  --skill memo

Privacy and safety

Because notes may contain code, credentials, or personal opinions, keep these guardrails in mind:

  • Vault access is local. Your notes never leave your machine unless you sync Obsidian yourself.
  • Filter before writing. Always tell the cron prompt to exclude API keys, tokens, and private messages.
  • Run MCP servers locally. Do not expose an Obsidian MCP server over the network.
  • Review digests. Auto-generated notes are a starting point, not a permanent record. Delete or refine anything that feels off.
  • Use a dedicated vault or folder. Isolate Hermes-generated content until you trust the workflow.

Troubleshooting

Symptom Likely cause Fix
Notes are not written Hermes cannot resolve the vault path Set OBSIDIAN_VAULT_PATH to the absolute path
Cron job never fires Model/provider drift guard Pin cron.model in config.yaml or per job
Digests are too long Prompt lacks length constraint Add “top 5 insights only” to the cron prompt
Duplicate notes Cron uses relative paths with wrong cwd Use absolute paths in file operations

For cron model pinning, see the Scheduled Tasks docs.

What’s next

The line between “talking to an AI” and “maintaining a knowledge base” is blurring. Hermes gives you the building blocks — persistent memory, session recall, skills, cron, and MCP — to close that gap. Obsidian gives you ownership and structure. Together, they turn ephemeral conversations into a durable, searchable second brain.

If you want to compare Hermes with other agents before committing, see our comparison page. For setup help, the install guide is the fastest path to a working agent.