SIBYL LABSdocs
Lab home Research

CLI reference

Every command in sibyl-memory-cli. Install with pip install sibyl-memory-cli; it brings the SDK and the Hermes provider with it.

Command summary

CommandWhat it does
sibyl initActivate the plugin in your browser. Writes ~/.sibyl-memory/credentials.json.
sibyl setup [target]Auto-detect Hermes / Claude Code / Codex and wire Sibyl as the memory provider.
sibyl migrateGuided, backup-first onboarding of your existing agent memory.
sibyl statusShow local credentials, DB size, and the server's view of your tier.
sibyl upgradeOpen the upgrade flow: stake $SIBYL or subscribe in USDC.
sibyl whoamiOne-line account summary (masked by default).
sibyl devicesList devices (active bearer tokens) for the account.
sibyl memory …Read-only inspection of your store: list, search, recall.
sibyl healthRun the provider self-check (schema version, DB path, tenant).
sibyl updateCheck for newer sibyl-memory-* releases on PyPI.
sibyl dashboardOpen the account dashboard (delegates to status for now).
sibyl logoutRemove local credentials. Your memory.db stays put.

init

Opens the browser activation page. Sign a SIWE message with your wallet; the terminal picks up the binding automatically and writes credentials at mode 0600.

$ sibyl init

setup

Auto-detects your stack and wires Sibyl as the memory provider. No argument detects everything; name one target to wire just it.

$ sibyl setup                 # detect all
$ sibyl setup claude-code     # target: hermes | claude-code | codex
$ sibyl setup --dry-run       # print changes, write nothing

Flags: --yes (accept defaults), --force (overwrite a non-Sibyl provider config), --dry-run, and --hermes-home / --claude-settings / --codex-config to override autodetection.

migrate

Moves existing agent memory into Sibyl without risk. Backs up and byte-verifies every file it finds, wires Sibyl into each detected harness, prints an extraction prompt you run in your own agent (locally), then optionally trims the originals only on your confirmation.

$ sibyl migrate
$ sibyl migrate --no-debloat   # skip the trim step

Flags: --backup-dir PATH, --no-debloat, --yes (the trim step still asks separately).

status

Shows your local credentials, DB size, and tier cache, alongside the server's view of your tier and cap. If LOCAL and SERVER tiers diverge, run sibyl upgrade.

$ sibyl status

  Sibyl Memory Plugin · status

  LOCAL
    Account           a1b2c3d4…e5f6
    Tier              FREE
    DB size           1.19 MB

  SERVER
    Tier              FREE
    Cap bytes         2,097,152
    $SIBYL held       0
    Qualified         no

upgrade

Opens the upgrade page with two paths: stake $SIBYL on Base (free unlimited if you qualify), or subscribe in USDC. The CLI picks up the new tier the moment it flips. See Tiers & access.

$ sibyl upgrade

whoami & devices

$ sibyl whoami                 # masked one-line summary
$ sibyl devices                # active bearer tokens for this account
$ sibyl devices revoke 2       # revoke a device by its listed index

memory (read-only inspection)

Look at your own store without an agent in the loop. All three are read-only.

$ sibyl memory list                    # list entities (optionally by category)
$ sibyl memory search "atlas"           # FTS across entities + state + reference + journal
$ sibyl memory recall project atlas    # one entity by category + name

health & update

$ sibyl health                 # provider self-check
$ sibyl update                 # report outdated sibyl-memory-* packages
$ sibyl update --apply         # pip install -U the outdated ones
Internal overrides

SIBYL_API_BASE, SIBYL_ACTIVATE_BASE, and SIBYL_UPGRADE_BASE redirect the CLI at staging endpoints. They exist for internal testing; you do not need them in normal use.