Hermes Memory Enhancer can store and retrieve long-lived agent memory. This repository is only the Hermes plugin/integration layer; it is not the Memory Enhancer server repository and its security notes do not replace server-side threat modeling, authentication, TLS termination, database hardening, or deployment hardening. Treat the separately deployed Memory Enhancer server and database as sensitive infrastructure.

This repository is client-side Hermes plugin documentation and code only. It is not sufficient documentation for operating a production Memory Enhancer server.

A server repository should separately document at least:

• authentication and authorization model
• TLS/proxy deployment
• database location, permissions, backup, retention, and deletion
• network exposure and rate limiting
• tenant isolation, if multi-user
• audit logging and incident response
• handling of PHI/PII, secrets, and regulated data

The plugin is designed to fail closed for high-risk operations:

• Non-loopback remote endpoints must use HTTPS unless MEMORY_ENHANCER_ALLOW_INSECURE_REMOTE=true is explicitly set.
• Non-loopback remote endpoints require MEMORY_ENHANCER_API_KEY unless MEMORY_ENHANCER_ALLOW_UNAUTHENTICATED_REMOTE=true is explicitly set.
• memory_enhancer_add_resource is disabled unless MEMORY_ENHANCER_ENABLE_ADD_RESOURCE=true is explicitly set.
• Local file and directory ingestion requires MEMORY_ENHANCER_ALLOWED_UPLOAD_ROOTS.
• Obvious credential patterns are redacted from sync payloads and tool outputs when MEMORY_ENHANCER_REDACT_SECRETS=true (default).
• Automatic prefetch and synced message payloads are length-bounded.

• Prefer a loopback endpoint for single-user local deployments:

MEMORY_ENHANCER_ENDPOINT=http://127.0.0.1:1933

• For remote deployment, use HTTPS and an API key:

MEMORY_ENHANCER_ENDPOINT=https://memory.example.com
MEMORY_ENHANCER_API_KEY=replace-with-a-strong-secret

• Do not expose the Memory Enhancer server directly to the public internet without authentication, TLS, rate limiting, and normal web-service hardening.
• Store .env files and SQLite databases outside Git.
• Back up the SQLite database if it contains valuable memory.
• Do not store passwords, API keys, private keys, raw PHI/PII, or regulated data unless your own policy, consent, access controls, and retention rules allow it.

memory_enhancer_add_resource can ingest URLs, local files, or directories into long-term memory. Enable it only when you understand the data boundary.

If enabled for local uploads, restrict roots narrowly:

MEMORY_ENHANCER_ENABLE_ADD_RESOURCE=true
MEMORY_ENHANCER_ALLOWED_UPLOAD_ROOTS=/home/user/project-notes:/home/user/public-docs

Do not allow broad roots such as:

/
/home
/home/user
~

The plugin blocks common sensitive filenames such as .env, private keys, token files, and credential files, but this is a safety net, not a data-loss-prevention system.

Secret redaction is best-effort. It reduces accidental leakage of obvious credentials but cannot guarantee removal of every private value, medical datum, legal datum, or proprietary string.

Users remain responsible for deciding what may be sent to the Memory Enhancer server and stored in its database.

Please report vulnerabilities through GitHub Issues if no private channel is available. Do not include real secrets, private memory databases, or sensitive user data in public reports.