← Back to Skills Marketplace
430
Downloads
0
Stars
5
Active Installs
2
Versions
Install in OpenClaw
/install webchat-https-proxy
Description
HTTPS/WSS reverse proxy for OpenClaw WebChat Control UI. Serves the Control UI over HTTPS with TLS cert management, proxies WebSocket connections to the gate...
Usage Guidance
This skill appears to do what it claims, but review before installing: 1) Back up ~/.openclaw/openclaw.json — deploy.sh will modify allowedOrigins and the proxy will read the gateway token from that file. 2) If you expose the service to your LAN (setting VOICE_HOST/VOICE_BIND_HOST or using a non-local bind), ensure a gateway token is configured — otherwise /transcribe may be accessible from the network. 3) Note small naming mismatch: the service unit uses VOICE_BIND_HOST but SKILL.md documents VOICE_HOST; deploy.sh sets VOICE_BIND_HOST for the unit. 4) Inspect assets/https-server.py yourself (it is included) if you need to confirm cert handling and auth behavior. 5) The skill installs a user systemd service and writes files under ~/.openclaw/workspace/voice-input and certs; uninstall.sh attempts to remove those. 6) The registry metadata appears to have malformed required-env entries ("[object Object]"); get clarification from the publisher if that matters to you. If these behaviors are acceptable, the skill is proportionate to its purpose; if you require stronger guarantees (no token access, no config modification, or no persistent service), do not install.
Capability Analysis
Type: OpenClaw Skill
Name: webchat-https-proxy
Version: 0.1.1
The skill implements an HTTPS/WSS reverse proxy for the OpenClaw WebChat UI with a strong focus on security. Key features include SSRF protection (restricting upstream connections to localhost), path traversal protection for static file serving using realpath validation, and constant-time authentication token validation (hmac.compare_digest). The scripts (deploy.sh, uninstall.sh) and the Python server (https-server.py) follow best practices, such as enforcing TLS 1.2+, implementing upload/response size limits, and setting restrictive file permissions (0600) on generated private keys. No indicators of malicious intent or data exfiltration were found.
Capability Assessment
Purpose & Capability
Name/description match what the files do: they copy a Python proxy into the user's workspace, update gateway.allowedOrigins in ~/.openclaw/openclaw.json, and install a user systemd service to serve HTTPS/WSS and proxy /transcribe to a local transcription service.
Instruction Scope
SKILL.md and scripts explicitly modify ~/.openclaw/openclaw.json, write a user systemd unit, and copy the runtime python to ~/.openclaw/workspace/voice-input. The proxy reads the gateway token from that config for optional auth. All file and network accesses are declared in SKILL.md, but note the auth behavior: when no gateway token is present the proxy permits requests (safe for localhost by default), so exposing to a LAN without a gateway token would allow unauthenticated /transcribe access.
Install Mechanism
No external downloads or opaque installers. It's an instruction-only skill with included scripts and a Python file. Deploy copies local files into user workspace and relies on an existing Python + aiohttp; no arbitrary remote code is fetched or executed during install.
Credentials
Requested env/config access is appropriate for a local proxy (port, bind host, allowed origin, workspace paths, and the openclaw config for gateway token). Minor inconsistencies exist between documented env names and actual usage: SKILL.md documents VOICE_HOST/VOICE_ALLOWED_ORIGIN/VOICE_HTTPS_PORT and config_paths, but the runtime python reads VOICE_BIND_HOST and WORKSPACE; deploy.sh maps VOICE_HOST → VOICE_BIND_HOST when creating the systemd unit. Registry metadata at the top also shows garbled required-env entries ("[object Object]").
Persistence & Privilege
The skill creates a user-level systemd service (~/.config/systemd/user) and enables it for the user; no root/sudo operations. always:true is not set. Uninstall script attempts to revert created artifacts.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install webchat-https-proxy - After installation, invoke the skill by name or use
/webchat-https-proxy - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.1
MIT license added; same-origin transcribe auth hardening; preserve configured voice host on redeploy.
v0.1.0
Security hardening pass: constant-time auth compare, SSRF guard, symlink-safe path checks, CORS origin validation, bounded request sizes, docs cleanup
Metadata
Frequently Asked Questions
What is WebChat HTTPS Proxy?
HTTPS/WSS reverse proxy for OpenClaw WebChat Control UI. Serves the Control UI over HTTPS with TLS cert management, proxies WebSocket connections to the gate... It is an AI Agent Skill for Claude Code / OpenClaw, with 430 downloads so far.
How do I install WebChat HTTPS Proxy?
Run "/install webchat-https-proxy" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is WebChat HTTPS Proxy free?
Yes, WebChat HTTPS Proxy is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does WebChat HTTPS Proxy support?
WebChat HTTPS Proxy is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created WebChat HTTPS Proxy?
It is built and maintained by neldar (@neldar); the current version is v0.1.1.
More Skills