sibyl-memory-cli 0.3.8

Command-line interface for the Sibyl Memory Plugin. `sibyl init` activates, `sibyl upgrade` runs the staker / subscription flow, `sibyl status` shows current tier and DB stats, `sibyl whoami` gives a one-line account summary, `sibyl devices` lists active devices and supports per-device revoke.

sibyl-memory-cli

Command-line interface for the Sibyl Memory Plugin.

pip install sibyl-memory-cli

This pulls in sibyl-memory-client (the local SDK) and sibyl-memory-hermes (the Hermes provider) automatically.

Commands

sibyl init                  Open the browser activation page. Writes ~/.sibyl-memory/credentials.json.
sibyl upgrade               Open the upgrade page. Stake $SIBYL or subscribe in USDC.
sibyl status                Show local credentials, DB size, and the server's view of your tier.
sibyl health                Run the SibylMemoryProvider self-check (schema version, DB path, tenant).

Activation

$ sibyl init

  activation · three paths · pick whichever fits your device

  Session          a1b2c3d4…e5f6
  Code             1 2 3 4 5 6   (use this in the email panel)
  Opening          https://auth.sibyllabs.org/a1b2c3d4-…

  desktop wallet · email + code · or send USDC from any mobile wallet
  this terminal will pick up automatically when you bind.

  ⠹ watching the network for your bind … 9:42 left

The browser opens to a dedicated short-URL auth subdomain (auth.sibyllabs.org/<session-uuid>). Pick a wallet from the EIP-6963 picker (Rabby / MetaMask / Coinbase Wallet / Frame / Brave / Rainbow), enter email + 6-digit code, or send a unique sub-cent USDC amount from any mobile wallet on Base. The terminal picks up the moment any of the three paths binds. Credentials are written to ~/.sibyl-memory/credentials.json at mode 0600.

Upgrade

$ sibyl upgrade

  upgrade · lift the 2 MB free-tier cap

  Account            a1b2c3d4…e5f6
  Current tier       FREE
  Opening            https://sibyllabs.org/plugin/upgrade?session=…

  two paths in the browser:
    1. stake $SIBYL on Base (free unlimited if you qualify)
    2. subscribe in USDC (monthly / quarterly / annual)

In the browser:

• Stake — connect your wallet (browser or Coinbase Smart Wallet), sign to bind, and the page checks your $SIBYL balance on Base. If you hold the threshold (default 100,000 $SIBYL liquid+staked, configurable), the local cap lifts.
• Subscribe — pick monthly ($29) / quarterly ($79) / annual ($290) USDC, sign the transfer, the server records the subscription. Tier flips immediately.

On either path, the CLI sees the tier change, rewrites credentials.json, and clears tier_cache.json so your next write picks up the new entitlement without delay.

Status

$ sibyl status

  Sibyl Memory Plugin · status

  LOCAL
    Credentials       ~/.sibyl-memory/credentials.json
    Account           a1b2c3d4…e5f6
    Tier              FREE
    DB size           1,247,300 bytes (1.19 MB)
    Tier cache        free (checked 2026-05-16T18:12:03)

  SERVER
    Tier              FREE
    Source            free
    Cap bytes         2,097,152
    $SIBYL held       0
    Threshold         100,000
    Qualified         no

If LOCAL and SERVER tiers diverge, run sibyl upgrade.

Environment overrides

For internal testing only:

SIBYL_API_BASE=https://staging.api.sibyllabs.org sibyl init
SIBYL_ACTIVATE_BASE=https://staging.auth.sibyllabs.org sibyl init
SIBYL_UPGRADE_BASE=https://staging.sibyllabs.org/plugin/upgrade sibyl upgrade

SIBYL_ACTIVATE_BASE accepts both subdomain form (https://auth.example.org → path-based session URL: https://auth.example.org/<uuid>) and legacy path form (https://example.org/plugin/activate → query-based: ?session=<uuid>). The CLI auto-detects from the hostname.

Security

• credentials.json is written atomically at mode 0600.
• session_token is never printed in full — only a short slice.
• No memory content ever transits these endpoints. The CLI never reads memory.db content; it only checks file size.
• Wallet operations happen in the browser. The CLI sees only the resulting tier change.

License

MIT.