Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The Microsoft Edge TTS provider is not being registered on startup, resulting in TTS failures.

Steps to reproduce

1. Configure TTS with Microsoft Edge provider in openclaw.json
2. Restart gateway
3. Attempt TTS conversion
4. Error: microsoft: no provider registered

Expected behavior

Microsoft Edge TTS provider should be registered and available when the gateway starts. TTS conversion requests should succeed without requiring any API key configuration, as Microsoft Edge TTS is a free service.

When provider: "microsoft" is configured:

• Provider should appear in the registered providers list
• TTS conversion should return audio output
• No "no provider registered" error should occur

Microsoft Edge TTS should work without API keys (free service).

Actual behavior

Actual Behavior

The Microsoft Edge TTS provider is not registered when the gateway starts. Any TTS request fails immediately with:

OpenClaw version

OpenClaw version: 2026.4.11

Operating system

Ubuntu 24.04

Install method

npm global

Model

ollama/llama3.1:latest

Provider / routing chain

openclaw lokal

Additional provider/model setup details

Issue persists through multiple version updates. Other providers (OpenAI, MiniMax) show different errors (quota/not configured), but Microsoft Edge simply shows "no provider registered" as if the module isn't loading at all.

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response