hermes - 💡(How to fix) Fix [Show & Tell] hermes-memory-pgvector v0.3 — drop-in Postgres + pgvector memory provider plugin

Hey 👋 — sharing a memory-provider plugin that may be useful to folks running hermes-agent (and the desktop / workspace clients on top of it).

hermes-memory-pgvector v0.3 — drop-in Postgres + pgvector memory provider for hermes-agent. Stores hermes-agent's built-in memory(action='add', ...) writes into Postgres + pgvector with HNSW, and adds one recall_memory(query, scope, target, limit) tool for semantic search. No new ontology for the agent to learn, no LLM in the write path.

Key feature for multi-agent setups: per-agent themes via X-Hermes-Session-Key header, so your separate minions (marketing / trading / sre / etc.) don't pollute each other's recall by default — and you can still scope='all' for cross-theme search.

Ships as a standalone plugin per hermes-agent's CONTRIBUTING.md (in-tree memory-provider directory is closed; new providers install into ~/.hermes/plugins/).

• 📦 PyPI: https://pypi.org/project/hermes-memory-pgvector/
• 🐙 Repo: https://github.com/andreab67/hermes-memory-pgvector
• 💬 Full write-up + discussion: https://github.com/andreab67/hermes-memory-pgvector/discussions/1

Install:

pip install hermes-memory-pgvector
# then drop into ~/.hermes/plugins/pgvector/ and set memory.provider=pgvector

BSD-3-Clause. Tested live on a 7-minion ops stack. Feedback / issues welcome on the standalone repo.

— Happy to delete or convert this Issue if it's not the right channel; I checked and Discussions are off here, otherwise I'd have posted there. 🙏