"messages": {
  "tts": {
    "auto": "always",
    "mode": "final",
    "provider": "minimax",
    "timeoutMs": 30000,
    "maxTextLength": 1500,
    "providers": {
      "minimax": {
        "apiKey": "REDACTED",
        "baseUrl": "https://api.minimaxi.com",
        "model": "speech-2.8-hd",
        "voiceId": "yinlang_official_20260317",
        "speed": 1.0,
        "vol": 1.0,
        "pitch": 0
      }
    },
    "modelOverrides": {
      "enabled": false
    }
  }
}What I expected
MiniMax should be available as a registered TTS provider, and /tts status should show it as configured/usable.
What actually happened
/tts status:
📊 TTS status
State: ✅ enabled
Provider: minimax (❌ not configured)
Text limit: 1500 chars
Auto-summary: on

Last attempt: ✅
Provider: microsoft
Fallback: minimax -> microsoft
Attempts: minimax -> openai -> elevenlabs -> microsoft
Attempt details: minimax:skipped(no_provider_registered), openai:failed(provider_error), elevenlabs:skipped(not_configured), microsoft:success(ok)

So MiniMax is skipped before any actual TTS request is made.
Additional diagnostics
Config validation
openclaw config validate
Output:
Config valid: ~/.openclaw/openclaw.json
MiniMax models are present
openclaw models list | rg -i minimax
Output:
minimax/MiniMax-M2.7-highspeed             text+image 200k     no    yes   fallback#1,configured
minimax/MiniMax-M2.1-highspeed             text       200k     no    yes   fallback#2
minimax/MiniMax-VL-01                      text       200k     no    yes   image,configured
bailian/MiniMax-M2.5                       text       977k     no    yes   configured
MiniMax plugin is loaded
openclaw plugins list | rg -i minimax
Output includes:
@openclaw/ minimax  openclaw  loaded  stock:minimax/index.js  2026.4.2
Notes
This does not look like a general MiniMax auth/config problem, because MiniMax models are already available in models list and the stock MiniMax plugin is loaded.
It looks specifically like the MiniMax speech/TTS provider is not being registered, even though the MiniMax provider/plugin is present.
Possible regression area
Maybe something in:
MiniMax bundled plugin capability registration
TTS provider registry plugin discovery
CN base URL handling for MiniMax speech provider
distinction between text provider availability vs speech provider availability


### Steps to reproduce

Reproduction
1. Configure MiniMax provider so MiniMax models appear in openclaw models list
2. Add the messages.tts.providers.minimax config shown above
3. Restart gateway
4. Run /tts status
5. Run /tts audio hello from minimax

comfig:

"messages": {
  "tts": {
    "auto": "always",
    "mode": "final",
    "provider": "minimax",
    "timeoutMs": 30000,
    "maxTextLength": 1500,
    "providers": {
      "minimax": {
        "apiKey": "REDACTED",
        "baseUrl": "https://api.minimaxi.com",
        "model": "speech-2.8-hd",
        "voiceId": "yinlang_official_20260317",
        "speed": 1.0,
        "vol": 1.0,
        "pitch": 0
      }
    },
 }
}



### Expected behavior

MiniMax should register as a valid TTS provider and be used for /tts audio and message TTS.

### Actual behavior

MiniMax remains not configured in TTS, and fallback provider is used instead.

### OpenClaw version

2026.4.2

### Operating system

26.3.1 (25D2128)

### Install method

npm global

### Model

minimax-m2.7

### Provider / routing chain

openclaw -> minimax cn -> minimax m2.7

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell