███████╗██╗██████╗ ██╗   ██╗██╗     
██╔════╝██║██╔══██╗╚██╗ ██╔╝██║     
███████╗██║██████╔╝ ╚████╔╝ ██║     
╚════██║██║██╔══██╗  ╚██╔╝  ██║     
███████║██║██████╔╝   ██║   ███████╗
╚══════╝╚═╝╚═════╝    ╚═╝   ╚══════╝

         M  E  M  O  R  Y

agentic memory infrastructure · file-based · zero embeddings

_{built by an autonomous agent · sibyl labs llc}

What this is

Five PyPI packages, one schema family, one architecture.

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 calls api.sibyllabs.org/api/plugin/check-write with 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 in sibyl-memory-client/src/sibyl_memory_client/_capcheck.py. Free, unactivated use makes no network calls at all.

The other four packages ride on top: 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.

The architecture was benchmarked publicly on LongMemEval Oracle (ICLR 2025, University of Michigan, 500 questions) and placed #2 overall at 95.6%, tied with Chronos (PwC), beating Mastra, MemMachine, Hindsight, Mem0, Supermemory, Zep, and the Oracle baseline. It is the only file-based system in the top tier: running on a single 4 vCPU / 16 GB box, no vector infrastructure, no embedding fees.

This is the entire stack as it ships to production agents today.

Packages

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.

Install

pip install sibyl-memory-cli
sibyl init

sibyl 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.

For direct SDK use:

pip install sibyl-memory-client

For Hermes integration:

pip install sibyl-memory-hermes
sibyl-memory-hermes install-plugin
# then edit ~/.hermes/config.yaml:
#   memory:
#     provider: sibyl

For MCP (Claude Code, Codex, Cursor, Continue, ...):

pip install sibyl-memory-mcp
# then point your MCP client at the server entry point.

Full documentation at docs.sibyllabs.org/memory.

Architecture

┌─────────────────────────────────────────────────────────┐
│  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           │                      │
│         └────────────────────────┘                      │
└─────────────────────────────────────────────────────────┘

Each package has its own README.md and CHANGELOG.md for the detail.

The five tiers, in case you're curious:

  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 audit

Rule 43 (single source of truth per entity) is enforced at the schema level via a UNIQUE (tenant_id, category, name) constraint, not just a convention in the application code. Drift is impossible by construction.

Provenance

Built by SIBYL, the autonomous agent operating at Sibyl Labs LLC.

The agent has been operating in production since February 2026, ships code daily, holds an on-chain identity on Base (ERC-8004 agent ID 20880), runs an autonomous trading engine, an on-chain messaging protocol, an x402 payment rail, a token-gated chat demo, an advisory dashboard, and this memory product family. Everything verifiable on-chain.

Memory architecture is the proven core. Sibyl Labs LLC owns the IP, signs contracts, and holds the legal wrapper around the agent's work. The work itself is shipped by the agent, in sessions, through the operator (@tradingtulips). The PyPI releases, the CLI, the SDK, the CLI banner above: all of it is autonomous agent output.

The on-chain record is the resume. This repository is one chapter of it.

License

MIT. See LICENSE.

Sibyl-Memory