openclaw - 💡(How to fix) Fix image_generate: No image-generation provider registered for google after 2026.3.23-2 update [2 comments, 2 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#53761Fetched 2026-04-08 01:23:44
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
commented ×2closed ×1locked ×1subscribed ×1

After updating to 2026.3.23-2, the image_generate tool fails with:

No image-generation provider registered for google

The same config worked correctly on the previous version. Gateway restarts do not resolve the issue.

Root Cause

After updating to 2026.3.23-2, the image_generate tool fails with:

No image-generation provider registered for google

The same config worked correctly on the previous version. Gateway restarts do not resolve the issue.

Code Example

No image-generation provider registered for google
RAW_BUFFERClick to expand / collapse

Bug Report

Version: 2026.3.23-2 (7ffe7e4)

Summary

After updating to 2026.3.23-2, the image_generate tool fails with:

No image-generation provider registered for google

The same config worked correctly on the previous version. Gateway restarts do not resolve the issue.

Config (sanitized)

models.providers.google is configured with api: "google-generative-ai", a valid baseUrl, apiKey, and a models array containing the image preview model IDs.

agents.defaults.imageGenerationModel.primary is set to google/gemini-3.1-flash-image-preview.

The config matches the current documented schema exactly.

Expected Behavior

image_generate resolves the google provider and generates an image.

Actual Behavior

Runtime throws: No image-generation provider registered for google

Investigation Notes

  • openclaw plugins list shows the Google plugin as loaded
  • The bundled code still includes api.registerImageGenerationProvider(buildGoogleImageGenerationProvider())
  • Schema validation passes — models.providers.google is still valid
  • Suspect the active plugin registry may be reused in a stale state that's missing imageGenerationProviders, based on the resolvePluginImageGenerationProviders logic in pi-embedded-*.js
  • Gateway restart does not resolve the issue

Steps to Reproduce

  1. Configure models.providers.google with api: "google-generative-ai" and a valid image model ID
  2. Set agents.defaults.imageGenerationModel.primary: "google/gemini-3.1-flash-image-preview"
  3. Update to 2026.3.23-2 and restart gateway
  4. Call image_generate tool

Additional Context

The 2026.3.22 changelog mentions standardizing the stock image path on image_generate and removing the bundled nano-banana-pro skill wrapper. This may be related.

extent analysis

Fix Plan

To resolve the No image-generation provider registered for google issue, we need to ensure the Google image generation provider is properly registered. Given the suspicion of a stale plugin registry, we'll focus on refreshing the plugin registry and ensuring the google-generative-ai API is correctly configured.

Steps to Fix:

  1. Verify Plugin Configuration: Confirm that models.providers.google is correctly set up with api: "google-generative-ai", a valid baseUrl, apiKey, and the models array containing the image preview model IDs.
  2. Refresh Plugin Registry: Manually reload the plugins to ensure the registry is updated. This can be done by running:
    openclaw plugins reload
  3. Check for Updates: Ensure all dependencies and plugins are up to date, as updates might have been made to address similar issues:
    openclaw update
  4. Explicitly Register Provider: If the issue persists, try explicitly registering the Google image generation provider in your configuration or startup script. This might involve adding a custom initialization script that calls api.registerImageGenerationProvider(buildGoogleImageGenerationProvider()) after the plugins have been loaded.

Example Code Snippet for Explicit Registration:

// Ensure this runs after plugins have been loaded
// This is a hypothetical example; actual implementation may vary based on the framework
api.on('pluginsLoaded', () => {
  const googleImageGenerationProvider = buildGoogleImageGenerationProvider();
  api.registerImageGenerationProvider(googleImageGenerationProvider);
});

Verification

After applying these steps, restart the gateway and attempt to use the image_generate tool again. If the issue is resolved, the tool should successfully generate an image using the Google provider.

Extra Tips

  • Regularly check the changelog for updates that might affect plugin compatibility or configuration.
  • Consider implementing a periodic task to reload plugins to prevent similar issues due to stale registries.
  • If problems persist, verify that the google-generative-ai API and the specified models are accessible and correctly configured.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix image_generate: No image-generation provider registered for google after 2026.3.23-2 update [2 comments, 2 participants]