You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/WINDOWS_NODE_TESTING.md
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,6 +129,29 @@ When the node connects, it advertises these capabilities:
129
129
dotnet test .\tests\OpenClaw.Shared.Tests\OpenClaw.Shared.Tests.csproj --filter "FullyQualifiedName~Mxc"
130
130
```
131
131
132
+
### Full Gateway `system.run` MXC runtime proof
133
+
- The focused E2E below provisions a fresh WSL Gateway, starts an isolated tray instance, sets a local exec approval rule through MCP, invokes `system.run` through the real Gateway `node.invoke` path, and verifies tray MXC diagnostics show contained `mxc-direct-appc` execution for both allowed execution and denied writes to the tray data directory.
134
+
- Run it when validating the Gateway/Windows node runtime path, not just direct MCP or shared library behavior.
135
+
- When reproducing this manually against an existing Gateway, make sure `gateway.nodes.allowCommands` includes `system.run`, `system.run.prepare`, and `system.which`, then approve any `pending-reapproval` request with `openclaw nodes approve <pendingRequestId>`. The node can advertise `system.run` while the Gateway still blocks it until both gates are updated.
136
+
137
+
```powershell
138
+
.\build.ps1
139
+
$env:OPENCLAW_REPO_ROOT = (Get-Location).Path
140
+
$env:OPENCLAW_RUN_E2E = "1"
141
+
dotnet test .\tests\OpenClaw.E2ETests\OpenClaw.E2ETests.csproj `
0 commit comments