#Image

1 messages · Page 1 of 1 (latest)

dense ginkgo
#

When I'm asking my bot to generate an image using nano banana pro . It's says no response generated.

final sirenBOT
#

That “no response generated” usually means the run failed before OpenClaw had anything it could send back to Discord (tool error, missing key/binary, or Discord delivery error). For nano-banana-pro specifically, the most common causes are missing requirements (API key / uv / browser.enabled) or sandbox env not being passed through.

Here’s the fast triage:

  1. Grab version + logs while reproducing
  • openclaw --version
  • In one terminal: openclaw logs --follow
  • Re-run the exact “nano banana pro” request and copy the first obvious error/stacktrace from the logs.
  1. Confirm the skill is actually eligible (requirements)
    The bundled nano-banana-pro skill is gated on:

Minimum config example (~/.openclaw/openclaw.json):

# 
{
  browser: { enabled: true },
  skills: {
    entries: {
      "nano-banana-pro": {
        enabled: true,
        env: { GEMINI_API_KEY: "YOUR_KEY" }
      }
    }
  }
}
  1. If you’re running the agent sandboxed (Docker):
    skills.entries.*.env does not automatically propagate into the container. You must also pass it via:
  • agents.defaults.sandbox.docker.env (or per-agent override)
#

(That’s a very common “works on host, fails in sandbox” reason for “no response generated”.)

  1. Rule out Discord delivery issues
    Run: openclaw channels status --probe
    If Discord can’t upload files in that channel (missing “Attach Files”, etc.), you’ll see a 401/403/Forbidden-style error in logs.

If you paste:

  • your openclaw --version
  • the log snippet around the failed run (10–30 lines)
  • and whether the session is sandboxed

…I can tell you which of the above it is in one pass.

dense ginkgo
#

The skill was working previously

final sirenBOT
#

If it worked before and now you get “no response generated”, that almost always means something about the gateway runtime environment changed (restart, upgrade, switched from “run in terminal” → “run as service”, enabled sandboxing, changed config allowlists), so the nano-banana-pro skill is either:

  • no longer eligible/loaded (missing GEMINI_API_KEY, uv not on PATH, browser.enabled false, or bundled-skill allowlist blocking it), or
  • it’s loading but failing at runtime (401/429 from Gemini, tool failure, Discord upload permission failure).

What I’d check first (in this order):

  1. Did you restart the gateway / start it as a background service?
    If you previously had GEMINI_API_KEY in your shell env, and now it’s running under a service, that env var often disappears. Same for PATH (so uv vanishes). Fix is to put the key in ~/.openclaw/openclaw.json under skills.entries."nano-banana-pro".env (or apiKey) instead of relying on shell env.

  2. Paste the first real error from logs while reproducing

  • openclaw --version
  • openclaw gateway status
  • openclaw logs --follow (then trigger one image gen)

Look specifically for lines like:

  • missing GEMINI_API_KEY
#
  • uv: not found
  • browser.enabled requirement not met
  • 401/403/429 responses
  • Discord “Forbidden / Missing Permissions” when trying to upload
  1. If you turned on sandboxing (Docker) since it last worked:
    Host-injected skill env doesn’t automatically reach the container. You need to pass the key via agents.defaults.sandbox.docker.env.

If you drop just the relevant log snippet (10–30 lines) from the failing attempt (please redact any secrets), I can tell you which of these it is and what exact knob to change.

small viper
#

did you set up your skill yourself or was it a custom one? @dense ginkgo