OpenClaw Launcher

Create Windows desktop shortcut and scripts for one-click OpenClaw startup on WSL. Use when: (1) user asks to create/open/fix OpenClaw launcher, (2) user rep...

Before installing or running these instructions: 1) Inspect every generated .ps1/.bat/.bat keep-alive file — don't run them blindly. 2) Be aware the script reads your WSL OpenClaw config (~/.openclaw/openclaw.json) to extract a token; that token is sensitive and is used locally to open a dashboard URL. 3) netsh interface portproxy changes networking and requires admin privileges; allow it only if you trust the source and understand the change. 4) PowerShell uses -ExecutionPolicy Bypass and hidden execution — this suppresses prompts and reduces protections; prefer to review and run interactively first. 5) SKILL.md appears truncated; get the full instructions before proceeding. 6) If unsure, manually create the shortcut and run the steps one-by-one (or test in a disposable/VM environment). 7) Ensure Python + Pillow are installed if you need icon conversion, and back up any existing files the scripts may overwrite.

Type: OpenClaw Skill Name: openclaw-launcher Version: 1.1.0 The openclaw-launcher skill bundle (SKILL.md) automates the creation of a Windows-to-WSL bridge using several high-risk techniques: it extracts a 40-character authentication token from a local configuration file (~/.openclaw/openclaw.json), modifies system-wide network settings using `netsh interface portproxy` (requiring administrative privileges), and creates hidden background processes while bypassing PowerShell execution policies. Although these actions are technically consistent with the stated goal of facilitating a one-click startup for the OpenClaw dashboard, the combination of credential extraction and administrative network manipulation represents a significant security surface.