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

Check the whole path your agent uses: start the MCP server, save a marked test memory, recall it, delete it:

$ sibyl doctor

Changed plan, staked, or signed a computer out? Check your account now instead of waiting for the next check-in:

$ sibyl refresh

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, Codex, Cursor or Grok Bot, also refresh the connector:

$ pip install -U sibyl-memory-mcp

Manage your devices

See and sign out the computers on your account. Free covers one computer, Pro up to 2:

$ sibyl devices
$ sibyl devices revoke 2

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 setup installs the save procedure for you: /sibyl-save in Claude Code, a block in Codex's AGENTS.md and a Codex skill, a skill in Hermes, and the save prompt on any MCP host. It commits a whole session into memory in one step, so your progress carries to the next session and your working context stays clean. Run it after a large session or at the end of any session.

The manual path, if you want the standalone skill without sibyl setup:

$ 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 →

On Pro

On Pro, Claude Code saves your session by itself: once early, then about every hour of active work; on Hermes, Cursor and Codex the plugin asks your agent to save at the same moments; a session capsule is recorded either way. Set the interval or turn it off with sibyl autosave. Each automatic save is one extra model turn that reads and writes memory. At every start Sibyl measures your instruction files and, within the policy you set once, moves accreted history out of them and into memory, where it stays searchable. It prompts you to decide which pieces to store to memory, and, for the files you pre-authorize, does it for you. On the free plan you run /sibyl-save and /sibyl-debloat yourself; Sibyl reminds you quietly, and you can turn the reminders off. See Tiers & access or the full pricing on the lab site.