@visa/cli 5.0.0-rc.394 → 5.0.0-rc.395
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -3
- package/dist/cli.js +172 -172
- package/dist/mcp-server/index.js +310 -310
- package/dist/merchant-ucp-mcp/index.js +4 -4
- package/native/bin/win32-arm64/visa-runtime-signer.exe +0 -0
- package/native/bin/win32-x64/visa-runtime-signer.exe +0 -0
- package/package.json +2 -2
- package/server.json +2 -2
package/README.md
CHANGED
|
@@ -200,9 +200,12 @@ Re-run `visa connect` any time to see what is mounted and finish whatever is
|
|
|
200
200
|
unfinished; every step is idempotent. To ask what this machine can do from
|
|
201
201
|
inside an agent, call `get_status`.
|
|
202
202
|
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
203
|
+
A signed-out machine that holds no agent gets one URL and one short code: the
|
|
204
|
+
owner signs in on the protected-agent page, types the code once (it signs the
|
|
205
|
+
terminal in and binds its request), then approves the device and its limits as
|
|
206
|
+
a separate press. A machine that already holds an agent, or a Visa web that
|
|
207
|
+
does not yet offer this, signs in on its own page first, so the owner sees two
|
|
208
|
+
URLs and two codes, one at a time. Never relay the code on the owner's behalf.
|
|
206
209
|
|
|
207
210
|
After the device is approved, the owner's page sets up the agent's key on
|
|
208
211
|
their Tempo wallet (it asks for USDC.e first if the wallet is empty, and keeps
|