@visa/cli 5.0.0-rc.391 → 5.0.0-rc.392

package/README.md

@@ -204,6 +204,15 @@ Two browser approvals remain: the sign-in page, then the protected-agent page
 where the owner approves the device and its limits. Each prints one URL and one
 short code at a time. Never relay the code on the owner's behalf.
 
+After the device is approved, the owner's page sets up the agent's key on
+their Tempo wallet (it asks for USDC.e first if the wallet is empty, and keeps
+trying on its own while it is open). `visa connect` waits up to two minutes
+for it and says "Connected. Nothing is owed." only once the key is set up;
+until then the device line is pending with `wallet_key_setup_pending` and the
+next step. `get_status` reports the same in `walletKey.tempoKey`. Reopening
+the approval link, in the same tab or a new one, lands on the same approval;
+it never asks again for a code the terminal has already used.
+
 `visa connect --restart` starts a fresh approval for this machine: choose
 **Replacing** on the approval page to give the same agent new keys (its budget
 and history stay; the old keys are retired and this machine's old local records
@@ -418,6 +427,13 @@ Console with the human's approval.
 That URL is not payment-gated. That is an answer, not a fault: search for the
 service's paid route with `discover { "query": "<what you want>" }`.
 
+**`wallet_key_setup_pending` after `visa connect`**
+The agent is connected, but its key on the owner's Tempo wallet is not set up
+yet, so it cannot pay. The open approval page finishes it on its own (add
+USDC.e to the wallet if it asks); if that page was closed, opening the Visa
+Console finishes it the same way. Then run `visa connect` again to confirm. Do
+not use `--restart`.
+
 **Enrollment ended `expired` or `cancelled`**
 The ceremony timed out — run `visa connect` again. Do not look for a resume
 command; the retired setup doors are removed, and `connect` is idempotent.