All plugins

tam

Local-first long-term memory backed by total-agent-memory (TAM) over MCP — saves each completed turn (with a noise filter; TAM's quality gate applies), recalls relevant memories before each turn within a token budget, and adds tam_recall / tam_save tools; optional TAM team server for shared company memory. Disclosure — local mode starts the separately installed tam binary as a child process per session with an allowlisted environment that carries no credentials: Hermes provider keys (including HF_TOKEN and OLLAMA_API_KEY), TAM_API_TOKEN and any *_TOKEN / *_API_KEY / *_SECRET / *_PASSWORD variable are withheld, and of HF_* / OLLAMA_* only non-secret settings pass (OLLAMA_URL, OLLAMA_EMBED_MODEL, HF_HOME, HF_HUB_OFFLINE); it stores user/assistant turn text plus built-in memory additions (not tool output) in TAM's store, by default outside HERMES_HOME and shared with other agents using TAM; remote mode sends the same text to the user-configured URL with an optional TAM_API_TOKEN bearer token; hermes memory setup tam writes tam.json, TAM_API_TOKEN to .env and memory.provider in config.yaml.

vbcherepanov1Memoryv0.1.1Updated 1 month ago

About

Local-first long-term memory backed by total-agent-memory (TAM) over MCP — saves each completed turn (with a noise filter; TAM's quality gate applies), recalls relevant memories before each turn within a token budget, and adds tam_recall / tam_save tools; optional TAM team server for shared company memory. Disclosure — local mode starts the separately installed tam binary as a child process per session with an allowlisted environment that carries no credentials: Hermes provider keys (including HF_TOKEN and OLLAMA_API_KEY), TAM_API_TOKEN and any *_TOKEN / *_API_KEY / *_SECRET / *_PASSWORD variable are withheld, and of HF_* / OLLAMA_* only non-secret settings pass (OLLAMA_URL, OLLAMA_EMBED_MODEL, HF_HOME, HF_HUB_OFFLINE); it stores user/assistant turn text plus built-in memory additions (not tool output) in TAM's store, by default outside HERMES_HOME and shared with other agents using TAM; remote mode sends the same text to the user-configured URL with an optional TAM_API_TOKEN bearer token; hermes memory setup tam writes tam.json, TAM_API_TOKEN to .env and memory.provider in config.yaml.

tam — total-agent-memory for Hermes

Long-term memory for Hermes Agent backed by
total-agent-memory (TAM), over MCP.

  • Saves each completed turn (user message + final reply; no tool output) to TAM, skipping trivial
    prompts and very short exchanges. TAM's quality gate, when enabled, has the final say.
  • Before each turn, recalls relevant memories from TAM within a token budget.
  • Tools: tam_recall (search) and tam_save (store a durable fact, decision, solution, lesson or convention).
  • Shares one store with other agents on the same TAM (Claude Code, Codex CLI, Cursor, ...).

Local-first. By default Hermes starts your installed tam binary (MCP stdio), so data stays on
your machine. The spawned process gets a reduced environment with no credentials (no Hermes provider keys, no
*_TOKEN / *_API_KEY / *_SECRET variables). Remote mode connects
to a TAM HTTP endpoint or a TAM team server (URL + optional TAM_API_TOKEN) for shared team memory.

Quick start

pipx install total-agent-memory        # provides the `tam` command
hermes plugins install tam
hermes memory setup tam                # local/remote, command, data dir, project; tests the connection
hermes memory status

The plugin has no Python dependencies and never crashes Hermes: if TAM is missing or slow, the
recall for that turn is empty, saves are queued with retry, and shutdown waits a bounded time.

Configuration reference, privacy details and the team-server walkthrough:
https://github.com/vbcherepanov/hermes-tam-memory#readme

MIT © 2026 Vitalii Cherepanov

README from the reviewed commit 9a6e518; it updates when the author re-pins.

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section