Skip to main content

rushdb-hermes-memory

Native RushDB persistent memory for Hermes Agent.

The provider recalls scope-authorized historical context before inference, captures completed turns without blocking the response, and uses a profile-local durable outbox so acknowledged events survive process restarts.

Requirements

  • Python 3.11–3.13
  • Hermes Agent with memory-provider entry-point support
  • A RushDB project API key from app.rushdb.com, or a standalone RushDB engine and an embedding provider (see below)

Install

Install the provider into the same Python environment as Hermes Agent:

pip install rushdb-hermes-memory
hermes memory setup

Set the RushDB project key in the Hermes environment:

export RUSHDB_API_KEY="your-project-api-key"

Optional environment variables:

  • RUSHDB_API_URL selects a different RushDB Cloud API endpoint. To self-host, run the RushDB engine and use the settings below.
  • RUSHDB_MEMORY_SCOPE_SALT makes participant hashes deployment-specific.

A standalone RushDB engine

Recall is a vector search. RushDB Cloud embeds memories for you; a standalone engine (rushdb) does not, so the provider embeds them itself through an OpenAI-compatible embeddings endpoint:

export RUSHDB_ENGINE_URL="http://127.0.0.1:3000"
export RUSHDB_ENGINE_TOKEN="your-engine-token"
# export RUSHDB_ENGINE_SCOPE="tenant-1"   # only for an engine started with --multitenant
export RUSHDB_EMBEDDING_API_KEY="sk-..."
export RUSHDB_EMBEDDING_MODEL="text-embedding-3-small"
export RUSHDB_EMBEDDING_DIMENSIONS="1536"
# export RUSHDB_EMBEDDING_BASE_URL="https://api.openai.com/v1"

On start the provider creates the external vector indexes it needs; every memory is written with its vector and recall searches with the embedded query. With RushDB Cloud the embedding settings are optional. When the configuration is incomplete, hermes memory status reports what is missing.

Hermes discovers the rushdb provider through the hermes_agent.memory_providers Python entry-point group.

Behavior

  • Recall searches EPISODE.summary and active MEMORY_FACT.text records with mandatory agent, profile, privacy, participant, and sandbox scope filters.
  • Recall has a short fail-open timeout and falls back to bounded recent in-process episodes.
  • Successful primary-agent turns are captured asynchronously as canonical EPISODE records.
  • Explicit Hermes memory add and replace operations are mirrored as active MEMORY_FACT records.
  • A replace (or a patch, which Hermes mirrors as a replace) deactivates the fact holding the entry it replaced and records its id in supersedesFactId; a remove deactivates the removed entry's fact. Both set validUntil and keep the old fact for history. The entry is matched by the exact previous_content Hermes reports, within the same scope and target; Hermes versions that don't report it keep the earlier fact active.
  • Writes first enter an atomic local outbox under $HERMES_HOME/rushdb-memory/outbox, then use deterministic IDs and idempotent RushDB upserts.
  • Surviving outbox files are retried while the process is running and replayed after restart.

Privacy and trust

The provider uploads bounded user and assistant text from completed primary-agent turns. It does not automatically upload Hermes' complete messages payload, system prompts, tool calls, command output, or local file paths. Subagents do not write memory.

Recalled records are formatted as untrusted historical context, never as instructions or policy. Participant identifiers are stored as hashes rather than raw platform IDs.

Development

uv sync --locked --group dev
uv run ruff format --check .
uv run ruff check .
uv run pytest
uv build

Release

CI verifies pull requests and every push to main. A successful main build publishes the version in pyproject.toml to PyPI when that exact version is not already present. Configure the pypi GitHub environment and its PYPI_TOKEN secret. Bump version before merging a subsequent release.

License

Apache-2.0

Metadata

Release files for rushdb-hermes-memory 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rushdb-hermes-memory 0.2.1
File Size Uploaded Provenance Actions
rushdb_hermes_memory-0.2.1.tar.gz 25.7 kB With provenance Details for rushdb_hermes_memory-0.2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for rushdb-hermes-memory 0.2.1
File Interpreter ABI Platform Actions
rushdb_hermes_memory-0.2.1-py3-none-any.whl Python 3 none any Details for rushdb_hermes_memory-0.2.1-py3-none-any.whl

Total release size: 44.6 kB

Release files / rushdb_hermes_memory-0.2.1.tar.gz

Download URL rushdb_hermes_memory-0.2.1.tar.gz
Size 25.7 kB
Tags Source
SHA-256 checksum
How to use checksums
9c7948c53b04662a12163e8a845990e862dc079520669c4cf48f9f33b75d3da1
BLAKE2b-256 checksum
How to use checksums
f31d92a2240b07da616e9942485cb47b162e1c53a944b31d57caccf95b41c04b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

Release files / rushdb_hermes_memory-0.2.1-py3-none-any.whl

Download URL rushdb_hermes_memory-0.2.1-py3-none-any.whl
Size 18.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
568af68c746d1318ebdcd449f983dd022104e2d7dd96e96b350cebcf592d6e1b
BLAKE2b-256 checksum
How to use checksums
1e06c15e275d8b6c6b47d3a8c45599584f7b92b555bbd6dbfd40a6b465e1ed8b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

Security for rushdb-hermes-memory 0.2.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for rushdb_hermes_memory-0.2.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page