api_google_nano_banana2_image_edit references removed node GeminiNanoBanana2V2 (also widget order mismatch)

Open
  • Is something wrong?
#858 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
json
Domain
tooling

Research direction

Start with templates/api_google_nano_banana2_image_edit.json and reproduce the node-type output with the curl/python command from the issue. Compare its widgets_values order with the installed GeminiNanoBanana2 schema described in the report. Done means the template uses an installed node and validates successfully on Comfy Cloud without the reported node or value errors.

Written by the indexing model from the issue text.

Description

Bug: api_google_nano_banana2_image_edit template references removed node GeminiNanoBanana2V2

The template templates/api_google_nano_banana2_image_edit.json contains a node of type GeminiNanoBanana2V2, but the only node currently installed on Comfy Cloud is GeminiNanoBanana2 (no V2 suffix), with a different widget signature.

This is a top-30 template by usage (7,847 runs per the cloud search_templates listing) and currently fails on cloud with:

Workflow validation failed — unknown node type(s): "GeminiNanoBanana2V2"
Reproduction
curl -sS -L https://raw.githubusercontent.com/Comfy-Org/workflow_templates/main/templates/api_google_nano_banana2_image_edit.json \
  | python3 -c "import json,sys; d=json.load(sys.stdin); print({n.get('type') for n in d['nodes']})"
# {'GeminiNanoBanana2V2', 'LoadImage', 'SaveImage'}

vs. cloud's installed node (via the comfyui-cloud MCP search_nodes tool):

{"name": "GeminiNanoBanana2", "display_name": "Nano Banana 2", "category": "api node/image/Gemini", ...}
Note: also a parameter-shape mismatch, not just a name mismatch

Renaming GeminiNanoBanana2V2 → GeminiNanoBanana2 is not sufficient. The template's widgets_values use the old V2 schema; the current GeminiNanoBanana2 schema is different:

Current GeminiNanoBanana2 required widget order:

prompt, model, seed, aspect_ratio, resolution, response_modalities, thinking_level

After patching node type only, cloud rejects with:

"value_not_in_list" — aspect_ratio = "MINIMAL" (was meant for thinking_level)
"value_not_in_list" — response_modalities = "randomize" (control_after_generate value)
"value_not_in_list" — thinking_level = "IMAGE" (was meant for response_modalities)

So the template's widgets_values array is also in the old V2 order and needs to be re-mapped, or the V2 variant of the node needs to be reinstated on cloud.

Suggested fix

Either:

  1. Republish the template using the current GeminiNanoBanana2 node + correct widget order, or
  2. Restore GeminiNanoBanana2V2 as a still-installed compatibility alias on cloud.
Discovered during

comfy_cloud MCP smoke test round R001-popular-2026-05-11 (test-02-template-workflow-execution).

Dominant language
TypeScript
Stars
1.5k
Forks
270
Avg merge
7h 23m
Merged PRs (30d)
65

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Comfy-Org/workflow_templates

All issues in Comfy-Org/workflow_templates

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.