Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: Microsoft TTS provider not registered in 2026.4.5 [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62117•Fetched 2026-04-08 03:08:50
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
kof2023kof2023
Participants
kof2023kof2023
Timeline (top)
labeled ×2cross-referenced ×1

TTS fails with 'microsoft: no provider registered' error even though node-edge-tts is installed

Error Message

TTS fails with 'microsoft: no provider registered' error even though node-edge-tts is installed TTS conversion fails with error: 'microsoft: no provider registered; openai: not configured; minimax: not configured; vydra: not configured'

Root Cause

TTS fails with 'microsoft: no provider registered' error even though node-edge-tts is installed

Fix Action

Fixed

PR fix notes

PR #62197: fix(plugins): merge compat providers with active runtime

Description (problem / solution / changelog)

Summary

  • fix runtime capability resolution so compat-loaded providers are still considered when the active registry is only partial
  • preserve already-active providers instead of replacing them when config-specific compat loading is needed
  • add regression coverage for TTS provider lookup on a partially populated active registry

Root cause

resolvePluginCapabilityProviders() returned the active runtime providers immediately whenever any provider for that capability existed. In the failing case, the active registry already had openai, so a config asking for Microsoft TTS never loaded or merged the compat-shaped microsoft provider registry. That made getSpeechProvider("edge") fall through to microsoft: no provider registered.

Testing

  • node scripts/run-vitest.mjs run --config vitest.codex-standalone.config.ts src/plugins/capability-provider-runtime.test.ts src/tts/provider-registry.test.ts

Closes #62117

Changed files

  • src/plugins/capability-provider-runtime.test.ts (modified, +26/-6)
  • src/plugins/capability-provider-runtime.ts (modified, +20/-4)
  • src/tts/provider-registry.test.ts (modified, +30/-5)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

TTS fails with 'microsoft: no provider registered' error even though node-edge-tts is installed

Steps to reproduce

  1. Install OpenClaw 2026.4.5 via npm install -g openclaw@latest
  2. Configure TTS with provider: microsoft in ~/.openclaw/openclaw.json
  3. Run openclaw gateway start
  4. Attempt to use TTS via /tts command or message tool

Expected behavior

TTS should synthesize speech using Microsoft Edge TTS (node-edge-tts) and produce audio output

Actual behavior

TTS conversion fails with error: 'microsoft: no provider registered; openai: not configured; minimax: not configured; vydra: not configured'

OpenClaw version

2026.4.5

Operating system

Windows 11

Install method

npm global (npm install -g openclaw@latest)

Model

minimax-portal/MiniMax-M2.7

Provider / routing chain

openclaw (local gateway) -> microsoft edge TTS (node-edge-tts)

Additional provider/model setup details

Config used: { "messages": { "tts": { "auto": "always", "provider": "microsoft", "providers": { "microsoft": { "enabled": true, "voice": "es-ES-AlvaroNeural", "lang": "es-ES", "outputFormat": "audio-24khz-48kbitrate-mono-mp3" } } } } }

node-edge-tts is confirmed installed at: openclaw/node_modules/node-edge-tts The module loads correctly in Node.js but OpenClaw gateway does not register it as a provider.

Logs, screenshots, and evidence

Impact and severity

Affected: All users relying on Microsoft TTS (free, no API key required) Severity: Annoying (blocks voice feature) Frequency: Always (100% reproducible) Consequence: TTS text-to-speech does not work at all with Microsoft provider

Additional information

No response

extent analysis

TL;DR

The issue can likely be resolved by ensuring the node-edge-tts module is properly registered as a provider in the OpenClaw configuration.

Guidance

  • Verify that the node-edge-tts module is correctly installed and loaded by checking the openclaw/node_modules directory and the Node.js module loading process.
  • Check the OpenClaw configuration file (~/.openclaw/openclaw.json) to ensure that the microsoft provider is correctly configured and enabled.
  • Investigate the OpenClaw gateway startup process to determine why the node-edge-tts module is not being registered as a provider, despite being installed and loaded correctly.
  • Consider checking the OpenClaw documentation or source code to see if there are any specific requirements or constraints for registering custom providers.

Example

No code snippet is provided as the issue does not imply a specific code-related fix.

Notes

The issue may be related to a configuration or registration issue within OpenClaw, rather than a problem with the node-edge-tts module itself. Further investigation into the OpenClaw configuration and startup process is needed to determine the root cause.

Recommendation

Apply workaround: Check the OpenClaw configuration and startup process to ensure that the node-edge-tts module is properly registered as a provider, as this is the most likely cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

TTS should synthesize speech using Microsoft Edge TTS (node-edge-tts) and produce audio output

#api#dependency conflict#environment setup#docker error#permission error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING