Give Your AI Agent a Memory It Can't Forget β And You Can Actually Read.
Every conversation session archived as clean Markdown, automatically secret-scrubbed,
tracked for token telemetry, and staged for human review. No black boxes. No vendor lock-in.
Native Obsidian power with built-in MCP server support.
Your agent now remembers why you decided things, your vault has a local undo history, and cron noise stays out of your real chat logs.
Axioms03-Resources/Axioms.md
The few beliefs everything else derives from
β
Principles03-Resources/Principles/
Standing rules distilled from repeated decisions
β
Decisions03-Resources/Decisions/
Hard-to-reverse choices, with alternatives rejected
π§v1.24
Decisions, Principles & Axioms
Log hard-to-reverse choices from Decisions/TEMPLATE.md. The Alternatives Rejected section is mandatory, so agents stop re-proposing ideas you already ruled out. Axioms.md ships empty on purpose: it should hold your beliefs, not generic filler.
πv1.24
Local Git Safety Net
Hook session_git_snapshot.py into Hermes' on_session_end and every session gets its own commit you can git diff or revert. Local history only: it never pushes or fetches. A secret-scanning gate blocks the commit if anything looks like an API key or private key, and logs only the file path, never the content.
ποΈv1.23.1
Cron Runs Kept Separate
Cron logs, lock files and cron-run session notes now live in 04-Archives/Cron/, so Daily/ holds only your real chats. Upgrading? migrate_cron_sessions.py moves old cron notes over and is safe to re-run.
β v1.23
Post-Install Verification
The installers now finish by running verify_install, which sanity-checks vault structure, plugins, the MCP server and the memory pipeline, so problems show up on day one instead of week three.
ποΈv1.23
Opt-In Feature Packs
Scripts are grouped into beginner, analyst, poweruser and experimental packs under _System/Scripts/features/. Start with the core and copy in more when you're ready.
πv1.23
Template Drift Checker
template_drift.py compares your vault to the latest template release by SHA-256 and sorts every file into safe, customized, outdated or missing, so you know exactly what an update will touch.
π³οΈv1.22
Interactive Memory Review
promote_memory.py --review walks you through pending candidates one by one: promote to MEMORY.md or your User Profile, dismiss, or skip. Every action lands in the consolidation audit log.
πv1.22
Dream Cycle v2
dream_cycle.py was rebuilt as an autonomous reflection engine that consolidates memories between sessions, and now ships with its own test suite.
Compare the context window token overhead of naive chat log dumping vs Hermes Brain's human-staged fact memory.
Daily Agent Sessions10 chats/day
1 session40 sessions/day
Avg Tokens per Session4,000 tokens
1k tokens (short)12k tokens (deep spike)
π‘ Why this matters: Staging verified facts into 04-Archives/Memory-Review/ extracts durable knowledge while discarding 92% of transient chat noise from prompt tokens.
Naive Unstaged Context
1.2M
monthly prompt tokens
Hermes Brain Footprint
96k
staged facts injected
Tokens Saved (Monthly)
1.1M (92%)
context reduction
Estimated API Savings
$3.31 / mo
at $3.00/1M tokens avg
Information Architecture
Built on the Proven PARA Method
Organized for discoverability, speed, and effortless agent context ingestion.
Explore the directory hierarchy below.
Vault Root Hierarchy
01-Projects/
02-Areas/
03-Resources/
04-Archives/
_System/
01-Projects β Active Charters & ADRs
01-Projects/
Contains active initiatives with concrete deadlines and deliverables. Includes Architectural Decision Records (ADR) with 4-agent peer review personas (Argus for security, Codex for code, Ledger for token efficiency, Vox for human alignment).
Key Files & Artifacts
π Hermes-Agent-Vault-Setup.mdMaster hub note and deployment charter
π ADR/ADR-001-Memory-Pipeline.mdArchitectural record of staging protocol
π Projects.baseObsidian Dataview live database of active projects
Model Context Protocol
Built-In MCP Server (hermes_brain_mcp.py)
Expose your Obsidian second brain directly to Claude Desktop, Cursor, OpenClaw, and any MCP-compatible client over stdio.
Exposed Agent Tools & Resources
Click any tool below to test the simulated stdio JSON-RPC request and see the real-time response payload:
vault_search(query, tags)
Keyword, regex, and frontmatter tag search across the entire vault.
read_note(path)
Safely fetch Markdown note content, frontmatter, and headings.
get_user_profile()
Fetch operator operating parameters, boundaries, and tone guidelines.
stage_memory_candidate(fact, category)
Stage candidate facts directly into the Kanban queue for human review.
vault_stats()
Telemetry metrics on sessions, token usage, projects, and archiver health.
Choose the setup option that fits your workflow β from a 1-paste chat prompt to an interactive terminal script.
Fastest: Run the automated installer directly in your terminal
Downloads the latest template, asks where you want your vault, checks for Obsidian, registers HERMES_VAULT_PATH, then runs verify_install to confirm the vault structure, plugins, MCP server and memory pipeline are all wired up.
Zero Manual Terminal Work: Paste directly into your Hermes / OpenClaw chat
Hermes will clone the repo, run the installer, configure the environment, and wire up the hourly archiving cron job automatically.
Clone https://github.com/mistrysiddh/hermes-brain-template into a new "Hermes Brain" vault for me. Steps:
1. Ask me where I want the vault folder to live (default: ~/Hermes Brain on Linux/macOS, or %USERPROFILE%\Hermes Brain on Windows).
2. Clone the repo into that location.
3. Run the platform-appropriate installer (_System/Scripts/Installers/install.sh or install.ps1).
4. Relay any questions to me and confirm env.HERMES_VAULT_PATH is set.
5. Create an hourly session-archiving cron job named "hermes-brain-archive-hourly" pointing to <vault>/_System/Scripts/hourly_archive.py.
6. Show me the verify_install results and fix anything it flags.
Own Your Private Git Repo with Full Version History
Use GitHub's green "Use this template" button to fork the repository privately into your GitHub account, then clone it locally:
No! The core vault, session archiver, and memory-review pipeline work with any Hermes / OpenClaw agent without requiring local models. Only the optional trend-digest and nocturnal dream cycle scripts use Ollama or sentence-transformers for local semantic embeddings.
100% private. Everything lives in your local vault directory (or private GitHub fork). All session archives in 04-Archives/Daily/, candidate reviews in 04-Archives/Memory-Review/, and plugin configs are strictly git-ignored so you never accidentally commit personal data.
Yes. The vault structure, Dataview queries, Kanban boards, and templates make an outstanding standalone Obsidian "Second Brain" for developers and engineers. The Hermes automation simply adds automated session harvesting on top.
Run ./_System/Scripts/Installers/update.sh (or update.ps1 on Windows). It pulls the latest scripts, templates, and bug fixes without touching your existing personal notes, daily logs, or user profiles. Want to see what would change first? Run python _System/Scripts/template_drift.py "<vault-path>" to get a report of which files are safe, customized, outdated or missing.
Since v1.24, you can wire _System/Scripts/session_git_snapshot.py in as a Hermes on_session_end hook. It commits a local snapshot of the vault after every session (creating a local-only repo on first run), so a bad multi-file edit is one git revert away. It never pushes or fetches, and it refuses to commit if it spots something that looks like a secret.
Since v1.23.1, cron-run session notes are filed under 04-Archives/Cron/sessions/ so Daily/ only holds real conversations and your Dataview queries stay clean. Upgrading from an older vault? Run python _System/Scripts/migrate_cron_sessions.py --vault "<vault-path>" once (add --dry-run to preview) to move the existing ones.