Back to Hermes Agent

Supermemory Memory Provider

plugins/memory/supermemory/README.md

2026.6.54.5 KB
Original Source

Supermemory Memory Provider

Semantic long-term memory with profile recall, semantic search, explicit memory tools, and full-session conversation ingest (one ingest per session) for richer profiles.

Requirements

Setup

bash
hermes memory setup    # select "supermemory"

Or manually:

bash
hermes config set memory.provider supermemory
echo 'SUPERMEMORY_API_KEY=***' >> ~/.hermes/.env

Config

Config file: $HERMES_HOME/supermemory.json

KeyDefaultDescription
container_taghermesContainer tag used for search and writes. Supports {identity} template for profile-scoped tags (e.g. hermes-{identity}hermes-coder).
auto_recalltrueInject relevant memory context before turns
auto_capturetrueStore cleaned user-assistant turns after each response
max_recall_results10Max recalled items to format into context
profile_frequency50Include profile facts on first turn and every N turns
capture_modeallSkip tiny or trivial turns by default
search_modehybridSearch mode: hybrid (profile + memories), memories (memories only), documents (documents only)
entity_contextbuilt-in defaultExtraction guidance passed to Supermemory
api_timeout5.0Timeout for SDK and ingest requests

Environment Variables

VariableDescription
SUPERMEMORY_API_KEYAPI key (required)
SUPERMEMORY_CONTAINER_TAGOverride container tag (takes priority over config file)

Tools

Kebab-case names are registered for the agent; snake_case aliases remain supported.

ToolAliasDescription
supermemory-savesupermemory_storeStore an explicit memory
supermemory-searchsupermemory_searchSearch memories by semantic similarity
supermemory-forgetsupermemory_forgetForget a memory by ID or best-match query
supermemory-profilesupermemory_profileRetrieve persistent profile and recent context

Source attribution

All Supermemory API calls send x-sm-source: hermes, and document writes stamp metadata.sm_source: hermes. This is a functional routing key, not telemetry: it groups Hermes-written memories into a dedicated "Hermes" Space in the Supermemory app, so you can filter, browse, and bulk-manage them per source agent (alongside Codex, Claude Code, etc.) from the Supermemory UI.

Behavior

When enabled, Hermes can:

  • prefetch relevant memory context before each turn
  • buffer the full conversation and ingest it as one session at session end (or on /reset, branch, compression, or shutdown)
  • ingest the full session to the conversations endpoint for richer profile/graph updates
  • expose explicit tools for search, store, forget, and profile access

The session is written once via the conversations endpoint, which drives Supermemory's entity extraction and profile building while keeping a clean, retrievable full transcript.

Profile-Scoped Containers

Use {identity} in the container_tag to scope memories per Hermes profile:

json
{
  "container_tag": "hermes-{identity}"
}

For a profile named coder, this resolves to hermes-coder. The default profile resolves to hermes-default. Without {identity}, all profiles share the same container.

Multi-Container Mode

For advanced setups (e.g. OpenClaw-style multi-workspace), you can enable custom container tags so the agent can read/write across multiple named containers:

json
{
  "container_tag": "hermes",
  "enable_custom_container_tags": true,
  "custom_containers": ["project-alpha", "project-beta", "shared-knowledge"],
  "custom_container_instructions": "Use project-alpha for coding tasks, project-beta for research, and shared-knowledge for team-wide facts."
}

When enabled:

  • supermemory-search, supermemory-save, supermemory-forget, and supermemory-profile accept an optional container_tag parameter
  • The tag must be in the whitelist: primary container + custom_containers
  • Automatic operations (turn sync, prefetch, memory write mirroring, session ingest) always use the primary container only
  • Custom container instructions are injected into the system prompt

Support