[CahidArda]

Resolves the rest of DX-3182. Brings the Hermes Agent memory provider from #76 to main.

Why this PR

#76 was stacked on #75. #75 was squash-merged into main, and #76 was merged 91 seconds later into #75's branch, which by then was already merged. So the provider never reached main, which still has only the scaffold.

What's in it

• b702d2f: Hermes Agent memory provider on Upstash Redis (DX-3182) #76's squash commit, cherry-picked onto main. Its tree is identical to what Hermes Agent memory provider on Upstash Redis (DX-3182) #76 merged; Support Python packages in the monorepo (DX-3182) #75's final tree equalled main, so it applied without conflicts. The code and its review history are in Hermes Agent memory provider on Upstash Redis (DX-3182) #76.
• 17ee9cc: one e2e fix. The control session now gets its own HERMES_HOME. Hermes's built-in session_search reads every session in state.db, whoever it belonged to, so in a shared home the control user could find sessions 1 and 2 there. That happened once in a local run, even though the provider's Redis searches returned nothing for that user.
• The upstash-hermes-memory: minor changeset from Hermes Agent memory provider on Upstash Redis (DX-3182) #76, so merging this opens a Version Packages PR that bumps the package to 0.1.0.

Tested on this branch

• pnpm py:lint and node scripts/sync-version.mjs --check pass.
• 46 pytest tests pass against the test Redis.
• python/hermes-memory/e2e/hermes_e2e.py passes in a real Hermes (v0.20.2, gpt-5-mini):
  • session 2 recalls the facts with no tool calls;
  • the control user's Upstash searches return nothing;
  • the transcripts are searchable;
  • the TS SDK recalls the memory Hermes saved.

Still open from #76's review (not in this PR)

• If a user id with : is refused, initialize() has already created the stores, so the provider stays active as user default.
• /undo keeps an undone turn when the user message and the reply both repeat exactly.

Before the release

The PyPI pending trusted publisher for upstash-hermes-memory must exist before the Version Packages PR is merged: owner upstash, repo agentkit, workflow release.yml, no environment.

[linear-code]

DX-3182

[Copilot]

🟡 Changes recommended

An explicit zero TTL leaves transcripts stored indefinitely, and forgetting reports success before the search index reflects deletion, allowing removed memories to remain retrievable.

2 open issues

• Treat ttl_seconds=0 as immediate expiration · New
• Wait for search index after forgetting memory · New

What changed in this PR

Brings the Hermes memory provider from #76 onto main, replacing the Python scaffold with Redis-backed memory and chat history shared with the TypeScript SDK.

Changes:

• Adds Python memory primitives and a Hermes provider for automatic recall, transcript storage, and memory tools.
• Adds contract, lifecycle, packaging, and end-to-end checks, with an isolated home for the control user.
• Documents setup and queues the first 0.1.0 release through Changesets.

File	Description
README.md	Replaces scaffold status with the provider’s capabilities.
python/​hermes-memory/​tests/​test_redis.py	Tests live Redis operations and shared data compatibility.
python/​hermes-memory/​tests/​test_provider.py	Tests provider tools, lifecycle, isolation, and transcript rewind.
python/​hermes-memory/​tests/​test_package.py	Checks public exports, registration, and wheel contents.
python/​hermes-memory/​tests/​test_layout.py	Checks Redis layout compatibility and telemetry.
python/​hermes-memory/​tests/​conftest.py	Adds unique test prefixes and key cleanup.
python/​hermes-memory/​src/​upstash_hermes_memory/​provider.py	Implements Hermes recall, tools, and transcript lifecycle.
python/​hermes-memory/​src/​upstash_hermes_memory/​memory.py	Adds the Python AgentMemory implementation.
python/​hermes-memory/​src/​upstash_hermes_memory/​chat_history.py	Adds transcript storage and search.
python/​hermes-memory/​src/​upstash_hermes_memory/​_telemetry.py	Adds the package’s Redis telemetry tag.
python/​hermes-memory/​src/​upstash_hermes_memory/​_search.py	Handles search index provisioning and recovery.
python/​hermes-memory/​src/​upstash_hermes_memory/​__init__.py	Exports primitives and registers the provider.
python/​hermes-memory/​README.md	Documents setup, storage layout, and verification.
python/​hermes-memory/​pyproject.toml	Declares the Hermes discovery entry point.
python/​hermes-memory/​e2e/​hermes_e2e.py	Checks real Hermes recall, isolation, and SDK interoperability.
CLAUDE.md	Updates provider documentation and testing guidance.
.changeset/​hermes-memory-provider.md	Queues the initial minor release.

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Python’s save logic preserves an existing title when passed an explicit empty string, preventing callers from clearing it and diverging from TypeScript behavior.

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Treat an empty title as an explicit request to clear it

python/​hermes-memory/​src/​upstash_hermes_memory/​chat_history.py:117

Passing title="" after a titled save preserves the old title here, whereas TypeScript ChatHistory.saveChat treats an explicitly empty title as clearing it (packages/sdk/src/chat-history.ts:225). A Python caller therefore cannot clear an existing title and writes a different document for the same operation. Fall back to the existing title only when title is None.

2 resolved since last review

• Wait for search index after forgetting memory
• Treat ttl_seconds=0 as immediate expiration

_{Review effort: Balanced}