docs: clarify node exec approval plan forwarding

This commit is contained in:
Peter Steinberger
2026-04-04 12:17:55 +01:00
parent 605f48556b
commit 9ddfaff45f
4 changed files with 23 additions and 0 deletions

View File

@@ -130,3 +130,8 @@ The node host stores its node id, token, display name, and gateway connection in
- `~/.openclaw/exec-approvals.json`
- [Exec approvals](/tools/exec-approvals)
- `openclaw approvals --node <id|name|ip>` (edit from the Gateway)
For approved async node exec, OpenClaw prepares a canonical `systemRunPlan`
before prompting. The later approved `system.run` forward reuses that stored
plan, so edits to command/cwd/session fields after the approval request was
created are rejected instead of changing what the node executes.