@visa/cli 4.1.0-rc.67 → 4.1.0-rc.69

package/dist/skills/pair-visa-agent/SKILL.md

@@ -202,15 +202,25 @@ setup step. Follow this sequence:
       operation, so this runtime needs a live owner session before `grant-wallet`:
       `agent_login` (MCP) or `visa agent login` (CLI). Without a session the grant has
       no account to delegate from.
-- [ ] **Resolve the next step** with `setup_agent` (`{"rail":"wallet"}`), or drive the
-      raw `visa agent grant-wallet <agentId>` ceremony. `setup_agent` sequences
-      identity → wallet → policy → ready and points at the owner-approval grant — it
-      does not tell you to self-mint.
-- [ ] **Owner approves the wallet.** The human confirms the wallet grant on the **v4
-      agent dashboard** (`app.visacli.sh/agent/enroll`), approving with their **sign-in
-      session — no passkey** — and confirming the caps. That approval registers the
-      delegated Turnkey signer + caps and writes the delegated Turnkey credential
-      (`turnkey.json`) to this runtime. You cannot approve on their behalf.
+- [ ] **Initiate the wallet grant from MCP — no shelling.** Call `agent_connect`
+      (`{"rail":"wallet","ceiling":"<usd>","perTransaction":"<usd>"}`); omit `agentId`
+      to target the most recently paired agent. It creates the delegation request and
+      returns `{ url, code, attachId, willGrant, expiresAt }`. Present the bare `url`
+      and `code` to the human exactly as returned — the crypto approval happens in the
+      browser and **cannot** run inline in chat. Prefer this over the raw
+      `visa agent grant-wallet <agentId>` CLI ceremony; `setup_agent` (`{"rail":"wallet"}`)
+      still sequences identity → wallet → policy → ready if you need the next-step map.
+      If `agent_connect` returns `{"code":"session_required"}`, run `agent_login` first.
+- [ ] **Owner approves the wallet.** The human opens the `url` and confirms the wallet
+      grant on the **v4 agent dashboard** (`app.visacli.sh/agent/enroll`), approving with
+      their **sign-in session — no passkey** — and confirming the caps. You cannot approve
+      on their behalf.
+- [ ] **Finish from MCP with `agent_connect_poll`.** Call `agent_connect_poll`
+      (`{"attachId":"<from agent_connect>"}`; or resume by `agentId`) — each call runs one
+      bounded poll. It returns `{"ok":false,"state":"...","blockedByKind":"awaiting_human_approval"}`
+      while pending; call again until it returns `{"ok":true,"state":"grant_activated","fundAddress":...,"caps":...}`.
+      Activation registers the delegated Turnkey signer + caps and writes the delegated
+      Turnkey credential (`turnkey.json`) to this runtime. It never spends.
 - [ ] **Confirm the real wallet** with `wallet_status` (or `visa wallet show`). Only a
       provisioned/delegated credential — not the served tool list — means the wallet is
       usable; `agent_capabilities.wallet.available` reflects this.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@visa/cli",
-  "version": "4.1.0-rc.67",
+  "version": "4.1.0-rc.69",
   "description": "Visa CLI runtime for stable agent identity and separately authorized payment capabilities",
   "bin": {
     "visa-cli": "./bin/visa-cli.js",

package/server.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
   "name": "io.github.visa-crypto-labs/visa-cli",
-  "version": "4.1.0-rc.67",
+  "version": "4.1.0-rc.69",
   "title": "Visa CLI",
   "description": "Pair a human-approved agent identity, configure payment capabilities separately, and discover and pay x402 services from your AI coding assistant.",
   "websiteUrl": "https://github.com/Visa-Crypto-Labs/Visa-mono/tree/main/packages/cli#readme",
@@ -9,7 +9,7 @@
     {
       "registryType": "npm",
       "identifier": "@visa/cli",
-      "version": "4.1.0-rc.67",
+      "version": "4.1.0-rc.69",
       "transport": {
         "type": "stdio"
       },