yuga-hashimoto/openclaw-assistant

Registry

Summary

OpenClaw Assistant is an open-source, offline-first voice assistant app for Android and Wear OS, built with Kotlin and Jetpack Compose. It features wake word activation, system assistant integration via VoiceInteractionService, and local speech recognition using Vosk, enabling private, self-hosted AI assistance without cloud dependency.

Key features

• Wake word activation for hands-free use
• System assistant integration via VoiceInteractionService
• Offline speech recognition with Vosk
• Built with Kotlin and Jetpack Compose
• Supports Wear OS devices
• Self-hosted and open-source

Use cases

• Hands-free voice commands on Android
• Private offline voice assistant for Wear OS
• Self-hosted AI assistant without cloud services
• Customizable wake word activation
• System-level assistant integration

README excerpt

# WakeHermesClaw for Android 🦞 > **A native Android voice client for OpenClaw and Hermes Agent.** > > WakeHermesClaw is the successor to *OpenClaw Assistant*. It keeps every > OpenClaw feature you already have — wake word, Voice Overlay, Gateway > + HTTP backends, Wear OS, on-device node capabilities, continuous > conversation — and adds first-class support for **Hermes Agent** as a > peer backend that can be configured side-by-side with OpenClaw. > > **Supported backends** (configure any combination, pick one as primary): > - OpenClaw Gateway (WebSocket, pairing, QR, TLS) > - OpenClaw HTTP (OpenAI-compatible chat) > - Hermes API Server (`/v1/chat/completions` streaming + `/v1/runs` Runs API) > > **Mobile Bridge (optional, off by default).** WakeHermesClaw can expose a > bearer-token-protected local HTTP service that lets Hermes reach a > curated set of Android capabilities. See > [`docs/hermes-mobile-bridge.md`](docs/hermes-mobile-bridge.md) and > [`integrations/hermes-mobile-bridge/`](integrations/hermes-mobile-bridge/). > > **Migration.** Existing OpenClaw Assistant installs upgrade in place > (`applicationId` unchanged); the first launch silently migrates the > previous Gateway / HTTP settings into the new multi-backend repository > and marks the existing setup as **Primary**. Wake word, HotwordService, > Voice Overlay, Wear OS, and node capabilities continue to target the > Primary backend. > > **Hermes setup in 30 seconds.** Run `hermes gateway` with the API > server enabled (default port `8642`), bind it to your LAN/VPN, > generate an API key, and add it in **Settings → Backends → Add Hermes > API Server**. WakeHermesClaw accepts both `http://host:8642` and > `http://host:8642/v1`. Authentication uses `Authorization: Bearer > <key>`; the default model name is `h

Topics