@catena/cli 0.9.0 → 0.11.0

package/README.md

@@ -7,12 +7,12 @@ and submit policy-checked money movement intents.
 Run it without installing:
 
 ```bash
-pnpm dlx @catena/cli <command> [args]
+npx @catena/cli <command> [args]
 ```
 
-The package exposes the `catena` binary. Examples use `pnpm dlx @catena/cli` so
-they work directly from npm; pnpm selects `catena` because it is the package's
-only executable.
+The package exposes the `catena` binary. Examples use `npx @catena/cli` so they
+work directly from npm; npx selects `catena` because it is the package's only
+executable.
 
 ## How it works
 
@@ -31,7 +31,7 @@ browser, so `link` cannot store a credential there. Set `CATENA_SECRET_KEY` to
 the agent's P-256 secret key instead:
 
 ```bash
-CATENA_SECRET_KEY="<64 hex characters>" pnpm dlx @catena/cli whoami
+CATENA_SECRET_KEY="<64 hex characters>" npx @catena/cli whoami
 ```
 
 Create the key in the Catena console: open the agent, select the **Secret keys**
@@ -57,14 +57,14 @@ agent id. Use `--name` to suggest a name when the console creates a new agent;
 the approving operator can edit it before approval.
 
 ```bash
-pnpm dlx @catena/cli link --name "Hermes Runtime"
+npx @catena/cli link --name "Hermes Runtime"
 ```
 
 To link a specific existing agent, ask the Catena customer for the agent id
 shown in the Catena console. It looks like `agent_...`.
 
 ```bash
-pnpm dlx @catena/cli link <agent-id>
+npx @catena/cli link <agent-id>
 ```
 
 The browser approval window stays open for up to 5 minutes. If the approval is
@@ -85,8 +85,8 @@ Connect the selected profile to an agent. Omit `agent-id` to create or choose an
 agent from the Catena console.
 
 ```bash
-pnpm dlx @catena/cli link --name "Hermes Runtime"
-pnpm dlx @catena/cli link <agent-id>
+npx @catena/cli link --name "Hermes Runtime"
+npx @catena/cli link <agent-id>
 ```
 
 ### `unlink`
@@ -94,7 +94,7 @@ pnpm dlx @catena/cli link <agent-id>
 Disconnect the selected profile from its agent and remove its local credential.
 
 ```bash
-pnpm dlx @catena/cli unlink
+npx @catena/cli unlink
 ```
 
 ### `profiles current`
@@ -102,7 +102,7 @@ pnpm dlx @catena/cli unlink
 Show the selected credential profile and its routing metadata.
 
 ```bash
-pnpm dlx @catena/cli profiles current
+npx @catena/cli profiles current
 ```
 
 ### `profiles list`
@@ -110,7 +110,7 @@ pnpm dlx @catena/cli profiles current
 List linked credential profiles and mark the selected default profile.
 
 ```bash
-pnpm dlx @catena/cli profiles list
+npx @catena/cli profiles list
 ```
 
 ### `profiles use <profile>`
@@ -118,7 +118,7 @@ pnpm dlx @catena/cli profiles list
 Set the selected default profile. The profile must already be linked.
 
 ```bash
-pnpm dlx @catena/cli profiles use mcp
+npx @catena/cli profiles use mcp
 ```
 
 ### `whoami`
@@ -126,7 +126,7 @@ pnpm dlx @catena/cli profiles use mcp
 Show which agent the selected profile is linked to.
 
 ```bash
-pnpm dlx @catena/cli whoami
+npx @catena/cli whoami
 ```
 
 ### `policy show`
@@ -135,7 +135,7 @@ Show the policy assigned to the linked agent. Read this before creating
 counterparties or submitting intents.
 
 ```bash
-pnpm dlx @catena/cli policy show
+npx @catena/cli policy show
 ```
 
 The policy includes `policyCapabilities` rows. Each row grants one `read`,
@@ -148,7 +148,7 @@ counterparty creation.
 Ask a person to approve a temporary increase to one policy limit.
 
 ```bash
-pnpm dlx @catena/cli policy request-override \
+npx @catena/cli policy request-override \
   --account acct_... \
   --amount 500 \
   --duration 4h \
@@ -175,12 +175,14 @@ Fetch an MPP-protected HTTP endpoint and pay a supported USDC charge from a
 wallet account:
 
 ```bash
