Your AI forgets everything between conversations. Sibyl gives it a memory that sticks: it remembers your work and picks up where you left off, every time. Three commands, about two minutes.
In your terminal:
Installs everything in one go. Hit an "externally managed environment" error? Quick fix in If something didn't work at the bottom.
Opens a sign-in link in your browser:
Sign in there — connect a wallet, or use your email and a code — and the terminal picks it up on its own.
Finds your AI app and connects Sibyl to it — no config editing:
Restart your AI app afterward. Connected nothing, or you use a different one? See If something didn't work.
Open your AI and tell it something worth remembering, like "remember that I like short, direct answers." Close it, open it again later, and ask "how do I like my answers?" It'll know. That's the whole thing: your AI remembers now, and keeps remembering — across every conversation.
The beta is still moving. Check what's outdated:
Or upgrade in-place:
update tracks the CLI, client, and Hermes adapter. If you wired Claude Code or Codex, bump the MCP server too: pip install -U sibyl-memory-mcp.
You won't need most of these — the three steps above are the whole setup. They're here for when you want them.
sibyl command| Command | What it does |
|---|---|
| sibyl init | Activate the plugin in your browser. Writes credentials to ~/.sibyl-memory/. |
| sibyl migrate | Guided onboarding: back up existing memory/agent files, wire Sibyl into every harness, populate Sibyl Memory from the backup, optionally slim the originals. |
| sibyl status | Local + server tier, DB size, schema version, account ID. Now lists every memory store on the machine and warns if they've split-brained. |
| sibyl memory list [category] | Read-only: list stored entities, optionally by category. |
| sibyl memory search <query> | Read-only: full-text search across every tier. Matches stored text, not meaning. |
| sibyl memory recall <cat> <name> | Read-only: recall one entity by category + name. |
| sibyl whoami | One-line account summary. Add --full to unmask email + wallet. |
| sibyl health | Provider self-check. Verifies DB, schema, FTS5, server reachability. |
| sibyl upgrade | Open the tier upgrade flow (stake or subscribe). |
| sibyl update | Check installed packages against PyPI. Exit 0 current / 2 outdated. |
| sibyl update --apply | Run pip install -U for outdated packages in place. |
| sibyl devices | List active devices (bearer tokens) bound to this account. |
| sibyl devices revoke <i> | Revoke a device by its index from sibyl devices. |
| sibyl setup | Auto-detect Hermes / Claude Code / Codex and wire SIBYL as the memory provider. |
| sibyl setup hermes | Wire just Hermes Agent. |
| sibyl setup claude-code | Wire just Claude Code via claude mcp add --scope user (absolute path, connects first try). |
| sibyl setup codex | Wire just Codex. Writes [mcp_servers.sibyl_memory] to ~/.codex/config.toml (atomic, .bak backup). |
| sibyl dashboard | Open the account dashboard. Delegates to status until account.sibyllabs.org ships. |
| sibyl logout | Remove local credentials. Your memory.db stays. |
Your agent already has memory scattered across flat files. The easiest path is one
command: sibyl migrate backs up every memory/agent file it finds, wires
Sibyl into every harness it detects, hands the extraction to your own agent, verifies
what landed, and (only if you confirm) slims the originals. Your live data is never
touched until that final, optional, confirmed step.
sibyl migrate copies your existing memory and agent files to a timestamped backup and works from that copy, leaving your live files unmodified until an explicit, confirmed trim. This is beta software: keep your own backup and verify the migration before you rely on it. Sibyl Labs is not responsible for any loss of data.
Get the current sibyl-memory-cli first: pip install -U sibyl-memory-cli, or sibyl update --apply if you already have it. Run it from the project whose memory you want to migrate.
It prints the extraction prompt for you to run in your agent (it reads the backup and writes via the sibyl-memory tool. The extraction runs locally; Sibyl Labs never sees your files). Flags: --no-debloat to skip the trim, --backup-dir PATH to choose where the backup goes.
The three steps work for almost everyone. If one of them didn't, the fix is here.
Some systems require a virtual environment. These two lines make one and install Sibyl there:
Then continue with Step 2 (sibyl init).
sibyl setup didn't pick up my agentWire one directly by name. Each command writes the right config for you — with the correct path resolved — so the agent connects on the first try. Nothing to open or edit:
Restart the agent afterwards. Still not connecting? It's almost always that the memory server isn't on the agent's PATH (common after a venv install) — re-run the command from the same place you installed. If it's still stuck, drop a note in the Discord and we'll sort it with you.
Easiest way: just use it. Tell your AI to remember something, close it, open it again, and ask. If it remembers, you're set.
Prefer a quick check in the Terminal? Paste sibyl status — it confirms you're signed in and where your memory is kept.
Tell it to remember something and it keeps it. Ask it to recall and it brings it back. When something you've saved is relevant, it'll mention it on its own. Mostly you won't think about any of it — your AI just remembers now.
Join the Discord and submit a ticket request to join the beta-tester chat. Bug reports, feature requests, setup questions. The cohort is small enough that every message gets a real reply.