openclaw/extensions/deepgram
Karl Yang 6d33c67c01
fix: enable groq and deepgram bundled media providers by default (#59982) (thanks @yxjsxy)
* fix: add enabledByDefault to groq and deepgram media plugin manifests

The groq and deepgram plugin manifests were missing the
enabledByDefault: true flag. Without this flag, both plugins are
treated as bundled-but-disabled-by-default, so resolveRuntimePluginRegistry
loads without them. When buildProviderRegistry later needs to resolve
audio providers, the active registry is used first (short-circuits
the compat path in resolvePluginCapabilityProviders), leaving groq
and deepgram absent from the registry.

This caused 'Media provider not available: groq' errors when users
configured tools.media.audio.models with groq or deepgram, even
with GROQ_API_KEY / DEEPGRAM_API_KEY set correctly.

The fix mirrors the pattern used by other audio/media-only providers
such as mistral, which already has enabledByDefault: true.

Fixes #59875

* fix: enable groq and deepgram bundled media providers by default (#59982) (thanks @yxjsxy)

---------

Co-authored-by: Ayaan Zaidi <hi@obviy.us>
2026-04-04 08:11:34 +05:30
..
audio.live.test.ts test(types): remove remaining testing barrel references 2026-04-03 23:03:02 +09:00
audio.test.ts test(deepgram): use direct audio test helpers 2026-04-03 21:32:47 +09:00
audio.ts refactor(providers): normalize transport policy wiring (#59682) 2026-04-02 22:54:34 +09:00
index.ts refactor(plugins): move remaining channel and provider ownership out of src 2026-03-22 19:13:25 -07:00
media-understanding-provider.ts refactor(plugins): move remaining channel and provider ownership out of src 2026-03-22 19:13:25 -07:00
openclaw.plugin.json fix: enable groq and deepgram bundled media providers by default (#59982) (thanks @yxjsxy) 2026-04-04 08:11:34 +05:30
package.json build: prepare 2026.4.1-beta.1 release 2026-04-01 15:09:19 +01:00