Memory Systems Guide

Source: r/hermesagent community discussion (May 2026) Based on: Memory provider thread (17 comments), multiple setup guides, and user experiences

Memory Provider Comparison Matrix

Detailed Provider Reviews

Hindsight (Most Recommended)

Setup: Local database option available, or cloud via subscription

• Installation: Ask Hermes to set it up with local database - "it went and did it" (u/Xiaomin4114)
• Strengths: Clean memory injection, good recall, stable operation
• Weaknesses: Can extract hallucinated info from LLM (u/Confusion_Which)
• Token cost: Moderate - requires LLM for processing memories

Community Tips:

• Run via Hermes embedded option, NOT Docker (Docker reported as unstable by u/Pcorajr)
• Use cheap model on OpenRouter if budget-conscious (u/marowitt)
• Test memory recall after setup to verify it's working correctly

User Quote: "I've tested many memory systems and so far hindsight has been the best for me" - u/foomanjee

Honcho

Setup: Cloud or self-hosted, most advanced feature set

• Strengths: Most comprehensive features, excellent recall, integrated feel
• Weaknesses: Resource hog - compiles info every 2 prompts, burns 3-5x tokens (u/johnfkngzoidberg)
• Token cost: High - local generation went from "conversational" to 1-2 min waits

Community Tips:

• Use with OpenAI/gpt-oss-120b:free via OpenRouter for free operation (u/Square_Confection_62)
• Open source UI available: https://github.com/offendingcommit/openconcho (u/sublimegeek)
• Good paired with Obsidian for larger wiki/KB memory bank (u/QuantumNugget47)

User Quote: "Honcho seems to be the resource hog, but most advanced" - u/johnfkngzoidberg

MemPalace

Setup: Self-hosted with optional Obsidian integration

• Strengths: Token-efficient, MD file management via Obsidian
• Weaknesses: Less documented than Hindsight/Honcho
• Token cost: Low-Moderate

Community Tips:

• Set up hooks during initial Hermes configuration (u/kjames2001)
• Optional Obsidian integration for manual MD management (u/mrruss3ll)

OpenViking

Setup: Self-hosted, stores memory in markdown files

• Strengths: Easy to inspect content (MD files), token-efficient
• Weaknesses: Less integrated feel than Honcho/Hindsight
• Token cost: Moderate

Configuration Example (u/WegoW):

LLM: deepseek-v4-flash on opencode go
Text embeddings: OpenRouter
Storage: Markdown files

Local Holographic Memory

Setup: Built-in local option, no external service required

• Strengths: Simplest setup, no token overhead for memory processing
• Weaknesses: May lack advanced features of dedicated providers
• Token cost: Low

Community Tips:

• "The simplest one" according to u/Almarma's top-voted advice post
• Good starting point before upgrading to Hindsight or Honcho
• Local graphiti MCP also available but requires agent to call on its own (u/nesarthin)

Obsidian Integration

Setup Patterns

Pattern 1: Hermes + Obsidian Sync (Paid)

• Use official Obsidian Sync for cross-device vault sync
• Pros: Reliable, automatic
• Cons: Subscription cost

Pattern 2: Syncthing (Free, Community Favorite)

• Set up Syncthing on PC and Raspberry Pi or other devices
• Pros: Free, self-hosted, works well
• Cons: Initial setup complexity
• u/ButterscotchTiny1114 switched from Obsidian Sync to Syncthing successfully

Pattern 3: Manual File Management

• Have Hermes save to specific vault folders
• Save file locations to memory for recall
• Use "save it to Herme's Vault" command pattern (u/dontforgetthef)

Common Issues and Solutions

Issue: Agent writes to Obsidian initially then forgets about it

• Solution: Explicitly instruct agent to use vault regularly, create skills that reference vault paths
• User experience: "It took me a lot of time and effort to get her to use it" (u/Almarma)

Issue: Agent doesn't recall where information was saved

• Solution: Save file locations to memory. Create master README with folder structure.
• Pattern: Different folders for sessions, skills, automations + master README (u/dontforgetthef)

Context Management Best Practices

Preventing Memory Bloat

1. Set compression threshold at ~70% - Balances context retention with token efficiency
2. Use rolling context window - Lets old info fade naturally
3. Max tested context: 262,144 tokens reported working without issues (u/Jonathan_Rivera)

Handling Context Loss After Hours

Problem: Agent forgets conversation after display sleep or hours of inactivity

• Root cause: Session timeout, gateway restart
• Solutions:
  • Keep sessions focused and short
  • Use profiles for persistent state across sessions
  • Save critical info to memory/vault before long breaks
  • Cron jobs persist independently of session state

Memory Provider Selection by Use Case

Troubleshooting Memory Issues

Agent Forgets What It Has Access To

Reported by: u/SandStorm1863 (26 comments)

• Symptom: Hermes forgets about sub-agents, tools, or capabilities between sessions
• Solutions discussed:
  • Explicitly list available tools in SOUL.md or context files
  • Create "capabilities" reference note in Obsidian
  • Use memory system to store tool access patterns

Agent Claims to Have Done Something But Didn't

Reported by: u/HsbndThrwAwyMnoPs (14 comments)

• Symptom: Hermes says it added info to Obsidian, shows proof with images, but files unchanged
• Likely cause: Hallucination or failed write that wasn't properly error-checked
• Solution: Always verify file writes independently. Use tool verification workflow.

Context Window Clogging with Local Models

Reported by: u/Direct_Bluebird7482

• Concern: Memory provider will quickly fill 64k context window on Ollama
• Solution: Choose token-efficient memory providers (MemPalace, OpenViking) or increase context window via vLLM instead of Ollama

Community Recommendations Summary

Most users converge on: Hindsight with local database + Obsidian vault for long-term knowledge storage

Token-conscious users prefer: MemPalace or OpenViking to avoid the 3-5x token multiplier of Honcho

Advanced users combine: Multiple systems - e.g., Honcho for persona/preference + Obsidian for wiki/KB (u/QuantumNugget47)