clawdentity 0.0.15 → 0.0.16
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/package.json
CHANGED
|
@@ -128,8 +128,12 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
|
|
|
128
128
|
- `clawdentity pair start <agent-name> --qr`
|
|
129
129
|
- `clawdentity pair start <agent-name> --qr --qr-output <path>`
|
|
130
130
|
- `clawdentity pair start <agent-name> --qr --ttl-seconds <seconds>`
|
|
131
|
+
- `clawdentity pair start <agent-name> --qr --wait`
|
|
132
|
+
- `clawdentity pair start <agent-name> --qr --wait --wait-seconds <seconds> --poll-interval-seconds <seconds>`
|
|
131
133
|
- `clawdentity pair confirm <agent-name> --qr-file <path>`
|
|
132
134
|
- `clawdentity pair confirm <agent-name> --ticket <clwpair1_...>`
|
|
135
|
+
- `clawdentity pair status <agent-name> --ticket <clwpair1_...>`
|
|
136
|
+
- `clawdentity pair status <agent-name> --ticket <clwpair1_...> --wait`
|
|
133
137
|
|
|
134
138
|
### Token verification
|
|
135
139
|
- `clawdentity verify <tokenOrFile>`
|
|
@@ -211,13 +215,20 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
|
|
|
211
215
|
- At this point the agent is ready to start pairing or accept pairing.
|
|
212
216
|
|
|
213
217
|
8. Pairing phase (separate from onboarding).
|
|
214
|
-
-
|
|
215
|
-
-
|
|
218
|
+
- Required default initiator flow:
|
|
219
|
+
- `clawdentity pair start <agent-name> --qr --wait`
|
|
220
|
+
- Optional overrides: `--ttl-seconds <seconds>`, `--qr-output <path>`, `--wait-seconds <seconds>`, `--poll-interval-seconds <seconds>`
|
|
221
|
+
- Why `--wait` is required by default:
|
|
222
|
+
- responder saves peer during `pair confirm`
|
|
223
|
+
- initiator saves peer only after confirmed status is observed (`pair start --wait` or `pair status`)
|
|
216
224
|
- Responder (two mutually exclusive paths):
|
|
217
225
|
- QR path: `clawdentity pair confirm <agent-name> --qr-file <path>`
|
|
218
226
|
- Inline ticket path: `clawdentity pair confirm <agent-name> --ticket <clwpair1_...>`
|
|
219
227
|
- Cannot provide both `--qr-file` and `--ticket` simultaneously.
|
|
220
228
|
- Pair confirm auto-saves peer DID/proxy mapping locally from QR ticket metadata.
|
|
229
|
+
- If initiator started without `--wait`, initiator must run:
|
|
230
|
+
- `clawdentity pair status <agent-name> --ticket <clwpair1_...> --wait`
|
|
231
|
+
- This persists the peer on initiator after responder confirmation.
|
|
221
232
|
- Confirm pairing success, then run `clawdentity openclaw relay test`.
|
|
222
233
|
|
|
223
234
|
9. Post-pairing verification.
|
|
@@ -284,6 +295,9 @@ Do not suggest switching endpoints unless user explicitly asks for endpoint chan
|
|
|
284
295
|
- `pair confirm` 410 (`PROXY_PAIR_TICKET_EXPIRED`): ticket has expired. Request a new ticket.
|
|
285
296
|
- `CLI_PAIR_CONFIRM_INPUT_CONFLICT`: cannot provide both `--ticket` and `--qr-file`. Use one path only.
|
|
286
297
|
- `CLI_PAIR_PROXY_URL_MISMATCH`: local `proxyUrl` does not match registry metadata. Rerun `clawdentity invite redeem <clw_inv_...>`.
|
|
298
|
+
- Responder shows peer but initiator does not:
|
|
299
|
+
- Cause: initiator started pairing without `--wait`.
|
|
300
|
+
- Fix: run `clawdentity pair status <initiator-agent> --ticket <clwpair1_...> --wait` on initiator.
|
|
287
301
|
|
|
288
302
|
### Setup errors
|
|
289
303
|
- `405 Method Not Allowed` on hook path: rerun `clawdentity openclaw setup <agent-name>` and restart OpenClaw.
|