Management & maintenance

Once Sibyl is installed, here is how to keep it healthy, up to date, and running lean. You will not reach for most of these day to day, they are here when you want them.

Check it is working

See your account, memory size, and plan:

$ sibyl status

Run a quick self-check of the memory engine:

$ sibyl health

Keep it up to date

The plugin improves often. See if you are behind, then update in place:

$ sibyl update

$ sibyl update --apply

If you connected Claude Code or Codex, also refresh the connector:

$ pip install -U sibyl-memory-mcp

Manage your devices

See and sign out the devices on your account:

$ sibyl devices

Best practices: keep your context small

Sibyl works best when your AI keeps a small, sharp context and lets memory hold the rest. A lean context is faster, cheaper, and more accurate. Two habits keep it that way.

Move your context into memory

If your project keeps notes in files like CLAUDE.md or AGENTS.md, move them into memory once. Sibyl backs up every file first, checks the copies, then hands the transfer to your own AI to read on your machine. Sibyl Labs never sees your files.

$ sibyl migrate

Run it from the project you want to bring over. Trimming the old files is the last step, it is optional, and only after you confirm.

Save at the end of a session

sibyl-save is a small companion skill that commits a whole session into memory in one step, so your progress carries to the next session and your working context stays clean. Install it once, then run it after a large session or at the end of any session.

$ git clone https://github.com/Sibyl-Labs/sibyl-save
$ mkdir -p .claude/skills/sibyl-save && cp sibyl-save/SKILL.md .claude/skills/sibyl-save/

Then run /sibyl-save setup once, and /sibyl-save whenever you want to save. It works with Claude Code, Codex, Cursor, and Hermes.

sibyl-save on GitHub →