Persistent cross-session memory for Hermes Agent, powered by mem9.

Conversations are automatically extracted into facts, recalled semantically each turn, and available across sessions and agents.

• Hermes Agent installed and working (hermes version should print version info)
• An internet connection (the plugin talks to the mem9 REST API)

Review the script first if you prefer, then run:

curl -fsSL https://raw.githubusercontent.com/mem9-ai/mem9-hermes-plugin/main/install.sh | bash

This single command:

1. Installs the plugin via hermes plugins install
2. Creates a symlink at plugins/memory/mem9 inside the Hermes repo
3. Obtains an API key — reuses an existing MEM9_API_KEY (with a connectivity check), or creates a new one if none exists
4. Saves credentials to HERMES_HOME/.env and config to mem9.json
5. Activates memory.provider=mem9 (skipped if the connectivity check failed)

If activation succeeds, start a new Hermes session — mem9 is active. If the script reports a connectivity failure, run hermes memory setup to reconfigure.

# 1. Install the plugin files
hermes plugins install mem9-ai/mem9-hermes-plugin

# 2. Link into the Hermes memory provider directory
bash "${HERMES_HOME:-$HOME/.hermes}/plugins/mem9/scripts/link-memory-provider.sh"

# 3. Run the interactive setup (API key + activation)
hermes memory setup        # select "mem9" in the picker

During hermes memory setup you can auto-provision a free API key or enter an existing one. The setup flow tests the connection before saving.

hermes plugins update mem9

This runs git pull inside the installed plugin directory. Start a new Hermes session to pick up the changes. Your .env and mem9.json are not touched.

If the symlink is missing after an upgrade (e.g. Hermes was reinstalled), re-run:

bash "${HERMES_HOME:-$HOME/.hermes}/plugins/mem9/scripts/link-memory-provider.sh"

hermes memory status

You should see mem9 listed as the active memory provider.

All files live under ${HERMES_HOME:-$HOME/.hermes}/.

.env — credentials and optional overrides (env vars take precedence over mem9.json):

mem9.json — provider config:

# Remove the symlink and plugin files
rm -f "$(hermes version 2>/dev/null | awk '/Project:/{print $2}')/plugins/memory/mem9"
hermes plugins remove mem9

# Switch to another provider or disable memory
hermes config set memory.provider ""