docs: refresh CLI and trusted-proxy docs
This commit is contained in:
@@ -21,6 +21,25 @@ openclaw devices list
|
||||
openclaw devices list --json
|
||||
```
|
||||
|
||||
### `openclaw devices remove <deviceId>`
|
||||
|
||||
Remove one paired device entry.
|
||||
|
||||
```
|
||||
openclaw devices remove <deviceId>
|
||||
openclaw devices remove <deviceId> --json
|
||||
```
|
||||
|
||||
### `openclaw devices clear --yes [--pending]`
|
||||
|
||||
Clear paired devices in bulk.
|
||||
|
||||
```
|
||||
openclaw devices clear --yes
|
||||
openclaw devices clear --yes --pending
|
||||
openclaw devices clear --yes --pending --json
|
||||
```
|
||||
|
||||
### `openclaw devices approve [requestId] [--latest]`
|
||||
|
||||
Approve a pending device pairing request. If `requestId` is omitted, OpenClaw
|
||||
@@ -71,3 +90,5 @@ Pass `--token` or `--password` explicitly. Missing explicit credentials is an er
|
||||
|
||||
- Token rotation returns a new token (sensitive). Treat it like a secret.
|
||||
- These commands require `operator.pairing` (or `operator.admin`) scope.
|
||||
- `devices clear` is intentionally gated by `--yes`.
|
||||
- If pairing scope is unavailable on local loopback (and no explicit `--url` is passed), list/approve can use a local pairing fallback.
|
||||
|
||||
@@ -281,7 +281,7 @@ Vector search over `MEMORY.md` + `memory/*.md`:
|
||||
|
||||
- `openclaw memory status` — show index stats.
|
||||
- `openclaw memory index` — reindex memory files.
|
||||
- `openclaw memory search "<query>"` — semantic search over memory.
|
||||
- `openclaw memory search "<query>"` (or `--query "<query>"`) — semantic search over memory.
|
||||
|
||||
## Chat slash commands
|
||||
|
||||
@@ -468,8 +468,9 @@ Approve DM pairing requests across channels.
|
||||
|
||||
Subcommands:
|
||||
|
||||
- `pairing list <channel> [--json]`
|
||||
- `pairing approve <channel> <code> [--notify]`
|
||||
- `pairing list [channel] [--channel <channel>] [--account <id>] [--json]`
|
||||
- `pairing approve <channel> <code> [--account <id>] [--notify]`
|
||||
- `pairing approve --channel <channel> [--account <id>] <code> [--notify]`
|
||||
|
||||
### `webhooks gmail`
|
||||
|
||||
|
||||
@@ -26,6 +26,7 @@ openclaw memory status --deep --index --verbose
|
||||
openclaw memory index
|
||||
openclaw memory index --verbose
|
||||
openclaw memory search "release checklist"
|
||||
openclaw memory search --query "release checklist"
|
||||
openclaw memory status --agent main
|
||||
openclaw memory index --agent main --verbose
|
||||
```
|
||||
@@ -37,6 +38,12 @@ Common:
|
||||
- `--agent <id>`: scope to a single agent (default: all configured agents).
|
||||
- `--verbose`: emit detailed logs during probes and indexing.
|
||||
|
||||
`memory search`:
|
||||
|
||||
- Query input: pass either positional `[query]` or `--query <text>`.
|
||||
- If both are provided, `--query` wins.
|
||||
- If neither is provided, the command exits with an error.
|
||||
|
||||
Notes:
|
||||
|
||||
- `memory status --deep` probes vector + embedding availability.
|
||||
|
||||
@@ -16,6 +16,17 @@ Related:
|
||||
## Commands
|
||||
|
||||
```bash
|
||||
openclaw pairing list whatsapp
|
||||
openclaw pairing approve whatsapp <code> --notify
|
||||
openclaw pairing list telegram
|
||||
openclaw pairing list --channel telegram --account work
|
||||
openclaw pairing list telegram --json
|
||||
|
||||
openclaw pairing approve telegram <code>
|
||||
openclaw pairing approve --channel telegram --account work <code> --notify
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Channel input: pass it positionally (`pairing list telegram`) or with `--channel <channel>`.
|
||||
- `pairing list` supports `--account <accountId>` for multi-account channels.
|
||||
- `pairing approve` supports `--account <accountId>` and `--notify`.
|
||||
- If only one pairing-capable channel is configured, `pairing approve <code>` is allowed.
|
||||
|
||||
Reference in New Issue
Block a user