Add Perseus Vault integration#538
Conversation
|
@tcconnally is attempting to deploy a commit to the deepset Team on Vercel. A member of the Team first needs to authorize it. |
|
Friendly nudge on this one 🙂 — catalog metadata + logo are in place and the package ( |
There was a problem hiding this comment.
Pull request overview
- Adds a new Haystack integration catalog page and logo for Perseus Vault (community “Memory Store” integration) so it can be listed and documented alongside other integrations.
Changes:
- Adds
integrations/perseus-vault-haystack.mdintegration page with metadata, overview, install instructions, usage snippet, and license. - Adds
logos/perseus-vault.svglogo asset referenced by the integration page.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
integrations/perseus-vault-haystack.md |
New integration catalog entry + usage snippet + license section. |
logos/perseus-vault.svg |
New SVG logo used by the integration page. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| from haystack import Pipeline, Document | ||
| from perseus_vault_haystack import ( | ||
| PerseusVaultMemoryStore, | ||
| PerseusVaultMemoryWriter, | ||
| PerseusVaultMemoryRetriever, | ||
| ) | ||
|
|
||
| store = PerseusVaultMemoryStore(db_path="~/.mimir/haystack.db") |
There was a problem hiding this comment.
Good catch — applied in 7964de5. The snippet now uses Path(...).expanduser() and creates the parent dir so it is copy/paste runnable.
|
Thanks for the review @kacperlukawski! Addressed the Copilot note in 7964de5 — the usage example now expands |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
… page The install section omitted the separate perseus-vault engine binary that the components drive over stdio, so pip-install-only readers hit a RuntimeError. Documented the releases-page download / $PATH step and swapped the usage snippet for a write+read that returns an actual hit (verified against perseus-vault-haystack 0.1.0 and perseus-vault v2.20.2).
|
Pushed one more polish commit (484f217) to make the page fully self-contained:
Verified end-to-end against |
Brings the catalog entry to parity with the other Memory Store integrations: Available Classes, a Haystack Agent example (retain/recall/reflect tools), an automatic-memory wrapper example, and the pipeline example. Overview now leads with the differentiators (local-first, encrypted at rest, no cloud, no API keys). All referenced symbols ship in perseus-vault-haystack 0.2.0 on PyPI.
|
Expanded the page to match the depth of the other Memory Store entries (2368c93):
Every symbol referenced on the page ships in 0.2.0, and the pipeline example is verified to run end-to-end. Thanks again for the review! 🙏 |
The repo was renamed from mimir-haystack; use the canonical slug so links don't rely on GitHub redirects.
This PR adds a catalog entry for Perseus Vault, a community Haystack 2.x integration providing local-first, encrypted, persistent memory for pipelines and agents.
Perseus Vault is a single-binary memory engine backed by an encrypted (AES-256-GCM) SQLite database with FTS5 + vector search that runs fully offline — no external vector DB or API keys required. The integration exposes
PerseusVaultMemoryStore,PerseusVaultMemoryWriter, andPerseusVaultMemoryRetriever.Adds a metadata file (
integrations/perseus-vault-haystack.md) and an SVG logo (logos/perseus-vault.svg). Bothpypiandrepofields are populated.