Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Persistent Memory

Hermes Agent has bounded, curated memory that persists across sessions. This lets it remember your preferences, your projects, your environment, and things it h

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/memory

Hermes Agent has bounded, curated memory that persists across sessions. This lets it remember your preferences, your projects, your environment, and things it h

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. How It Works
  2. How Memory Appears in the System Prompt
  3. Memory Tool Actions
  4. Substring Matching
  5. Two Targets Explained
  6. memory — Agent's Personal Notes
  7. user — User Profile
  8. What to Save vs Skip
  9. Save These (Proactively)
  10. Skip These
  11. Capacity Management
  12. What Happens When Memory is Full
  13. Practical Examples of Good Memory Entries
  14. Duplicate Prevention

Section map

How It Works

Maps how it works to the Core Features documentation path, with the source page reserved for exact commands and updates.

How Memory Appears in the System Prompt

Maps how memory appears in the system prompt to the Core Features documentation path, with the source page reserved for exact commands and updates.

Memory Tool Actions

Maps memory tool actions to the Core Features documentation path, with the source page reserved for exact commands and updates.

Substring Matching

Maps substring matching to the Core Features documentation path, with the source page reserved for exact commands and updates.

Two Targets Explained

Maps two targets explained to the Core Features documentation path, with the source page reserved for exact commands and updates.

memory — Agent's Personal Notes

Maps memory — agent's personal notes to the Core Features documentation path, with the source page reserved for exact commands and updates.

user — User Profile

Maps user — user profile to the Core Features documentation path, with the source page reserved for exact commands and updates.

What to Save vs Skip

Maps what to save vs skip to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: How It Works, How Memory Appears in the System Prompt, Memory Tool Actions, Substring Matching, Two Targets Explained. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: persistent, memory, bounded, curated, persists. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for persistent memory before applying exact upstream commands.

Verify firstHow It Works

Open the source anchor for How It Works and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for How It Works; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for How Memory Appears in the System Prompt if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page