github/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 18:21:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs: clarify Matrix recovery order

Browse Source
This commit is contained in:
Gustavo Madeira Santana
2026-03-09 10:14:05 -04:00
parent e3102fcae7
commit cc645e774b
2 changed files with 25 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/channels/matrix.md
View File

@@ -300,6 +300,18 @@ Use `--force-reset-cross-signing` only when you intentionally want to discard th
If you intentionally want to discard the current room-key backup and start a new backup baseline for future messages, use `openclaw matrix verify backup reset --yes`. If you intentionally want to discard the current room-key backup and start a new backup baseline for future messages, use `openclaw matrix verify backup reset --yes`.
Do this only when you accept that unrecoverable old encrypted history will stay unavailable. Do this only when you accept that unrecoverable old encrypted history will stay unavailable.
### Fresh backup baseline
If you want to keep future encrypted messages working and accept losing unrecoverable old history, run these commands in order:
```bash
openclaw matrix verify backup reset --yes
openclaw matrix verify backup status --verbose
openclaw matrix verify status
```
Add `--account <id>` to each command when you want to target a named Matrix account explicitly.
### Startup behavior ### Startup behavior
When `encryption: true`, Matrix defaults `startupVerification` to `"if-unverified"`. When `encryption: true`, Matrix defaults `startupVerification` to `"if-unverified"`.
@@ -342,7 +354,7 @@ That includes:
Incoming verification requests from another Matrix client are tracked and auto-accepted by OpenClaw. Incoming verification requests from another Matrix client are tracked and auto-accepted by OpenClaw.
When SAS emoji verification becomes available, OpenClaw starts that SAS flow automatically for inbound requests and confirms its own side. When SAS emoji verification becomes available, OpenClaw starts that SAS flow automatically for inbound requests and confirms its own side.
You still need to confirm "They match" in your Matrix client to complete the verification. You still need to compare the emoji or decimal SAS in your Matrix client and confirm "They match" there to complete the verification.
OpenClaw does not auto-accept self-initiated duplicate flows blindly. Startup skips creating a new request when a self-verification request is already pending. OpenClaw does not auto-accept self-initiated duplicate flows blindly. Startup skips creating a new request when a self-verification request is already pending.

12
docs/install/migrating-matrix.md
View File

@@ -259,6 +259,18 @@ openclaw matrix verify backup restore --recovery-key "<your-recovery-key>" --ver
If the backup restores successfully but some old rooms are still missing history, those missing keys were probably never backed up by the previous plugin. If the backup restores successfully but some old rooms are still missing history, those missing keys were probably never backed up by the previous plugin.
## If you want to start fresh for future messages
If you accept losing unrecoverable old encrypted history and only want a clean backup baseline going forward, run these commands in order:
```bash
openclaw matrix verify backup reset --yes
openclaw matrix verify backup status --verbose
openclaw matrix verify status
```
If the device is still unverified after that, finish verification from your Matrix client by comparing the SAS emoji or decimal codes and confirming that they match.
## Related pages ## Related pages
- [Matrix](/channels/matrix) - [Matrix](/channels/matrix)