We've opened a pull request to add Perseus Vault as a persistent, cross-session memory backend for CrewAI agents — local SQLite, confidence decay, and no external embedding service. It's in active review with the maintainers; here's what it does and exactly where it stands.
CrewAI agents are powerful but stateless between runs. This integration lets a crew remember decisions and patterns — and share them across crews — without standing up any external service.
Agents retain decisions, facts, and context across separate runs and deployments — via the standard MCP interface to the Perseus Vault binary.
Point multiple crews at the same perseus-vault.db. Knowledge learned by one crew is recallable by the next — scoped by agent and category.
Facts fade if unreinforced, so memory stays current instead of accumulating stale state.
Local SQLite + FTS5. No external APIs, no embedding models, no cloud — memory never leaves your machine.
search() signature to the storage-backend protocol). We'll mark this shipped here only once it merges.