explaingit

yelixir-dev/hermes-memory-stack

★ 12ShellAudience · developerComplexity · 3/5ActiveSetup · moderate

TLDR

Shell installer that layers optional memory, knowledge, and skill components on top of an existing Hermes Agent install, with profiles for minimal, API-free, and full setups.

Mindmap

mindmap
  root((hermes-memory-stack))
    Inputs
      Existing Hermes Agent install
      Local .env secrets
      User profile choice
    Outputs
      Skills layer
      llmwiki knowledge
      Hindsight routing config
      Optional NotebookLM sync
    Use Cases
      Add memory to Hermes
      API free local setup
      Guided wizard install
    Tech Stack
      Shell
      Bash
      curl
      OpenAI compatible API

Things people build with this

USE CASE 1

Add a local memory and knowledge layer to an existing Hermes Agent install

USE CASE 2

Set up an API free Hermes profile with llmwiki in markdown mode for offline use

USE CASE 3

Route Hermes through an OpenAI compatible endpoint using Hindsight environment variables

USE CASE 4

Bundle public documentation as NotebookLM sources on a refresh schedule via the optional source pack builder

Tech stack

ShellBashcurl

Getting it running

Difficulty · moderate Time to first run · 30min

Requires a working Hermes Agent install first; some layers depend on a local OAuth bearer token or OpenAI compatible endpoint configured in .env.

In plain English

Hermes Memory Stack is an optional add-on for an existing tool called Hermes Agent. The repository's installer layers in extra memory, knowledge, and skill components onto a fresh Hermes setup. The project insists that none of these components ship with API keys, OAuth tokens, Google cookies, or personal data; user secrets stay in a local .env file under the user's home directory. The installer is run with ./install.sh after cloning, or as a one-shot curl | bash line. It asks the user which layers to enable. The options listed in the README include reusable skills for memory-stack workflows, the Axiom Perception cache for repeated UI tasks, an llmwiki knowledge layer in several modes, Hindsight routing helpers for durable memory, an optional NotebookLM workspace, and an optional semble_rs code and log helper. Three install profiles are offered. Minimal adds only the skills and Axiom. API-free adds llmwiki in markdown mode and optional semble_rs, with no external network calls. Full is a guided wizard that lets the user pick everything piece by piece, including NotebookLM and the auxiliary model routing template. NotebookLM is off by default. If turned on, the installer adds a CLI and prints manual login steps. After login, a sync job can write a compact list of notebook names, IDs, source titles, and short summaries to a routing file under the user's wiki folder. A second opt-in path installs a source-pack builder from a separate GitHub repository, which can bundle public documentation as NotebookLM sources on a refresh schedule. For memory routing, the installer can keep the existing Hermes provider, ask whether Hindsight should reuse a local GPT OAuth bearer token, point Hindsight at any OpenAI-compatible endpoint via environment variables, or skip the routing change entirely. The Hermes config file is copied as a backup before any patching.

Copy-paste prompts

Prompt 1
Walk me through running install.sh for hermes-memory-stack on a fresh Hermes Agent install using the API free profile.
Prompt 2
Show me which environment variables hermes-memory-stack reads from ~/.env so I can wire up an OpenAI compatible endpoint via Hindsight.
Prompt 3
Explain the difference between the minimal, API free, and full install profiles in hermes-memory-stack and which one fits a local only laptop setup.
Prompt 4
Help me enable the NotebookLM sync in hermes-memory-stack and route notebook IDs and summaries into the wiki folder.
Prompt 5
Show me how hermes-memory-stack patches the Hermes config file and how to roll back to the backup if I want to remove the stack.
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.