Claw Store

Persist your memory across sessions and machines. Your data lives on Jackal Protocol decentralized storage — not on any single machine. If the machine dies, your memory survives.

All content is encrypted client-side with AES-256-GCM before leaving your machine. The server never sees plaintext.

Trust & security quick facts

• Runtime API host: https://web-production-5cce7.up.railway.app (separate from homepage domain)
• Data leaving your machine: encrypted payloads + key metadata + your Jackal public address for provisioning
• Data not leaving your machine: plaintext memory content, encryption key, wallet mnemonic/private key
• No runtime wordlist download: BIP39 English wordlist is vendored locally in this skill package
• Secret file permissions: locally generated key/mnemonic files are written with 0600 permissions

• Homepage: https://obsideo.io
• Source code: https://github.com/Regan-Milne/jackal-memory
• Publisher: Obsideo (obsideo.io@gmail.com)

Setup

1. Get an API key: https://web-production-5cce7.up.railway.app/auth/login
2. Set environment variable: JACKAL_MEMORY_API_KEY=
3. Install Python dependency: pip install cryptography
4. Install Node.js runtime (recommended Node >=20) and install helper deps in the skill folder:

npm install

1. On first save, an encryption key and a Jackal wallet are auto-generated locally and saved to

~/.config/jackal-memory/. These never leave your machine.

Back up your encryption key (run once, store the output safely):

python {baseDir}/jackal-memory/client.py keygen

Set JACKAL_MEMORY_ENCRYPTION_KEY= to use the same key on other machines.

Back up your Jackal wallet mnemonic (controls on-chain storage ownership):

python {baseDir}/jackal-memory/client.py wallet

Set JACKAL_MEMORY_WALLET_MNEMONIC= to use the same wallet on other machines.

Onboarding new users

If JACKAL_MEMORY_API_KEY is not set:

1. Tell the user you need their Claw Store API key to get started
2. Send them to: https://web-production-5cce7.up.railway.app/auth/login — sign in with Google, the key is shown immediately
3. Instruct them to set it directly in their environment — never share or paste an API key into chat:

```

export JACKAL_MEMORY_API_KEY=

```

1. Once set, confirm you're connected and offer to save something right away as a first test
2. After the first successful save, remind the user to back up their Jackal wallet mnemonic:

```

python {baseDir}/jackal-memory/client.py wallet

```

The mnemonic controls their on-chain storage. Losing it means losing sovereign access to stored files.

Important: Never ask the user to paste their API key, encryption key, or wallet mnemonic into chat. Always direct them to set it as an environment variable on their machine.

Base URL

https://web-production-5cce7.up.railway.app

Note: this runtime API host is currently on Railway and is distinct from the project homepage domain (obsideo.io). Verify endpoint trust in your environment before use.

Auth

Authorization: Bearer $JACKAL_MEMORY_API_KEY

Usage

On session start — restore memory:

python {baseDir}/jackal-memory/client.py load <key>

On session end — save memory:

python {baseDir}/jackal-memory/client.py save <key> <content>

Check storage usage:

python {baseDir}/jackal-memory/client.py usage

List known saved keys (local manifest):

python {baseDir}/jackal-memory/client.py list
python {baseDir}/jackal-memory/client.py list project-

Export local key manifest for backup/migration:

python {baseDir}/jackal-memory/client.py manifest-export ~/jackal-manifest.json

Show/generate Jackal wallet:

python {baseDir}/jackal-memory/client.py wallet
python {baseDir}/jackal-memory/client.py wallet --show-mnemonic
python {baseDir}/jackal-memory/client.py walletgen

Or call the API directly:

GET  /load/{key}
POST /save       {"key": "...", "content": "..."}
GET  /usage

Behaviour guidelines

• Load your identity/memory blob on startup before doing any work
• Write locally during the session as normal
• Call save at session end or on significant state changes
• Use descriptive keys: identity, session-2026-02-26, project-jackal
• Never log or expose JACKAL_MEMORY_API_KEY in output
• Never log or expose JACKAL_MEMORY_ENCRYPTION_KEY in output

Network latency & propagation (important)

Jackal is eventually consistent across a provider pool. A successful save means the write was accepted, but read visibility can lag.

Agent protocol:

1. If save succeeds, treat it as accepted and continue work (optimistic flow).
2. If immediate load fails, do not assume data loss.
3. Retry with patience (recommended: 8 attempts, 15s apart; ~2 minutes total).
4. If still unavailable, report as propagation delay and re-check later.
5. Escalate only after extended delay windows continue to fail.

Notes:

• Provider-level logs like Error: Can't claim can be non-fatal noise.
• Some providers may temporarily fail while others succeed.
• Operationally: save now, verify later, then finalize once data becomes readable.

Proactive memory suggestions

When you encounter something that seems important — a key decision, user preference, project status, significant result, or plan — proactively say:

> "This seems important. Should I back it up to Claw Store?"

If the user confirms, save it immediately with a descriptive key. Do not wait until the end of the session for important information — suggest saving it as soon as you recognise its value.

Never proactively suggest storing raw secrets (passwords, API keys, private keys, recovery phrases, tokens).

Only store such material if the user explicitly requests it and understands the risk.

Wallet sovereignty

Each user gets their own Jackal wallet, generated locally on first save. The private key (mnemonic)

never leaves your machine — not even the API server sees it. Your storage is owned by your wallet

address on the Jackal blockchain. If Obsideo shuts down, you can access your files directly via any

Jackal client using your mnemonic.

Back up the mnemonic:

python {baseDir}/jackal-memory/client.py wallet

For selective recovery after hardware loss, keep all three backups:

1. JACKAL_MEMORY_WALLET_MNEMONIC
2. JACKAL_MEMORY_ENCRYPTION_KEY
3. local key manifest (manifest-export) so you can restore specific keys instead of guessing.

Endpoint and storage transparency

This skill interacts with:

• Obsideo API: https://web-production-5cce7.up.railway.app
• Jackal decentralized storage providers (resolved dynamically by Jackal SDK)
• Local subprocess: jackal-memory/jackal-client.js (Node helper for Jackal upload/download)

Local files written by this skill:

• ~/.config/jackal-memory/key (AES encryption key, if not provided via env; written with 0600)
• ~/.config/jackal-memory/jackal-mnemonic (wallet mnemonic, if not provided via env; written with 0600)
• .env (read-only): jackal-client.js will load one directory up if present, to populate missing env vars.

Operational note: run in a clean environment when possible to avoid unintentionally inheriting unrelated secrets from .env.

Security

• All content is encrypted before leaving your machine — the server cannot read your memories
• Your Jackal wallet private key never leaves your machine
• Set API keys and secrets directly in local environment variables; never paste them into chat
• Back up both keys: keygen (encryption) and wallet (Jackal mnemonic)
• Treat memory content as sensitive — it may contain personal or operational data
• Do not proactively store raw secrets unless the user explicitly asks
• BIP39 English wordlist is included locally in the package (no runtime fetch required).