OpenClaw Alexa Voice Proxy Enables Bidirectional Voice Interaction
openclaw-alexa-voice is a Node.js proxy that connects an Alexa Custom Skill to the OpenClaw gateway, enabling voice interaction with full access to tools like email, calendar, and finances. The system implements a three-tier response architecture to handle different types of queries efficiently.
Three-Tier Response System
The proxy categorizes responses into three paths based on complexity and processing time:
- Fast path (<1s) – Handles simple queries like time, date, and custom APIs
- Agent path (<12s) – Provides quick answers from AI memory
- Deferred path (<2min) – Processes complex queries asynchronously, then plays back via Home Assistant TTS on any speaker
How It Works
When a query requires tool access (email, web search, market data), Alexa responds with "Let me check" and closes the session. The proxy then sends the query to OpenClaw's main session with full tool access, waits up to 2 minutes, strips markdown formatting, and plays the response on any Echo or Sonos device via Home Assistant's Alexa Media Player integration.
Key Features
- Voice PIN authentication with 1-hour sessions
- Multi-speaker TTS routing to any Echo, Sonos, or speaker group
- Extensible fast-response system for custom APIs
- Telegram fallback if TTS fails
- Alexa request signature validation
- Rate limiting and audit logging
- Binds to localhost only for security
Technical Stack
The implementation uses Node.js for the proxy, an Alexa Custom Skill for voice interface, OpenClaw gateway WebSocket for communication, and Home Assistant for TTS playback. This approach allows developers to extend voice capabilities to their OpenClaw instances while maintaining security through local binding and authentication.
The project was inspired by Discussion #11154 and is available as open source for developers who want to add voice interaction to their OpenClaw setups. The three-tier system ensures responsive voice interactions while still allowing complex queries to leverage OpenClaw's full tool capabilities.
📖 Read the full source: r/openclaw
👀 See Also
Self-updating translation system for OpenClaw maintains domain glossaries automatically
A Python script wraps the Kimi2.5 API to translate .srt files while preserving block indices, timestamps, and segmentation. The system uses project profiles with glossary.json, style.md, and memory.jsonl files, and includes a cron job that scans official sources every 6 hours to update terminology.
Claude Code's File-Based Memory System: A Pragmatic Alternative to Vector DBs
Claude Code implements a file-based memory system using .md files with frontmatter metadata and a MEMORY.md index, avoiding vector databases and embedding pipelines by scanning files, building manifests, and using a small model to select relevant memories.
OpenClaw Outlook Add-in Connects Local Agent to Email Sidebar
A developer built an Outlook add-in that connects to a local OpenClaw Gateway via WebSocket, providing full agent access with tools and automations directly in the email sidebar. The tool reads selected emails as context, maintains per-email chat sessions, and works with Outlook Desktop and Web.
Engram: Open-source memory layer for Claude Code and MCP clients
Engram is an open-source memory layer that works as an MCP server with any client like Claude Code, Cursor, or Windsurf. It stores unlimited memories with semantic vector search, achieves 80% accuracy on LOCOMO benchmark, and uses about 800 tokens per query versus 5K+ for file-based approaches.