@visa/cli 5.0.0-rc.352 → 5.0.0-rc.353

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

@@ -145,7 +145,7 @@ OpenClaw users receive the skill via `visa connect openclaw` (or through the `@v
      `~/.hermes/config.yaml`.
    - **No MCP integration:** everything below still works — connecting is a shell
      command, and `--format json` is available on every command.
-3. **Check what is owed.** `visa status` prints the owner, the agent, its limits, which
+3. **Check what is owed.** `get_status` reports the owner, the agent, its limits, which
    clients are mounted, and one `next:` line when something is blocking.
 
 ## MCP mounting examples
@@ -299,13 +299,14 @@ runtimes.
 ## Management commands (an agent that already exists)
 
 ```
-visa status --format json     # owner, agent, limits, mounts, every readiness gate
-visa limits --format json     # what it may spend; with amounts, the owner approves
-visa activity --format json   # payments across every rail
+get_status {}                 # owner, agent, limits, mounts, every readiness gate
+history    {}                 # this agent's payments
+# Caps are the owner's, in the Visa Console: /agent/enroll/limits?agent=<agent-id>
+# Spend across every rail is the Console's Activity feed.
 visa disconnect --revoke      # drop this machine's spending authority
 ```
 
-`visa status` is the one command that answers "can it spend, and what is missing" — it
+`get_status` is the one call that answers "can it spend, and what is missing" — it
 carries the readiness gates the old `spendability` and `preflight` commands each answered
 a fragment of. Pausing, resuming, renaming and revoking an agent are owner actions in the
 Visa Console, not terminal commands.
@@ -319,12 +320,12 @@ If this device already holds an agent, a fresh enrolment is not needed and creat
 _second, separate_ agent. Do this instead:
 
 1. **Tell the user plainly:** "This device is already set up as `<name>`." Read the name
-   from `agent_capabilities` or `visa status`. Start another enrolment only if they
+   from `get_status`. Start another enrolment only if they
    explicitly want a second agent.
 2. **Report status honestly — "set up" is several separate things.** Never imply the agent
    can spend just because it exists. Read it live from tools rather than guessing from
    prose: `agent_capabilities` returns the DERIVED capability map, `get_status` reports
-   pairing / account / version, `visa status --format json` answers "can it spend, and
+   pairing / account / version, `get_status` answers "can it spend, and
    what is missing", and `agent_login` establishes or confirms the account session.
    - **Identity** — bound to _this user's_ account, on _this device_.
    - **Spending** — the limits the owner approved in the browser. You **cannot** self-grant
@@ -344,7 +345,7 @@ one returns `legacy_door_removed`.
 
 What to do instead:
 
-- [ ] **Diagnose first.** `visa status --format json` and `agent_capabilities` say
+- [ ] **Diagnose first.** `get_status` says
       exactly what is missing. Do not start anything before you know which of identity,
       wallet delegation, card authority or funding is absent.
 - [ ] **If the device's identity custody is broken**, `visa connect` repairs it in place
@@ -433,7 +434,7 @@ chat, bypass eligibility, or retry an uncertain merchant submission. Existing
 Never infer or invent identity or address data.
 
 Create and inspect this profile through the `checkout_profile` MCP tool whenever the
-payment flow runs through MCP. Do not shell `visa status` as a substitute unless the
+payment flow runs through MCP. Do not shell a terminal command as a substitute unless the
 shell has the exact same `HOME` and `VISA_CLI_HOME` as the MCP subprocess. A profile
 found under another root is owner PII, not a migration candidate: never scan, copy, or
 auto-adopt it. If the roots drifted, keep the root holding the paired identity and have the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@visa/cli",
-  "version": "5.0.0-rc.352",
+  "version": "5.0.0-rc.353",
   "description": "Visa CLI runtime for stable agent identity and separately authorized payment capabilities",
   "bin": {
     "visa-cli": "./bin/visa-cli.js",
@@ -44,13 +44,13 @@
     "typescript": "^5.7.0",
     "@visa-cli/tools": "2.0.0-rc.3",
     "@visa/crypto": "0.3.0-rc.19",
-    "@visa/agent-mail": "0.2.0-rc.4",
     "@visa/identity": "0.3.0-rc.24",
-    "@visa/money": "0.2.1-rc.0",
+    "@visa/agent-mail": "0.2.0-rc.4",
     "@visa/observability": "0.2.2-rc.16",
-    "@visa/wallet": "0.3.0-rc.42",
+    "@visa/money": "0.2.1-rc.0",
+    "@visa/wallet-tools": "0.2.0-rc.50",
     "@visa/shared": "0.2.0-rc.15",
-    "@visa/wallet-tools": "0.2.0-rc.50"
+    "@visa/wallet": "0.3.0-rc.42"
   },
   "engines": {
     "node": ">=20.0.0"

package/server.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.visa-crypto-labs/visa-cli",
-  "version": "5.0.0-rc.352",
+  "version": "5.0.0-rc.353",
   "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": "5.0.0-rc.352",
+      "version": "5.0.0-rc.353",
       "transport": {
         "type": "stdio"
       },