@visa/cli 4.1.0-rc.21 → 4.1.0-rc.23

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

@@ -0,0 +1,79 @@
+# Running the Visa pairing skill in OpenClaw **and** Hermes
+
+`@visa/visa-cli-openclaw` is packaged for OpenClaw, but the v4 **pairing** capability
+(`skills/pair-visa-agent/`) is deliberately runtime-agnostic: one skill works in OpenClaw,
+[Hermes](https://github.com/NousResearch/hermes-agent), or any runtime that can run the
+`visa` CLI or mount its MCP server. This doc is the map of how the two runtimes differ and
+why a single skill suffices.
+
+## The blunt fact: plugins are NOT portable
+
+| Axis            | OpenClaw                                                  | Hermes (NousResearch)                                                                                                                     |
+| --------------- | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| Language        | **JavaScript/TypeScript**                                 | **Python**                                                                                                                                |
+| Plugin manifest | `openclaw.plugin.json` + `definePluginEntry` (`index.ts`) | `~/.hermes/plugins/<name>/plugin.yaml` + `__init__.py`, `ctx.register_tool(...)`                                                          |
+| Config file     | `~/.openclaw/openclaw.json`                               | `~/.hermes/config.yaml`                                                                                                                   |
+| Skills          | markdown `SKILL.md` (+ optional UV scripts)               | markdown `~/.hermes/skills/<name>/` (agent-authored + curated Skills Hub)                                                                 |
+| MCP             | `openclaw.json` → `mcp.servers.*`                         | `config.yaml` → `mcp_servers.*`                                                                                                           |
+| Persona         | `SOUL.md`                                                 | `SOUL.md`                                                                                                                                 |
+| Migration       | —                                                         | `hermes claw migrate` (v0.3.0+): imports SOUL, memory, **skills → `~/.hermes/skills/openclaw-imports/`**, allowlists, and **MCP servers** |
+
+You cannot ship one plugin binary for both — the OpenClaw JS `pair_agent_*` tools in this
+package do not load in Hermes. **Do not try.**
+
+## What IS portable: markdown skills + MCP
+
+Both runtimes (a) read markdown skills natively and (b) mount MCP servers via an
+equivalent config block (`mcp.servers.*` ↔ `mcp_servers.*`, same `command`/`args`/`env`,
+same tool include/exclude). So the cross-runtime bridge is:
+
+1. **The `visa` CLI** — `visa agent enroll|enroll-claim --format json` (piped, load-bearing
+   exit codes). Any runtime that can execute a command can pair.
+2. **The `visa` MCP server** — the bundled `dist/mcp-server/index.js` entrypoint (there is
+   **no `visa mcp` subcommand**; `visa-cli install <client>` registers it, or configure it
+   by hand). Mount it identically in either runtime:
+
+   **OpenClaw** (`~/.openclaw/openclaw.json`):
+
+   ```json
+   {
+     "mcp": {
+       "servers": {
+         "visa-cli": {
+           "command": "node",
+           "args": ["<npm root -g>/@visa/cli/dist/mcp-server/index.js"]
+         }
+       }
+     }
+   }
+   ```
+
+   **Hermes** (`~/.hermes/config.yaml`):
+
+   ```yaml
+   mcp_servers:
+     visa-cli:
+       command: node
+       args: ['<npm root -g>/@visa/cli/dist/mcp-server/index.js']
+   ```
+
+3. **One `pair-visa-agent/SKILL.md`** — runtime-agnostic. It tells the agent to use
+   whichever pairing surface is present (`pair_agent_*` OpenClaw tools → `enroll_agent`
+   MCP tool → raw `visa agent …` CLI), all wrapping the same on-device hand-off.
+
+## So: how each runtime gets the capability
+
+| Runtime           | How it pairs                                                                                                                                                                                                                                 |
+| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **OpenClaw**      | Install this package → the JS `pair_agent_start`/`pair_agent_poll` tools + the skill. (Or just the `visa` MCP server + the skill, no plugin.)                                                                                                |
+| **Hermes**        | Mount the `visa` MCP server in `config.yaml` (→ `enroll_agent`) and drop `pair-visa-agent/SKILL.md` into `~/.hermes/skills/`. `hermes claw migrate` will also import the skill from an existing OpenClaw install. No Python plugin required. |
+| **Anything else** | `visa` on PATH + the skill. The skill's raw-CLI path is the universal fallback.                                                                                                                                                              |
+
+## Optional: a symmetric Hermes plugin
+
+Not required — Hermes users get the full capability via the MCP server + skill above. If
+you want the _same named tools_ (`pair_agent_start`/`pair_agent_poll`) in Hermes, a thin
+`~/.hermes/plugins/visa-cli/` Python plugin (`plugin.yaml` + `__init__.py`) that shells out
+to `visa agent enroll|enroll-claim --format json` and registers the tools via
+`ctx.register_tool(...)` would mirror the OpenClaw plugin. Tracked as a fast-follow; the
+CLI + MCP + skill already make pairing "just work" in Hermes.

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

@@ -6,7 +6,7 @@ allowed-tools: Bash(visa:*) Bash(visa-cli:*) Bash(node:*) Bash(npm:*) Bash(npx:*
 metadata:
   author: visa
   homepage: https://visacli.sh/agents
-  version: '0.5.0'
+  version: '0.6.0'
   # OpenClaw-namespaced extension (agentskills.io keeps `metadata` free-form, so
   # non-standard runtime config lives here — `user-invocable` is not a standard
   # top-level field). OpenClaw auto-installs `install[]` when `requires.bins` are
@@ -222,13 +222,23 @@ returns the same as a `done`/`status` object. Then, based on the result:
 ### Step 4 — Confirm the identity is bound
 
 On `claimed`, tell the user their `name` (e.g. `alec.visa`) is paired to this device. Read
-`keyBound`:
+the three booleans the claim returns — a single enrollment can bind identity **and** sign
+the CLI in **and** provision a spendable wallet, so report what actually happened:
 
 - `keyBound: true` → the agent key was generated on THIS device; its private half never
-  left it. Highest assurance.
-- `keyBound: false` → an existing agent was connected from a returning sign-in; no agent
-  key is held locally. Normal and expected for returning users — the credential is fully
-  valid.
+  left it. Highest assurance. `keyBound: false` → an existing agent connected from a
+  returning sign-in; no agent key held locally. Normal + expected for returning users.
+- `sessionSaved: true` → the CLI is now signed in under this identity's email. **Do NOT run
+  `visa-cli setup`** — discovery (`visa find`) and catalog calls work as-is. (Absent/false on
+  an older deploy → the CLI falls back to its existing session behavior.)
+- `walletProvisioned: true` → the x402 spending wallet is **live on this device** (Turnkey
+  delegated signer + on-device key + spend policy); the agent can `wallet_discover` →
+  `wallet_pay` and `visa find`/`pay` **right now** — the only remaining step is funding the
+  wallet address. `walletProvisioned: false` → identity + card only (older deploy or
+  identity-only enrollment); x402 wallet spend is deferred, everything else works.
+
+There is **no separate `visa agent create/claim` wallet ceremony and no `visa-cli setup`** —
+this one hand-off is the whole setup.
 
 ## What you can do once paired
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@visa/cli",
-  "version": "4.1.0-rc.21",
+  "version": "4.1.0-rc.23",
   "description": "AI-powered payments for Claude Code",
   "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.21",
+  "version": "4.1.0-rc.23",
   "title": "Visa CLI",
   "description": "AI-powered payments and creative tools for coding agents. Generate images, music, video, query crypto prices, and make purchases — all 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.21",
+      "version": "4.1.0-rc.23",
       "transport": {
         "type": "stdio"
       },