Building a Voice Assistant with OpenClaw, Alexa, and Local LLM

A developer shared their implementation of a voice-first assistant that uses OpenClaw as the AI agent backbone, integrated with Alexa for voice interaction and a local LLM for cost-effective query handling.
How It Works
The system is triggered by saying "Alexa, open Lucy" to a custom Alexa skill. Queries are processed through a four-tier routing system:
- Fast path (0ms): Handles time, date, and hardcoded responses
- Ollama local LLM (<1s): Uses Qwen 2.5 3B for general knowledge queries, running on a Mac Mini with Apple Silicon
- Claude agent (5-12s): Handles personal context, memory, and complex reasoning
- Deferred + tools (up to 2min): Manages email, web search, and database queries via Home Assistant TTS
Responses return to the same Alexa device that initiated the query, auto-detected via Home Assistant's last_called feature. The system uses Piper TTS on Home Assistant for neural Spanish voice output on Sonos speakers and can deliver morning briefings with market data, calendar information, and business metrics.
Technical Stack
- OpenClaw: AI agent backbone supporting Telegram, Alexa, and voice interfaces
- Alexa Custom Skill: Node.js proxy with PIN authentication and session chaining
- Ollama + Qwen 2.5 3B: Local LLM providing ~0.5s responses
- Home Assistant: Integrates Alexa Media Player, Piper TTS, and device routing
- Piper TTS: Neural Spanish voice for Sonos speakers
Key Implementation Details
The developer found that using a local LLM saves approximately 80% of API costs for simple questions that don't require Claude. However, they noted that local models "hallucinate freely" and added a bypass filter for business and financial queries.
Alexa speech recognition was identified as the bottleneck, with AMAZON.SearchQuery and multiple sample utterances helping improve accuracy. Authentication uses userId rather than sessionId since Alexa generates new sessions for each invocation. The developer persists authentication to file because in-memory Maps don't survive proxy restarts.
The proxy code is available as open source: openclaw-alexa-voice. Future plans include wake word detection ("Hey Lucy"), smart home control, and presence-based speaker routing.
📖 Read the full source: r/openclaw
👀 See Also

OpenClaw Agent Implements Autonomous Self-Improvement Loop with Nightly Dream Cycles
An OpenClaw user has configured their agent to run a nightly 'dream cycle' that scans AI research, reflects on performance, and implements safe improvements autonomously. The cycle costs approximately $0.40 per night using model routing with Haiku for scanning and Opus for judgment.

Pioneering OpenClaw: Revolutionizing Large Corporate Workflows
Explore how OpenClaw is being deployed in large corporate settings, enhancing automation and efficiency in complex workflows. This discussion highlights key benefits and user experiences.

Agent Jam: AI Agents Collaborate on Godot Game Jam via GitHub
Agent Jam is a game jam where AI agents build a web game in Godot 4.4 on GitHub without human-written code. The project uses GitHub issues for design discussions, CI validation for PRs, and requires games to be web-playable via Godot HTML5 export.

Running OpenClaw locally with Jetson Nano and gaming laptop using Ollama
A developer set up OpenClaw to run locally using a Jetson Nano and a 2022 MSI gaming laptop with Qwen 3.5 9B via Ollama, implementing wake-on-LAN for power efficiency and hybrid routing to OpenAI for complex tasks.