Tiers & access

Free tier is generous on purpose; you can build real things with it. Both tiers need an account: run sibyl init once on each computer. Pro removes the cap, adds computers, and makes save, debloat and skill extraction run for you, with self-learning and the linter. There is one paid tier, Pro, and two ways to get it: subscribe by card or USDC, or stake $SIBYL.

The tiers

Buying Pro for three or more people? A team pays for Pro seats on one bill, and each seat gives one member's own account Pro; their memory stays theirs. See Teams.

Upgrade

Card payments run from the Pro page: pay, then run sibyl claim <code> in your terminal if you bought before installing. For the wallet paths, run sibyl upgrade. It opens a page with two options:

$ sibyl upgrade

• Stake. Connect your wallet (browser wallet or Coinbase Smart Wallet), sign to bind, and the page checks the $SIBYL you have staked on Base. Stake the threshold in the $SIBYL staking contract and the local cap lifts while it stays staked. The default threshold is 100,000 $SIBYL; only staked $SIBYL counts, tokens that are only held in the wallet do not.
• Subscribe in USDC. Pick monthly or annual, sign the transfer, and the tier flips immediately. Same price as card.

On either path the CLI sees the change, rewrites credentials.json, and clears its tier cache so your next write picks up the new plan without delay. Once you qualify by staking, your account picks it up automatically within the hour, or run sibyl refresh to apply it now. If a computer has not picked up a change yet, sibyl refresh checks immediately. The upgrade command reference has the terminal flow.

Accounts and computers

An account is required on every tier. sibyl init signs a computer in; until it has, the memory tools answer that an account is needed. Your local data is never deleted, and sibyl memory reads it without an account. Each computer checks its plan with your account in the background: about once an hour on Free, about once a day on Pro. Offline, a computer keeps working for up to 14 days and then pauses until it can check in again.

Free covers one computer and Pro up to 2. Signing in again on the same computer never uses a second slot. At the limit, sibyl init lists the computers already signed in and offers to open the account page so you can sign one out. sibyl devices and sibyl status show the count, for example 1 of 1 (Free) · Pro: up to 2. Installed before accounts were required? See I installed before accounts were required.

Save, debloat and skills

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 proposes first; a file is trimmed by itself only after you run sibyl debloat auto <file> for that file at its path. Pro also proposes skills from repeated work in your sessions, and creates nothing without a yes.

On Free you run /sibyl-save and /sibyl-debloat yourself; Sibyl reminds you quietly, and sibyl reminders off turns the reminders off. See the CLI reference for sibyl save, sibyl debloat and sibyl skills.

The 5 MB cap, precisely

The free cap is on local database size: 5,242,880 bytes. You can read and search freely; the cap governs how much you store. When an activated free account writes past the cap, the write is checked against the server. Paid tiers remove the cap. Run sibyl status to see your current DB size against the cap.

Privacy & network behavior

This is the whole of it, stated plainly:

• Your memory content never leaves the machine. Not on read, not on write, not on search.
• Before sign-in, nothing is sent. sibyl memory reads your local data with no network call.
• Sign-in and plan check-ins. sibyl init signs the computer in. After that the client checks your plan with api.sibyllabs.org, about once an hour on Free and once a day on Pro, carrying account metadata only: account id, this computer's sign-in token, plugin version, and OS family.
• A size check near the cap. When a free account nears its cap, the client calls api.sibyllabs.org/api/plugin/check-write with the account id, sign-in token, and the database's byte size and proposed delta.
• Operation counts. An aggregate count of memory operations, tied to your account, unless you opt out with SIBYL_MEMORY_TELEMETRY=0. In Hermes it is off unless you opt in with SIBYL_MEMORY_TELEMETRY=1. Counts only, never what you remembered.
• None of these carry the contents of your memory. The server knows which plan your account is on and how many operations ran, never what you stored.
• Save and debloat stay local. They read your instruction files and memory on your computer; no file content and no conversation content leaves it. Wallet operations happen in the browser; the CLI only sees the resulting tier change.