Hindsight Long-Term Memory Flow

Auto-recall before turns, retain after responses, and cross-session memory through Hindsight

TURN LIFECYCLE: RECALL → RESPOND → RETAIN → REUSE User new message new session or existing one Hermes Agent profile-specific memory provider = hindsight Auto-recall prefetch relevant memory before the turn Respond use recalled context while answering Auto-retain store durable facts after the turn Hindsight knowledge graph + entity resolution + retrieval retain store extract entities add tags recall semantic search keyword match graph traversal reflect cross-memory synthesis reasoning cloud mode or local embedded PostgreSQL Entity resolution "Rohit" → person "production-blue" → environment "AWS us-east-1" → region "platform team" → team facts become connected, not just stored Deployment modes Cloud HINDSIGHT_API_KEY managed storage fastest setup Local embedded PostgreSQL free local mode hindsight-embed UI Switch UI memory surface Memory page helps you inspect memory state but provider setup still lives in Hermes config UI = inspection surface Agent config = source of truth stored facts improve the next session

Memory tools

  • • hindsight_retain stores facts with entity extraction
  • • hindsight_recall finds relevant memories before a turn
  • • hindsight_reflect synthesizes across many memories
  • • best for durable, cross-session knowledge

Auto-pilot behavior

  • • auto-recall before each turn
  • • auto-retain after each response
  • • built-in memory still stays active alongside Hindsight
  • • profile-specific setup avoids mixing unrelated memory

Modes

  • • cloud mode for easiest setup
  • • local mode for embedded PostgreSQL and local control
  • • local UI via hindsight-embed -p hermes ui start
  • • tune recall budget and memory mode in config

Hermes Switch UI • How-to diagram for Hindsight long-term memory