@visa/cli 5.0.0-rc.394 → 5.0.0-rc.396

package/README.md

@@ -200,9 +200,12 @@ Re-run `visa connect` any time to see what is mounted and finish whatever is
 unfinished; every step is idempotent. To ask what this machine can do from
 inside an agent, call `get_status`.
 
-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.
+A signed-out machine that holds no agent gets one URL and one short code: the
+owner signs in on the protected-agent page, types the code once (it signs the
+terminal in and binds its request), then approves the device and its limits as
+a separate press. A machine that already holds an agent, or a Visa web that
+does not yet offer this, signs in on its own page first, so the owner sees two
+URLs and two codes, one 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
@@ -220,6 +223,14 @@ are kept as `*.replaced-<time>` backups). `--restart` never touches the
 installed `pair-visa-agent` skill; `--force-skill` replaces it, moving a locally
 edited copy to `.visa-cli-managed/backups/` first.
 
+`visa connect --setup <key>` picks up an agent the owner started on the Visa
+website. That page shows the exact line to run once the agent exists. The
+approval link this prints carries the key, and the owner's page binds this
+machine to that agent instead of making a new one. Running the same line again
+resumes the same approval. A setup can be picked up by one computer only; a
+second gets `web_start_already_adopted`. In a chat, pass `setup` to
+`agent_enroll` with the same key.
+
 The agent's keys (wallet, card and TAP) live in the operating system's
 store: the macOS Keychain, Windows data protection (DPAPI), or the Linux Secret
 Service; a server without one uses an owner-only `0600` file only when
@@ -319,7 +330,7 @@ a name that was ever real has to stay readable here.
 | Tool | Description |
 |------|-------------|
 | `get_status` | Everything about this machine in one answer: the owner signed in, the agent this machine holds, its limits, its capabilities, and what is owed next |
-| `agent_enroll` | The one door. Idempotent, and runs whichever leg is owed: signs the owner in when the session lapsed, answers `already_connected` when this machine already holds a usable agent (so an agent that exists is never answered by minting a second one), and enrolls when none is held. One Approve certifies this machine's wallet, card and TAP keys. On a new computer, the owner can choose "replacing" on the approval page to move an existing agent there; the old computer's keys stop. Pass `restart: true` to force a fresh enrollment |
+| `agent_enroll` | The one door. Idempotent, and runs whichever leg is owed: signs the owner in when the session lapsed, answers `already_connected` when this machine already holds a usable agent (so an agent that exists is never answered by minting a second one), and enrolls when none is held. One Approve certifies this machine's wallet, card and TAP keys. On a new computer, the owner can choose "replacing" on the approval page to move an existing agent there; the old computer's keys stop. Pass `restart: true` to force a fresh enrollment, or `setup: "<key>"` to pick up the agent the owner started on the Visa website |
 | `discover` | Find something to pay for. Takes search text (by default it searches paid services the wallet pays on Tempo), or one URL to read its live charge without paying |
 | `pay` | Pay **from the agent wallet**: MPP on Tempo, in USDC.e. Search text searches; a URL whose 402 offers a Tempo charge pays (without `max` it returns the price and what the agent can spend now). A merchant with no Tempo charge, or a directory listing id, is refused with `merchant_not_supported`. A merchant checkout URL is refused by name — that is `purchase_create` |
 | `history` | Receipts, across every rail, with reconciliation when a payment's outcome is unresolved. Tempo payments are listed under `tempoPayments` |