File size: 5,052 Bytes
2cf7040 c5a913d 2cf7040 c5a913d 2cf7040 c5a913d 2cf7040 c5a913d 2cf7040 b2101ae 2cf7040 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 | # sibyl-memory-cli
Command-line interface for the **Sibyl Memory Plugin**.
```bash
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 migrate Guided onboarding: back up your existing memory/agent files, wire Sibyl
into every detected harness, populate Sibyl Memory from the backup, and
optionally slim the originals. Backup-first, never destructive.
sibyl setup [target] Wire Sibyl as the memory provider for Hermes, Claude Code, and/or Codex.
target is one of: hermes | claude-code | codex (default: detect all).
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).
```
## Migrate (guided onboarding)
```bash
$ sibyl migrate
```
`sibyl migrate` moves your accumulated agent memory into Sibyl without risking
your existing files:
1. **Back up first.** Every memory/agent file it finds (`CLAUDE.md`,
`AGENTS.md`, `.codex/config.toml`, `.hermes/*`, and similar) is copied to a
timestamped backup folder and byte-verified before anything else happens.
2. **Wire Sibyl** into every detected harness — Claude Code (via
`claude mcp add --scope user`), Codex (via `~/.codex/config.toml`), Hermes.
3. **Extract** — it prints a prompt you run in your own agent. The agent reads
only from the backup and writes structured memory through the `sibyl-memory`
tool. The extraction runs locally on your machine; Sibyl Labs never sees your
files or memory.
4. **Verify** the new entries that landed in your local DB.
5. **Optionally trim** the originals — only if you confirm, and only because a
verified backup exists. Your full pre-migration files are always preserved.
Flags: `--backup-dir PATH` (default: home), `--no-debloat` (skip the trim
step), `--yes` (skip the initial confirm; the trim step still asks separately).
> No warranty. Keep your backup until you've confirmed everything migrated.
> Sibyl Labs is not responsible for data loss.
## Activation
```bash
$ sibyl init
Sibyl Memory Plugin · activation
Session: a1b2c3d4…e5f6
Opening: https://sibyllabs.org/plugin/activate?session=a1b2c3d4-…
Sign in with your wallet in the browser. This terminal will pick up automatically.
⠹ waiting for browser activation … 9:42 left
```
The browser opens. Sign a SIWE message with your wallet. The terminal picks up the moment the binding lands. Credentials are written to `~/.sibyl-memory/credentials.json` at mode 0600.
## Upgrade
```bash
$ sibyl upgrade
Sibyl Memory Plugin · upgrade
Account a1b2c3d4…e5f6
Current tier FREE
Opening https://sibyllabs.org/plugin/upgrade?session=…
Two paths in your 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
```bash
$ 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:
```bash
SIBYL_API_BASE=https://staging.api.sibyllabs.org sibyl init
SIBYL_ACTIVATE_BASE=https://staging.sibyllabs.org/plugin/activate sibyl init
SIBYL_UPGRADE_BASE=https://staging.sibyllabs.org/plugin/upgrade sibyl upgrade
```
## 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.
|