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

• Repository: openclaw/openclaw
• Author: wiliyam
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/59926

Description (problem / solution / changelog)

Summary

• Problem: Groq (and potentially other bundled audio providers like Deepgram) are silently unavailable even when correctly configured via tools.media.audio.models, producing "Media provider not available: groq" on every transcription attempt.
• Why it matters: Groq Whisper STT is completely broken for any user whose active gateway registry already contains other media understanding providers (e.g. OpenAI for image understanding). The early-return in resolvePluginCapabilityProviders caused the bundled-compat load path to be skipped entirely.
• Root cause: resolvePluginCapabilityProviders checked activeProviders.length > 0 and returned immediately — but activeProviders is the full active registry across all capability types, not just audio. So if OpenAI was loaded for image, groq was never loaded for audio.
• What changed: When a caller config is provided, always resolve via the compat-config path (which injects bundled providers like groq/deepgram via withBundledPluginEnablementCompat). Fall back to the active registry only when no cfg is provided or compat load yields nothing.
• What did NOT change: No config schema changes. No behavior change when no cfg is passed.

Change Type

• Bug fix

Scope

• Integrations

Linked Issue/PR

• Closes #59875
• Related #59502, #59437
• This PR fixes a bug or regression

Root Cause / Regression History

• Root cause: resolvePluginCapabilityProviders line 72 if (activeProviders.length > 0) return — early return skips the compat config load that injects bundled capability providers.
• Missing detection / guardrail: No test covered the case where the active registry has providers for capability A (image) but the request is for capability B (audio) with a bundled provider not in the startup registry.
• Prior context: The early return was introduced to prefer the active gateway registry when already populated; this optimization broke the fallback for capability-specific providers.
• Why this regressed now: PR #3dbd81e610 restored bundled compat loading in resolveCapabilityProviderConfig but left the early-return guard intact, so the compat path was only reached when the active registry was completely empty.

Regression Test Plan

• Coverage level: Unit test
• Target test: src/plugins/capability-provider-runtime.test.ts (if exists) or src/media-understanding/runner.ts test suite
• Scenario: active registry contains openai (image), user requests groq (audio) — groq must be returned
• Existing test: extensions/groq/plugin-registration.contract.test.ts covers registration; gap is in resolvePluginCapabilityProviders multi-provider scenario

User-visible / Behavior Changes

Groq Whisper audio transcription now works when tools.media.audio.models: [{"provider": "groq", "model": "whisper-large-v3-turbo"}] is configured and GROQ_API_KEY is set, even when other media providers (OpenAI, Google) are already loaded in the gateway registry.

Security Impact

• New permissions/capabilities? No
• Secrets/tokens handling changed? No
• New/changed network calls? No (Groq was already being called when active registry was empty)
• Command/tool execution surface changed? No
• Data access scope changed? No

Repro + Verification

Environment

• OpenClaw 2026.4.1, Amazon Linux 2023
• GROQ_API_KEY set, tools.media.audio.enabled: true

Steps

1. Set tools.media.audio.models: [{"provider": "groq", "model": "whisper-large-v3-turbo"}]
2. Enable OpenAI for image understanding (or any other media provider)
3. Send voice note via WhatsApp/Telegram
4. Before: audio understanding failed: Error: Media provider not available: groq
5. After: Groq transcribes successfully

Expected

Groq is loaded and audio is transcribed

Actual (before fix)

Media provider not available: groq — provider silently missing from registry

Evidence

• Issue #59875 reports exact error: "audio understanding failed: Error: Media provider not available: groq"
• Code trace: resolvePluginCapabilityProviders → activeProviders.length > 0 early-return → compat load skipped → groq not in registry → line 521 in runner.entries.ts throws

Human Verification

• Traced the code path manually through resolvePluginCapabilityProviders → resolveRuntimePluginRegistry → resolveCapabilityProviderConfig → withBundledPluginEnablementCompat
• Confirmed the early-return bypasses compat loading when activeProviders.length > 0
• Did NOT verify in a live environment with GROQ_API_KEY (no live Groq key available)

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.

Compatibility / Migration

• Backward compatible? Yes — behavior only changes when cfg is provided and compat load succeeds
• Config/env changes? No
• Migration needed? No

Risks and Mitigations

• Risk: compat load is slightly heavier than the active registry path
  • Mitigation: resolveRuntimePluginRegistry uses getCompatibleActivePluginRegistry cache internally; most calls will hit cache and be cheap

AI-assisted: Prepared with Claude via OpenClaw. Root cause identified by code trace through capability-provider-runtime.ts, bundled-compat.ts, and runner.entries.ts. Verified by contributor.

Changed files

• docs/channels/slack.md (modified, +34/-1)
• src/plugins/capability-provider-runtime.ts (modified, +20/-7)

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

• Repository: openclaw/openclaw
• Author: yxjsxy
• State: closed | merged: True
• Link: https://github.com/openclaw/openclaw/pull/59982

Description (problem / solution / changelog)

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

Changed files

• CHANGELOG.md (modified, +1/-0)
• extensions/deepgram/openclaw.plugin.json (modified, +1/-0)
• extensions/groq/openclaw.plugin.json (modified, +1/-0)

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

• Repository: openclaw/openclaw
• Author: zigash
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/60392

Description (problem / solution / changelog)

Problem

After the plugin activation refactor (f911bbc353), bundled media provider plugins like Groq silently stop working even when:

• GROQ_API_KEY is set in env
• tools.media.audio.models explicitly references provider: groq

The auto-enable logic handles channel plugins and web search/fetch providers, but never checks tools.media config for media understanding providers. Groq (and likely Deepgram) fall through to "bundled, disabled by default."

Multiple users affected since 2026.3.31 / 2026.4.x.

Fixes #59875, fixes #59502, fixes #54695, fixes #59437

Solution

• Add collectConfiguredMediaProviderIds() to scan all tools.media.{models,audio,image,video}.models entries for provider references
• Add resolveMediaUnderstandingProviderPluginIds() to map provider IDs → plugin IDs (bundled snapshots + third-party manifests via mediaUnderstandingProviders contract)
• Wire both into resolveConfiguredPlugins() so referenced media providers get auto-enabled
• Update configMayNeedPluginAutoEnable() and configMayNeedPluginManifestRegistry() guards
• Add "media-provider-configured" kind to PluginAutoEnableCandidate union type

Review feedback addressed (v2)

• P1 (greptile): Normalize bundled provider IDs via normalizeMediaProviderId() before map insertion to avoid alias mismatches (e.g. "gemini" → "google")
• P1 (codex): Move media provider check outside the channels-only early return in configMayNeedPluginManifestRegistry so third-party media plugins can resolve without channel config
• P2 (greptile): Skip registry loading for bundled-only media providers via isBundledMediaProviderId() gate

Testing

• Added tests for bundled (Groq) and third-party media provider plugin auto-enable
• Manually verified: Groq audio transcription works with only tools.media.audio.models: [{ provider: "groq" }] — no plugins.entries.groq.enabled: true workaround needed
• Existing tests pass: vitest run src/config/plugin-auto-enable.test.ts && vitest run src/plugins/providers.test.ts

AI-assisted

This PR was authored with AI assistance (Claude Opus 4.6). Fully tested locally (unit tests + manual Groq transcription verification on a dev OpenClaw instance). We understand what the code does — it extends the existing plugin auto-enable pattern to cover media understanding providers the same way it already covers channels, browser, and web search/fetch providers.

Changed files

• src/config/plugin-auto-enable.test.ts (modified, +64/-1)
• src/config/plugin-auto-enable.ts (modified, +95/-9)