Hermes Memory OS: cross-session memory for the Hermes Agent

Set up cross-session memory so that a question asked in a new session is answered by retrieval from existing memory rather than re-investigation with tools.

Hermes Intermediate Copied: 0
1 resource

Requirements

  • The repository provides a one-command installer for the complete stack.
  • Hermes Agent hook and plugin support is required.
  • Docker and Python 3.11 or newer are required.
  • Qdrant, Redis, ARQ worker, and the bundled SQLite databases.
  • An optional local LLM provider; the memory infrastructure is provider-agnostic.

How to use

This stack is substantially heavier than MEMORY.md, USER.md, and session search; use it when structured cross-session recall justifies Qdrant, Redis, workers, and durable storage.

Although storage is local-first, a hosted model provider may receive recalled context.

Review what automatic extraction stores because durable memory can retain sensitive or obsolete information.

Run the installer command below to set up the system.

curl -sSL https://raw.githubusercontent.com/ClaudioDrews/memory-os/main/setup.sh | bash

The installer brings up Qdrant, Redis, and the ARQ worker, initializes the SQLite stores, and installs the Hermes-side components. The repository also provides a manual installation guide and smoke tests for troubleshooting.

Hooks perform recall automatically; no special prompt is needed for every recall.

Verify recall by recording a concrete project decision, starting a new session, and asking the supplied question.

What decision did we make about this project's deployment, and why?

Source: aliaihub/awesome-hermes-usecases and its contributors. License: CC-BY-4.0. Source license notice.

Translation and editorial adaptation by ClawCases.

>Resources

>Related Use Cases

>More at this level: Intermediate