-pnpm dlx @catena/cli mpp --url https://api.example.com/paid \
+npx @catena/cli mpp --url https://api.example.com/paid \
   --account acct_... --max-amount 0.25
 ```
 
-Initial support covers `evm/charge` and `usdc/charge` for native USDC on Base
-and Base Sepolia. Payments use the agent's normal send capability, counterparty
+The CLI recognizes structurally valid EVM `evm/charge` and `usdc/charge`
+challenges and leaves network and canonical USDC support to the connected
+server. Base and Base Sepolia are supported where enabled. Arc support is
+rolling out. Payments use the agent's normal send capability, counterparty
 allowlist, spend limits, and approval flow. The recipient must already be a
 saved counterparty wallet rail.
 
@@ -195,7 +197,7 @@ retrying so the resource is not paid twice.
 List the accounts available under the agent's policy.
 
 ```bash
-pnpm dlx @catena/cli accounts list
+npx @catena/cli accounts list
 ```
 
 ### `counterparties list`
@@ -204,7 +206,7 @@ List counterparties, their status, and their rails. Use rail ids from this
 output with `send`.
 
 ```bash
-pnpm dlx @catena/cli counterparties list
+npx @catena/cli counterparties list
 ```
 
 ### `counterparties create`
@@ -214,7 +216,7 @@ saves the counterparty without sending an email. The command returns an intent
 envelope; policy may complete it, block it, or route it to approval.
 
 ```bash
-pnpm dlx @catena/cli counterparties create \
+npx @catena/cli counterparties create \
   --name "Acme Vendor" \
   --email billing@acme.test
 ```
@@ -232,7 +234,7 @@ Request creation of a bank-rail counterparty. The command returns an intent
 envelope; policy may complete it, block it, or route it to approval.
 
 ```bash
-pnpm dlx @catena/cli counterparties create bank \
+npx @catena/cli counterparties create bank \
   --name "Acme Vendor" \
   --bank-name "Chase" \
   --routing-number 021000021 \
@@ -256,15 +258,15 @@ Request creation of a wallet-rail counterparty. The command returns an intent
 envelope; policy may complete it, block it, or route it to approval.
 
 ```bash
-pnpm dlx @catena/cli counterparties create wallet \
+npx @catena/cli counterparties create wallet \
   --name "DAO Treasury" \
   --address 0xAbC123...
 ```
 
 Required flags: `--name`, `--address`.
 
-Optional flags: `--network` (defaults to `base`; Base is the only supported
-wallet network), `--email`, `--idempotency-key`.
+Optional flags: `--network` (defaults to `base`; availability depends on the
+connected environment), `--email`, `--idempotency-key`.
 
 ### `counterparties request-details`
 
@@ -272,7 +274,7 @@ Ask an existing counterparty to provide bank details, wallet details, or both.
 The request follows policy and may require human approval.
 
 ```bash
-pnpm dlx @catena/cli counterparties request-details cp_... --bank
+npx @catena/cli counterparties request-details cp_... --bank
 ```
 
 Pass at least one of `--bank` or `--wallet`. `--idempotency-key` is optional.
@@ -283,7 +285,7 @@ The outstanding-invitation conflict remains independent of idempotency.
 Request a USD send to a counterparty rail.
 
 ```bash
-pnpm dlx @catena/cli send \
+npx @catena/cli send \
   --rail cprl_... \
   --amount 125.00 \
   --method ach
@@ -318,7 +320,7 @@ when its inputs match an earlier command.
 Request a USD transfer between two accounts visible to the agent.
 
 ```bash
-pnpm dlx @catena/cli transfer \
+npx @catena/cli transfer \
   --from acct_... \
   --to acct_... \
   --amount 125.00
@@ -332,12 +334,44 @@ To check whether a transfer completed, run `intents get <id>` with the returned
 intent id. A separate invocation without an explicit key is a new transfer, even
 when its inputs match an earlier command.
 
