OpenClaw Windows Node
https://github.com/openclaw/openclaw-windows-node- Category
- Developer Tools
- Rank
- No. 519Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- openclaw
- GitHub
- 2.1k stars
- Latest release
- v2026.7.2-alpha.86
- Date
About
Windows companion suite for OpenClaw — system tray app, shared library, node, and PowerToys Command Palette extension.
What it does
It connects a Windows PC to OpenClaw so agents can use selected local capabilities. Users control command execution, browser automation, cameras, screen capture, audio, location, and visual canvases through explicit permissions. It also supports native chat, diagnostics, notifications, deep-link automation, and local access from MCP clients without requiring a gateway connection.
Why it's ranked here
This is a substantial Windows integration, not a thin launcher. It combines capability controls, gateway pairing, configurable command isolation, local MCP access, diagnostics, onboarding, updates, and native UI. Its layered approval model and extensive automated testing make it credible for sensitive desktop automation, though its Windows and OpenClaw focus sharply limits its audience.
What's good
Permissions determine which capabilities the PC advertises, while gateway policy and Windows checks provide additional enforcement. Command execution offers locked-down, recommended, unprotected, and custom containment profiles. The local MCP endpoint uses bearer authentication and exposes the same capability registry, so newly registered capabilities become available across supported transports without separate bridge work.
Tradeoffs
The main application requires a recent Windows release, and WebView2 may need separate installation. Some capabilities require Windows consent plus deliberate gateway approval. Command isolation can fall back to uncontained host execution when MXC is unavailable unless strict fallback blocking is enabled. Local MCP lacks streaming, detailed per-tool input schemas, remote authentication, and a configurable port interface.
How to use it well
Use it when OpenClaw agents need controlled access to a dedicated Windows workstation, or when local MCP clients need Windows-native tools without gateway setup. Start with restrictive sandbox settings, enable only required capabilities, and review reapproval warnings after policy changes. It does not replace gateway security for commands executed on the gateway, nor does it serve non-Windows desktop deployments.
Technical notes+
README.md describes a .NET 10 solution split across WinUI, connection, shared capability, chat, setup, validation CLI, node CLI, and functional UI projects. docs/MCP_MODE.md documents an in-process JSON-RPC 2.0 MCP bridge on loopback port 8765, bearer-token authentication, live capability discovery, cooperative cancellation, and independent gateway-node and MCP-server toggles. package.json is private and exists only to supply the Microsoft MXC sandbox dependency copied into application output. docs/RELEASING.md documents tag-driven GitVersion releases, signed Inno installers, portable update ZIPs, x64 and ARM64 builds, and a paused MSIX distribution path. docs/TEST_COVERAGE.md lists unit, native UI, accessibility, integration, end-to-end, setup, CLI, functional UI, and packaging validation surfaces.
Observed
- License
- MIT
- Primary stack
- C# on .NET 10 with WinUI 3 for the desktop application
- Platform support
- Windows 10 20H2 or later and Windows 11, on x64 and ARM64
- Installation
- Pre-built, non-administrator Inno setup executables for x64 and ARM64
- Interfaces
- Native tray UI, chat, deep links, gateway WebSocket node, local HTTP MCP server, and command-line tools
- Local MCP transport
- JSON-RPC 2.0 over an authenticated loopback HTTP endpoint
- Testing structure
- Separate unit, UI, accessibility, integration, end-to-end, setup-engine, CLI, functional UI, and packaging test surfaces
Read from README.md, package.json, docs/SETUP.md, docs/MCP_MODE.md, docs/RELEASING.md, docs/TELEMETRY.md, docs/VERSIONING.md, docs/CODE_REVIEW.md, docs/ARCHITECTURE.md, docs/LOCALIZATION.md, docs/ACCESSIBILITY.md, docs/TEST_COVERAGE.md.
What it can do
Provide quick access to OpenClaw functions from system tray
User clicks on system tray icon → Menu with OpenClaw options and controls
Execute OpenClaw commands through PowerToys Command Palette
Command typed in PowerToys Run interface → Executed OpenClaw operation or result
Run OpenClaw as background service node
System startup or manual activation → Running OpenClaw service process
Expose OpenClaw functionality to other Windows applications
API calls from external applications → OpenClaw operation results via shared library
Integrate OpenClaw with Windows workflow automation
Windows automation scripts or tools → Automated OpenClaw task execution
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.