Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Session Storage

Session Storage Hermes Agent uses a SQLite database ( ) to persist session metadata, full message history, and model configuration across CLI and gateway sessio

Developer Guide
Section
Developer Guide
Source
hermesbible.com/docs/developer-guide/session-storage

Session Storage Hermes Agent uses a SQLite database ( ) to persist session metadata, full message history, and model configuration across CLI and gateway sessio

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. Architecture Overview
  2. SQLite Schema
  3. Sessions Table
  4. Messages Table
  5. FTS5 Full-Text Search
  6. Schema Version and Migrations
  7. Write Contention Handling
  8. Common Operations
  9. Initialize
  10. Create and Manage Sessions
  11. Store Messages
  12. Retrieve Messages
  13. Session Titles
  14. Full-Text Search

Section map

Architecture Overview

Maps architecture overview to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

SQLite Schema

Maps sqlite schema to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Sessions Table

Maps sessions table to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Messages Table

Maps messages table to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

FTS5 Full-Text Search

Maps fts5 full-text search to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Schema Version and Migrations

Maps schema version and migrations to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Write Contention Handling

Maps write contention handling to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Common Operations

Maps common operations to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Developer Guide 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: Architecture Overview, SQLite Schema, Sessions Table, Messages Table, FTS5 Full-Text Search. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: session, storage, sqlite, database, persist. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitDeveloper Guide documentation

Use when you need orientation for session storage before applying exact upstream commands.

Verify firstArchitecture Overview

Open the source anchor for Architecture Overview 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 Developer Guide, then open the linked source page for exact current syntax.
  2. Start with the source section for Architecture Overview; 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 SQLite Schema 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

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

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