+### Sends that cross chains
+
+A `send` to a counterparty wallet on the other side of the Base and Arc lane is
+an ordinary `send`. When the account cannot pay it from its balance on the
+rail's network, the send crosses chains under the same intent: the first
+signature burns the amount toward the account's own address on the other chain,
+and `intents continue` signs the send to the counterparty once the funds land.
+One intent covers the whole payment, so policy, spend limits and any approval
+are evaluated once. Gas on both legs is paid by Catena.
+
+```bash
+npx @catena/cli send --rail cprl_... --amount 250.00 --method on-chain
+npx @catena/cli intents get int_...
+npx @catena/cli intents continue int_...
+```
+
+The result carries `crossChain` when the send crossed. Its `nextStep` says what
+to do: `wait` and poll `intents get`, `continue` and run `intents continue`,
+`done`, or `blocked` with `failureReason` set. A network the provider does not
+sponsor yet answers `wallet_send_action_not_yet_enabled` rather than charging
+the agent; on `intents continue` the intent stays at `continue`, so try again
+later.
+
+### `intents continue`
+
+Sign the second leg of a send that crossed chains, once `intents get` shows
+`crossChain.nextStep` as `continue`. Optional: `--idempotency-key`.
+
+```bash
+npx @catena/cli intents continue int_...
+```
+
 ### `accounts balance`
 
 Read an account balance through the policy engine.
 
 ```bash
-pnpm dlx @catena/cli accounts balance acct_...
+npx @catena/cli accounts balance acct_...
 ```
 
 ### `accounts transactions`
@@ -347,7 +381,7 @@ same read access as `accounts balance` and never creates an intent. Returns
 `{ accountId, transactions, total }` newest-first.
 
 ```bash
-pnpm dlx @catena/cli accounts transactions acct_...
+npx @catena/cli accounts transactions acct_...
 ```
 
 Optional flags: `--start` / `--end` (ISO 8601 bounds), `--limit` (default 50,
@@ -360,7 +394,7 @@ Read an account deposit address through the policy engine. `--network` and
 `--asset` default to `base` and `usdc`.
 
 ```bash
-pnpm dlx @catena/cli accounts deposit-address acct_... --network base --asset usdc
+npx @catena/cli accounts deposit-address acct_... --network base --asset usdc
 ```
 
 ### `intents get`
@@ -368,7 +402,7 @@ pnpm dlx @catena/cli accounts deposit-address acct_... --network base --asset us
 Look up the current state of an intent created by this agent.
 
 ```bash
-pnpm dlx @catena/cli intents get int_...
+npx @catena/cli intents get int_...
 ```
 
 The response includes a `data` field carrying the associated result once one
@@ -389,9 +423,9 @@ stdin. Use stdin (or `--` before the argument) when the message starts with `-`
 or spans multiple lines.
 
 ```bash
-pnpm dlx @catena/cli feedback "The transfer flow worked great"
+npx @catena/cli feedback "The transfer flow worked great"
 
-pnpm dlx @catena/cli feedback <<'EOF'
+npx @catena/cli feedback <<'EOF'
 - transfer failed
 - policy was confusing
 EOF
@@ -404,8 +438,8 @@ with code 1.
 
 `send` and `transfer` exit as soon as the intent is created and any immediate
 next action is submitted. Inspect the returned `.status` and `.reasons` fields,
-then use `pnpm dlx @catena/cli intents get <intent-id>` to check whether it
-later completes, requires approval, or fails.
+then use `npx @catena/cli intents get <intent-id>` to check whether it later
+completes, requires approval, or fails.
 
 ## Configuration
 
@@ -419,11 +453,11 @@ later completes, requires approval, or fails.
 Every command supports `--help`.
 
 ```bash
-pnpm dlx @catena/cli --help
-pnpm dlx @catena/cli send --help
-pnpm dlx @catena/cli counterparties create --help
-pnpm dlx @catena/cli counterparties create email --help
-pnpm dlx @catena/cli counterparties create bank --help
-pnpm dlx @catena/cli counterparties create wallet --help
-pnpm dlx @catena/cli counterparties request-details --help
+npx @catena/cli --help
+npx @catena/cli send --help
+npx @catena/cli counterparties create --help
+npx @catena/cli counterparties create email --help
+npx @catena/cli counterparties create bank --help
+npx @catena/cli counterparties create wallet --help
+npx @catena/cli counterparties request-details --help
 ```