LaunchKit · 2026
Back to Skills

webchat-voice-proxy

Voice input and microphone button for OpenClaw WebChat Control UI.

0
616 downloads
by @neldar

Setup & Installation

openclaw skills install @neldar/webchat-voice-proxy

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install webchat-voice-proxy

Version History

v0.2.2Mar 6, 2026 - Version note by skill developer:

Deprecate monolith skill; replaced by webchat-https-proxy + webchat-voice-gui. Use webchat-voice-full-stack for one-step install.

What This Skill Does

Deprecated combined installer that set up HTTPS/WSS proxy and voice mic UI for OpenClaw WebChat in a single step. Replaced by webchat-https-proxy and webchat-voice-gui. Use webchat-voice-full-stack for equivalent one-step deployment.

When to use it

  • Adding push-to-talk voice input to OpenClaw WebChat
  • Running local speech-to-text without sending audio to external services
  • Accessing WebChat over HTTPS from a LAN device
  • Keeping voice transcription proxy running after reboots via systemd
  • Switching mic recording between push-to-talk and toggle mode

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: set up voice input for my OpenClaw WebChat on localhost

AGENT
  1. 1Verify faster-whisper transcription service is active on port 18790
  2. 2Run deploy.sh to inject voice-input.js into Control UI and configure gateway allowed origins
  3. 3Create and enable openclaw-voice-https.service systemd unit for persistent HTTPS proxy on port 8443
  4. 4Install gateway startup hook to re-inject voice script after Control UI updates
  5. 5Run status.sh to confirm both services are active and HTTPS returns 200
OUTPUT

Voice-enabled WebChat at https://127.0.0.1:8443 with mic button, push-to-talk keyboard shortcuts, and real-time VU meter

Requirements

Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.

faster-whisper HTTP transcription service running locally on port 18790