Hindsight Memory for Hermes Agent: Is It Unlimited and Free?
By Matt Cullerton, founder of Mavric and Apso
Hindsight is an MIT-licensed long-term memory system for AI agents from Vectorize, and it plugs into Hermes Agent as an external memory provider. A TikTok from @josephbchandler says it is free, has "no limit," and fixes Hermes condensing its built-in memory. Self-hosting is free and raw storage is unbounded, but Hindsight condenses memories on purpose, its Cloud version is metered, and it runs alongside Hermes' capped memory files instead of replacing them.
What is Hindsight?
The Hindsight overview describes three operations (retain, recall and reflect) and a tiered memory structure: world facts, experience facts, observations, mental models and knowledge pages. Observations are consolidated beliefs drawn from raw facts, and mental models are curated summaries drawn from observations.
The repository is MIT licensed and ships a Docker image, a pip install, a Helm chart and a Python embedded mode.
Does Hindsight give Hermes unlimited memory?
The video says, "Hermes does come with its own built-in memory, but as it fills up, the agent has to condense or remove things. Hindsight is better. There's no limit."
Hindsight's own blog disagrees. The Consolidation Problem in Agent Memory opens with "An agent that remembers everything is an agent that remembers nothing useful." It lists four levers that every consolidation policy uses: importance, merge, decay and eviction. Hindsight runs all four.
One part of the claim holds. Hindsight says "eviction is a compliance tool, not a performance tool," used for GDPR, user deletion requests and PII redaction. It does not delete raw facts to free space. Raw storage is effectively unbounded, while the material the agent reads back is compressed and decayed by design.
How does Hermes built-in memory work?
The settings screen in the video shows a "Memory Budget" of 2200 and a "Profile Budget" of 1375. The Hermes memory docs define these as character limits: memory_char_limit: 2200 (roughly 800 tokens) and user_char_limit: 1375 (roughly 500 tokens). Both are the stock defaults.
The two files live under ~/.hermes/memories/ and are loaded into the system prompt at session start. They are kept small so the prompt prefix stays stable for caching.
Hermes does not trim memory in the background. When the files are full, the write tool "returns an error instead of silently dropping entries," and the agent "makes room itself," consolidating or removing entries in the same turn before retrying.
Does Hindsight replace Hermes memory?
No. The Hermes memory providers docs say external providers run alongside built-in memory and only one external provider can be active at a time.
Hindsight's Hermes integration guide warns that with both active "the model may prefer the built-in one." It recommends disabling MEMORY.md and USER.md if you want Hindsight as the main store. If you keep them, "every entry the agent adds or replaces in them is also saved to the bank, tagged builtin-memory."
Installing Hindsight keeps a copy of what Hermes would otherwise prune, but the capped files keep getting pruned. In the video, the Hermes "Memory Provider" setting still reads "Built-in."
Is Hindsight free?
The self-hosted build is. The speaker runs his instance on a Tailscale address, which means he self-hosts. The MIT license costs nothing, but every retain and reflect calls a language model, so inference still costs money unless you run a local model. The project documents HINDSIGHT_API_LLM_PROVIDER=ollama for that. The video does not say which model provider the speaker uses.
Hindsight Cloud, shown on screen behind a "Start free on Cloud" button and a $5 signup credit, is metered. The billing page lists:
- Retain: $10.00 per million input tokens
- Recall: $0.75 per million output tokens
- Reflect: $0.05 per call
- Retrieve Model: $0.25 per million output tokens
- Refresh Model: $0.05 per call
- File Conversion: $7.50 per million output tokens
- Storage: $0.25 per million tokens per month, free for the first 30 days after a memory is retained
Can Codex, Claude Code and Hermes share one Hindsight memory?
Yes, through MCP. Hindsight exposes an MCP endpoint per memory bank, enabled by default at http://localhost:8888/mcp/{bank_id}/. The repository names Claude Code, Cursor, Codex and GitHub Copilot as clients, and xAI's Grok Build CLI also supports MCP.
There are two caveats. An endpoint on a private Tailscale network is reachable by local clients on that network, not by a cloud-hosted assistant, so "even Grok" depends on which Grok client you mean. The video also shows vendor logos rather than four agents reading one bank, and the banks visible on screen are named "atlas" and "hermes-agent," which suggests separate banks.
The video ends by asking viewers to comment "Memory" for a guide and shows a page promoting the creator's paid Agent Operator Skool community.
Bottom line
Self-hosted Hindsight is free software that gives Hermes and other MCP clients a shared, uncapped store of raw memories. It still consolidates what the model sees, its Cloud version bills per operation, and it supplements Hermes' 2,200 and 1,375 character memory files instead of replacing them.
Sources
- Hindsight overview - operations and memory types
- vectorize-io/hindsight on GitHub - license, deployment options, MCP endpoint and providers
- The Consolidation Problem in Agent Memory - Hindsight's consolidation policy
- Hindsight Cloud billing - Cloud pricing
- Hermes Agent persistent memory docs - character limits and overflow behaviour
- Hermes Agent memory providers docs - external provider rules
- Hindsight integration guide for Hermes - setup and built-in memory mirroring
- Hermes Agent homepage - Nous Research's agent
Published October 5, 2026. Based on a TikTok by @6530307856653112320. Full video notes (markdown)