docs(gateway): clarify backend RPC pairing · openclaw/openclaw@41b2702
steipete
·
2026-04-26
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -383,6 +383,14 @@ child session is marked `abortedLastRun: true`. Those restart-aborted child
|
383 | 383 | sessions remain recoverable through the sub-agent orphan recovery flow, which |
384 | 384 | sends a synthetic resume message before clearing the aborted marker. |
385 | 385 | |
| 386 | +If a sub-agent spawn fails with Gateway `PAIRING_REQUIRED` / `scope-upgrade`, |
| 387 | +check the RPC caller before editing pairing state. Internal `sessions_spawn` |
| 388 | +coordination should connect as `client.id: "gateway-client"` with |
| 389 | +`client.mode: "backend"` over direct loopback shared-token/password auth; that |
| 390 | +path does not depend on the CLI's paired-device scope baseline. Remote callers, |
| 391 | +explicit `deviceIdentity`, explicit device-token paths, and browser/node clients |
| 392 | +still need normal device approval for scope upgrades. |
| 393 | + |
386 | 394 | ## Stopping |
387 | 395 | |
388 | 396 | - Sending `/stop` in the requester chat aborts the requester session and stops any active sub-agent runs spawned from it, cascading to nested children. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
