> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usecarry.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# The carry CLI

> Proof-carrying memory from your terminal — recall with a receipt, gate access, and anchor verifiable proofs on Sui + Walrus.

`@usecarry/cli` gives you Carry's whole loop from a terminal: recall with an Answer Receipt printed in the shell, flip the gate, and anchor a **verifiable** proof on Sui — each memory blob checked live against Walrus.

<Card title="npm — @usecarry/cli" icon="npm" href="https://www.npmjs.com/package/@usecarry/cli">
  Published and installable.
</Card>

## Install

```bash theme={null}
npm i -g @usecarry/cli      # or: npx @usecarry/cli <command>
```

Works out of the box against Walrus + Sui testnet — no keys required for recall/verify. Anchoring on-chain uses your local **Sui CLI** keystore.

## Use

```bash theme={null}
carry seed                                    # load a demo vault (real Walrus testnet blobs)
carry recall "am I allergic to anything?"     # → Answer Receipt: authorized ✓  verified ✓ on Walrus
carry access revoke health                    # flip the retrieval gate
carry recall "am I allergic to anything?"     # → 1 namespace blocked · your data never reached the model
carry remember "Blood type is O negative" --ns health
carry anchor --onchain                        # → mints a Receipt object, prints a verify link
carry anchor --onchain --claim billing        # → all_authorized: false — the chain catches the lie
carry list                                    # every memory + its Walrus ref
carry policy                                  # the allow/deny policy
```

## What `--onchain` does

`carry anchor --onchain` stores the receipt to Walrus, computes its `blake2b256` content digest, and submits a real `carry::access::anchor_receipt` transaction — minting an owned, verifiable **Receipt** proof object and printing a `verify` link:

```text theme={null}
  all_authorized: true  ✓   (claimed: health)
    proof:  0xd84de0fd…424765f7
    verify ↗ https://carrysui.vercel.app/verify/0xd84de0fd…424765f7
```

Open the link and all three checks are green — the proof a terminal command produced is independently verifiable by anyone. See [the verifier](/onchain/verifier).

## Config

| Env                                        | Default                                          |
| ------------------------------------------ | ------------------------------------------------ |
| `WALRUS_PUBLISHER`                         | `https://publisher.walrus-testnet.walrus.space`  |
| `WALRUS_AGGREGATOR`                        | `https://aggregator.walrus-testnet.walrus.space` |
| `CARRY_STORE`                              | `~/.carry/store.json`                            |
| `CARRY_PACKAGE_ID` / `CARRY_ACCESS_POLICY` | the deployed testnet ids                         |

<Tip>
  The CLI and the [MCP server](/integrate/mcp) share the same on-disk vault (`~/.carry/store.json`) — a fact you `carry remember` in the terminal is recalled by your IDE agent, under the same gate.
</Tip>