Views
No views yet
Read-only mirror ofSibyl-Labs/Sibyl-Memory. The canonical source is on GitHub. Install from PyPI:pip install -U sibyl-memory-cli· Docs: https://docs.sibyllabs.org/memory/ · Product: https://sibyllabs.org/plugin · Benchmarks: https://blog.sibylcap.com/beta-analysis
███████╗██╗██████╗ ██╗ ██╗██╗
██╔════╝██║██╔══██╗╚██╗ ██╔╝██║
███████╗██║██████╔╝ ╚████╔╝ ██║
╚════██║██║██╔══██╗ ╚██╔╝ ██║
███████║██║██████╔╝ ██║ ███████╗
╚══════╝╚═╝╚═════╝ ╚═╝ ╚══════╝
M E M O R Y
sibyl-memory-client is a local-first agentic memory SDK. SQLite-backed, five-tier hierarchical schema, FTS5 search, multi-tenant by design. No vector database. No embedding model. No external retrieval service. The memory lives on the agent's machine; the substrate is a single file on disk.Privacy disclosure. Your memory content never leaves the machine. The only outbound network call is tier verification: when an activated account writes past its tier cap, the client callsapi.sibyllabs.org/api/plugin/check-writewith account metadata only (account id, session token, and the database's byte size and proposed delta) — never the contents of your memory. Verified against the source insibyl-memory-client/src/sibyl_memory_client/_capcheck.py. Free, unactivated use makes no network calls at all.
sibyl-memory-cli for activation and tier management, sibyl-memory-hermes for Hermes Agent integration, sibyl-memory-mcp for any MCP-compatible client (Claude Code, Codex, Cursor, Continue), and sibyl-memory-langgraph as a LangGraph BaseStore adapter.| Package | PyPI | Description |
|---|---|---|
sibyl-memory-client |  | Local-first agentic memory SDK. SQLite-backed five-tier hierarchical schema, FTS5 search, multi-tenant, with self-learning skill detection and local memory linter. Foundation of the plugin family. |
sibyl-memory-cli |  | Command-line interface. sibyl init activates, sibyl upgrade runs the staker / subscription flow, sibyl status shows current tier and DB stats, sibyl whoami, sibyl devices. |
sibyl-memory-hermes |  | Bundled memory payload for Hermes Agent v0.13+ (and any other Python orchestration that wants direct SDK access). |
sibyl-memory-mcp |  | MCP server. Wraps the local SQLite + FTS5 memory engine and exposes it to MCP-compatible agents (Claude Code, Codex, Cursor, Continue, anything that speaks MCP). |
sibyl-memory-langgraph |  | LangGraph BaseStore adapter. Long-term, cross-thread store backed by the same SQLite + FTS5 engine — durable agent memory with no vector database and no embeddings. |
1pip install sibyl-memory-cli
2sibyl initsibyl init opens a browser to activate your account, binds your wallet or email, and writes credentials to ~/.sibyl-memory/credentials.json. Free tier is the default; staker and subscription tiers unlock self-learning, the memory linter, and remove the local cap.pip install sibyl-memory-client1pip install sibyl-memory-hermes
2sibyl-memory-hermes install-plugin
3# then edit ~/.hermes/config.yaml:
4# memory:
5# provider: sibyl1pip install sibyl-memory-mcp
2# then point your MCP client at the server entry point.┌─────────────────────────────────────────────────────────┐
│ sibyl-memory-cli sibyl-memory-mcp │
│ ┌──────────────┐ ┌──────────────┐ │
│ │ sibyl init │ │ MCP server │ │
│ │ sibyl status │ │ (stdio) │ │
│ │ sibyl whoami │ └──────┬───────┘ │
│ └──────┬───────┘ │ │
│ └────────────┬─────────────────┘ │
│ sibyl-memory-hermes │ sibyl-memory-langgraph │
│ ┌──────────────┐ │ ┌────────────────┐ │
│ │ Hermes hook │ │ │ LangGraph │ │
│ └──────┬───────┘ │ │ BaseStore │ │
│ │ │ └───────┬────────┘ │
│ │ │ │ │
│ │ │ │ │
│ └────────────┼─────────────┘ │
│ ▼ │
│ sibyl-memory-client (SDK) │
│ ┌────────────────────────┐ │
│ │ SQLite + FTS5 │ │
│ │ 5-tier schema │ │
│ │ self-learning skills │ │
│ │ multi-tenant │ │
│ └────────────────────────┘ │
└─────────────────────────────────────────────────────────┘README.md and CHANGELOG.md for the detail. HOT state/ live working state, rewritten in place
WARM entities/ single source of truth per (category, name)
COLD journal/ append-only event log
REFERENCE reference/ static knowledge, rarely changes
ARCHIVE archive/ retired entities, kept for auditUNIQUE (tenant_id, category, name) constraint, not just a convention in the application code. Drift is impossible by construction.@tradingtulips). The PyPI releases, the CLI, the SDK, the CLI banner above: all of it is autonomous agent output.