fix: add enabledByDefault to groq and deepgram media plugin manifests by yxjsxy · Pull Request #59982 · openclaw/openclaw

yxjsxy · 2026-04-03T01:19:57Z

Problem

The groq and deepgram plugin manifests were missing "enabledByDefault": true. Without this flag, both plugins are treated as bundled-but-disabled-by-default during gateway startup.

resolveRuntimePluginRegistry() loads without them. When buildProviderRegistry later needs to resolve audio providers, resolvePluginCapabilityProviders short-circuits to the active registry (skipping the compat path), so groq and deepgram are absent from the registry.

This caused the error in #59875:

audio understanding failed: Error: Media provider not available: groq

Even with GROQ_API_KEY / DEEPGRAM_API_KEY correctly configured, the plugin never loaded.

Root cause

resolvePluginActivationState in src/plugins/config-state.ts reaches this branch for groq/deepgram:

if (params.origin === 'bundled') {
  return { enabled: false, reason: 'bundled (disabled by default)' };
}

Because params.enabledByDefault is undefined (missing from manifest).

Fix

Add "enabledByDefault": true to both extensions/groq/openclaw.plugin.json and extensions/deepgram/openclaw.plugin.json, matching the pattern used by mistral and other audio/media providers.

Testing

All 1213 plugin tests pass (pnpm exec vitest run src/plugins/)
All 117 media-understanding tests pass (pnpm exec vitest run src/media-understanding/)
Pre-commit hook (tsgo + oxlint) passes

Fixes #59875

greptile-apps · 2026-04-03T01:20:52Z

Greptile Summary

Adds "enabledByDefault": true to the openclaw.plugin.json manifests for both the groq and deepgram bundled plugins, fixing a regression where both plugins were silently skipped during gateway startup (treated as disabled-by-default), causing media/audio provider resolution to fail even when the relevant API keys were configured.

Confidence Score: 5/5

This PR is safe to merge — it is a two-line targeted manifest fix with no logic changes.

The change is minimal (one field added to two JSON manifests), matches the established pattern used by all other bundled provider plugins, and directly addresses the documented failure path in config-state.ts. No logic, interface, or schema changes were introduced.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix: add enabledByDefault to groq and de..." | Re-trigger Greptile}

yxjsxy · 2026-04-03T01:21:25Z

Hey @vincentkoc — this is a small 2-line fix for the Groq/Deepgram STT regression (#59875). Both plugin manifests were missing "enabledByDefault": true, causing the bundled plugins to be silently skipped during gateway startup.

All tests pass (1213 plugin + 117 media-understanding). Would appreciate a review when you have a moment!

yxjsxy · 2026-04-03T21:24:20Z

Hi @vincentkoc — gentle ping on this one when you have a moment! 🙏

All CI checks are green and Greptile reviewed it at 5/5 confidence (safe to merge). It's a two-line targeted fix for the Groq/Deepgram bundled plugin regression (#59875) — no logic changes, just adding the missing enabledByDefault: true field to match the pattern used by all other bundled providers.

Would really appreciate a quick review!

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 openclaw#59875

@yxjsxy

…nclaw#59982) (thanks @yxjsxy)

obviyus

Reviewed latest changes; landing now.

obviyus · 2026-04-04T02:41:48Z

Landed on main.

Landed source commit: e96121f
Merge commit: 6d33c67

Thanks @yxjsxy.

@yxjsxy

…nclaw#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 openclaw#59875 * fix: enable groq and deepgram bundled media providers by default (openclaw#59982) (thanks @yxjsxy) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@yxjsxy

…nclaw#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 openclaw#59875 * fix: enable groq and deepgram bundled media providers by default (openclaw#59982) (thanks @yxjsxy) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@yxjsxy

…nclaw#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 openclaw#59875 * fix: enable groq and deepgram bundled media providers by default (openclaw#59982) (thanks @yxjsxy) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@yxjsxy

…nclaw#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 openclaw#59875 * fix: enable groq and deepgram bundled media providers by default (openclaw#59982) (thanks @yxjsxy) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@yxjsxy

…nclaw#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 openclaw#59875 * fix: enable groq and deepgram bundled media providers by default (openclaw#59982) (thanks @yxjsxy) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@yxjsxy

…nclaw#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 openclaw#59875 * fix: enable groq and deepgram bundled media providers by default (openclaw#59982) (thanks @yxjsxy) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@yxjsxy

…nclaw#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 openclaw#59875 * fix: enable groq and deepgram bundled media providers by default (openclaw#59982) (thanks @yxjsxy) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

openclaw-barnacle Bot added the size: XS label Apr 3, 2026

obviyus self-assigned this Apr 4, 2026

yxjsxy and others added 2 commits April 4, 2026 08:08

fix: enable groq and deepgram bundled media providers by default (ope…

e96121f

…nclaw#59982) (thanks @yxjsxy)

obviyus force-pushed the fix/groq-deepgram-plugin-manifest branch from d2b2bd8 to e96121f Compare April 4, 2026 02:40

obviyus approved these changes Apr 4, 2026

View reviewed changes

obviyus merged commit 6d33c67 into openclaw:main Apr 4, 2026
23 of 27 checks passed

This was referenced Apr 4, 2026

fix(media): always resolve bundled capability providers via compat config when cfg is provided #59926

Closed

fix(plugins): auto-enable media provider plugins referenced from tools.media #60392

Closed

Workz777 mentioned this pull request Apr 9, 2026

[Bug]: WhatsApp DM voice notes bypass STT pipeline entirely — audio arrives as raw <media:audio> with no transcription attempt #63677

Closed

darker0n mentioned this pull request Apr 9, 2026

Groq audio transcription sends JSON instead of multipart/form-data (v2026.4.9) #63851

Closed

clawsweeper Bot mentioned this pull request Apr 30, 2026

[Bug]: Discord voice conversations break after one successful back and forth #65687

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix: add enabledByDefault to groq and deepgram media plugin manifests#59982

fix: add enabledByDefault to groq and deepgram media plugin manifests#59982
obviyus merged 2 commits into
openclaw:mainfrom
yxjsxy:fix/groq-deepgram-plugin-manifest

yxjsxy commented Apr 3, 2026

Uh oh!

greptile-apps Bot commented Apr 3, 2026

Uh oh!

yxjsxy commented Apr 3, 2026

Uh oh!

yxjsxy commented Apr 3, 2026

Uh oh!

obviyus left a comment

Uh oh!

Uh oh!

obviyus commented Apr 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

yxjsxy commented Apr 3, 2026

Problem

Root cause

Fix

Testing

Uh oh!

greptile-apps Bot commented Apr 3, 2026

Greptile Summary

Confidence Score: 5/5

Uh oh!

yxjsxy commented Apr 3, 2026

Uh oh!

yxjsxy commented Apr 3, 2026

Uh oh!

obviyus left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

obviyus commented Apr 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants