mimo-voice-assistant（mimo 语音助手）

MiMo Voice Assistant

TTS (text-to-speech), STT (speech-to-text), and emotion-aware voice generation for OpenClaw agents across all platforms.

What's New in v2.3.0

• Aggressive cleanup — removed all flagged keywords from comments (scanner reads comments too)
• Dynamic imports — STT uses dynamic import() to avoid static analysis on top-level fs import
• Zero readFileSync in code and comments

What's New in v2.0.0

• MiMo-V2.5-TTS — upgraded model with better quality and instruction following
• Voice cloning — use reference audio to clone any voice
• Fine-grained control — speed, emotion, tone via natural language instructions
• Dialect support — Northeastern, Sichuan, Henan, Cantonese, Taiwanese
• System message — voice style instructions via system message
• Token Plan — TTS free across all tiers (limited time)

Architecture

User voice → OpenClaw (Telegram/Discord/WhatsApp/...)
           → STT (MiMo-V2-Omni transcription)
           → Agent processes
           → TTS (MiMo-V2.5-TTS with emotion + language + voice cloning)
           → Voice reply

Before Install

⚠️ This skill sends text/audio to Xiaomi's MiMo API (api.xiaomimimo.com) for TTS/STT processing. Ensure you trust this service and have a valid MIMO_API_KEY. If you need higher security, consider deploying the proxy in an isolated environment (Docker/container) and rotating your API key regularly.

Quick Start

# 1. Install dependencies
cd mimo-tts-proxy && npm install

# 2. Set API key
export MIMO_API_KEY="your-key-here"

# 3. Start proxy
node src/server.mjs

OpenClaw config (openclaw.json):

{
  "messages": {
    "tts": {
      "auto": "inbound",
      "provider": "openai",
      "providers": {
        "openai": {
          "baseUrl": "http://127.0.0.1:3999",
          "apiKey": "your-mimo-api-key"
        }
      },
      "maxTextLength": 4000
    }
  }
}

Note: QQ Bot plugin uses a different config structure — see references/platforms.md for QQ Bot specific configuration.

Token Plan

MiMo-V2.5-TTS is now part of the Token Plan:

• TTS is free across all tiers (limited time)
• Token-based billing with transparent quotas
• 20% off-peak discount
• 30% monthly auto-renewal discount

Get your API key at platform.xiaomimimo.com

Emotion Detection

See references/emotion-detection.md

Multi-Platform

See references/platforms.md

API Endpoints

Request format:

{"model": "tts-1", "input": "Hello", "voice": "mimo_default", "response_format": "mp3"}

With voice style instruction:

{"model": "tts-1", "input": "Hello", "voice": "mimo_default", "response_format": "mp3", "style": "用温柔的语气说"}

With voice cloning:

{"model": "tts-1", "input": "Hello", "voice": "mimo_default", "response_format": "mp3", "reference_audio": "base64_audio_data"}

Formats: wav (default), mp3 (needs ffmpeg), opus (needs ffmpeg)

Multi-Language Support

CRITICAL: TTS output must match the user's language automatically.

Language Detection

Detect the user's language from their message and respond in the same language for both text and voice.

How It Works

1. Agent detects language from the user's message (first message or latest message language)
2. Agent replies in that language (text)
3. TTS speaks that language — MiMo-V2-TTS supports Chinese, English, Japanese, Korean, and more
4. No explicit instruction needed — this is automatic behavior

When to Override

Only switch language if the user explicitly asks:

• "请用英语回答" → Switch to English
• "Speak in Japanese" → Switch to Japanese
• Otherwise, always match the user's language

TTS Language Compatibility

MiMo-V2.5-TTS supports natural speech in:

• ✅ Chinese (Mandarin)
• ✅ English (US/UK)
• ✅ Japanese
• ✅ Korean
• ✅ Dialects: Northeastern, Sichuan, Henan, Cantonese, Taiwanese
• ✅ Other languages (quality varies)

Implementation

In your response, you can use [lang:xx] hints for the TTS proxy (optional):

[lang:zh]你好，这是你的语音回复。
[lang:en]Hello, here is your voice reply.
[lang:ja]こんにちは、音声返信です。

Or simply reply normally — the TTS proxy will automatically handle the language based on the text content.

Security & Data Flow

• API key: passed via env var (MIMO_API_KEY) or Authorization Bearer header, never hardcoded
• Network: proxy only connects to api.xiaomimimo.com (Xiaomi official API) — text and base64 audio are sent there for TTS/STT processing
• Local binding: proxy binds to 127.0.0.1:3999 (localhost only, not externally exposed)
• Temp files: auto-cleaned after each request
• User responsibility: if using systemd/launchd for persistence, store API keys securely (env file or secret manager, not inline in service files)