Structured code review through the shared OpenClaw agent-skills installation.
日本語の概要は準備中です。原文の説明を表示しています。
Use the OpenClaw Windows app's local MCP server and winnode CLI for development, debugging, proof, and automation.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill when developing, debugging, or validating the OpenClaw Windows app through its same-machine MCP server. This is a developer and automation surface, not the OpenClaw gateway-to-node transport.
| Path | Purpose | Transport |
|---|---|---|
| OpenClaw node mode | Product path for an OpenClaw agent to use a paired Windows machine | Gateway WebSocket and node.invoke; agents use the gateway nodes tool |
| Windows app local MCP | Developer/debugging path for same-machine clients to inspect and invoke the running Windows app | Authenticated loopback MCP HTTP; developers use MCP tools or winnode |
Do not describe a local MCP invocation as gateway proof. Do not use local MCP
as a substitute when the behavior being validated depends on gateway pairing,
allowlists, reapproval, routing, or node.invoke.
Prefer isolated tray data so tests do not change
%APPDATA%\OpenClawTray:
.\run-app-local.ps1 -Isolated -AllowNonMain
Copy the data directory printed by the launcher:
$env:OPENCLAW_TRAY_DATA_DIR = '<isolated-data-dir>'
Enable Local MCP Server in Permissions. MCP-only mode is supported:
EnableMcpServer=true with EnableNodeMode=false starts local capabilities
without requiring gateway credentials.
Always discover before invoking because settings determine which capabilities are currently exposed:
winnode --list-tools
The live tools/list response is authoritative. The complete static command
reference is .agents\skills\winnode\SKILL.md, and
McpToolBridge.CommandDescriptions is the canonical description source.
winnode --command app.status --params '{}'
winnode --command app.connection.status --params '{}'
winnode --command system.which --params '{"bins":["git","node"]}'
winnode targets the local Windows app only. Its --node argument is accepted
for CLI parity but ignored. It loads the MCP token from the selected tray
profile; do not place the token on the command line.
Use --invoke-timeout <ms> for bounded long-running calls. Parameters must be
a JSON object. Prefix with @ to load a large JSON object from a file.
Use raw JSON-RPC when changing server or protocol shape. Read the token from the selected isolated profile without printing it:
$tokenPath = Join-Path $env:OPENCLAW_TRAY_DATA_DIR 'mcp-token.txt'
$token = Get-Content $tokenPath -Raw
Send initialize, tools/list, and tools/call to the loopback endpoint
printed by the app. Use notifications/cancelled with the active JSON-RPC
request ID to prove cancellation. Never publish the bearer token, settings,
gateway records, device identities, or raw secret-bearing responses.
Local MCP exposes app.* commands that are not advertised to the gateway node:
app.status, app.connection.status, app.connection.gatewaysapp.navigate, app.menu, app.searchapp.chat.snapshot, app.chat.send, app.chat.resetapp.chat.queue.list, app.chat.queue.cancelapp.settings.get, app.settings.setUse these to set up deterministic UI state, navigate the current build, inspect
connection state, and drive functional proof. Re-read tools/list for the
exact commands available on the running build.
The same INodeCapability registration seam serves both local MCP and gateway
node mode, so local MCP can exercise capability implementations directly:
system.*, device.*, screen.*, camera.*, location.*canvas.*, including A2UIbrowser.proxytts.*, stt.*ollama.models, ollama.chat when Share Windows Ollama is enabledThis proves the local capability path only. Add a real gateway invocation when the change affects paired-gateway behavior.
For a new or changed Windows node command:
INodeCapability path.McpToolBridge.CommandDescriptions..agents\skills\winnode\SKILL.md.winnode tests.winnode --list-tools and winnode --command ....Follow .agents\skills\openclaw-proof-validation\SKILL.md for the complete
validation and PR evidence checklist.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Structured code review through the shared OpenClaw agent-skills installation.
日本語の概要は準備中です。原文の説明を表示しています。
Use Crabbox from macOS, Linux, or native Windows controllers to run OpenClaw Windows node builds, tests, and targeted proof on remote native Windows or WSL2 hosts, including Azure or brokered AWS leases and static SSH hosts. Use when remote Windows validation is needed or the user asks for Crabbox validation. Always report the actual provider, lease id, run URL, command, and result.
日本語の概要は準備中です。原文の説明を表示しています。
Run complete OpenClaw Windows Node issue and PR triage, including landing queues, proof pools, ownership audits, and release planning.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial dual-model code review that runs two AI models in parallel, cross-references findings, and produces a consensus severity table with fix confidence ratings. Use when asked for a thorough code review, adversarial review, dual-model review, confidence-rated review, or 'Hanselman review'.
日本語の概要は準備中です。原文の説明を表示しています。
Build the native (MSIX, isolated-session) OpenClaw Gateway from the latest openclaw/openclaw sources (or any ref, local checkout, or prebuilt openclaw.tgz), register it side by side with the Microsoft Store Gateway, and run Companion against it with OPENCLAW_NATIVE_GATEWAY_DEV_PATCH. Use when the user asks to test Companion with Gateway main, an unreleased Gateway change, or a source-built native Gateway, or to remove such a build.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and collect OpenClaw Windows validation/proof: tests, rubber-duck review, UI evidence, MCP output, and gateway runtime proof.
日本語の概要は準備中です。原文の説明を表示しています。