OpenClaw Proof and Validation

Use for changes that affect tray UX, Settings, onboarding, chat/canvas, Command Center, Windows node capabilities, local MCP, gateway connection/pairing, permissions, diagnostics, or agent-facing instructions.

If the validation host is macOS, read PARALLELS.md for the optional local Parallels Windows VM workflow.

Rules

• Required automated/focused tests are mandatory. Do not ask to skip them.
• Prefer isolated tray data so proof does not mutate %APPDATA%\OpenClawTray.
• Computer-use is usually a batched closeout proof pass, not a continuous dev-loop tool. Mid-development use is fine when explicitly requested or needed to unblock work; ask first whether to run it or provide manual screenshot/output steps.
• Local MCP is part of every Windows node command contract: command discovery and invocation must work through winnode or raw MCP JSON-RPC.
• Rubber-duck review is required before PR publication for non-trivial UI/MCP/node-command/setup/pairing/security/permissions/diagnostics work; it is also useful mid-development when extra design/testing validation is requested.
• Report blockers explicitly. Do not turn missing UI, MCP, gateway, camera, screen, or permission proof into success-shaped wording.

Required validation