Claude Code already sees your working tree. Claude Code Nano Banana is useful when the next still should start from a file you already have. Nano Banana 2 is the edit model; Claude Code is the file and brief layer.
- Claude Code can open the source PNG and the nearby copy.
- Nano Banana 2 is selected because identity must survive.
- The result is written beside the original, not pasted as a description.
- A failed edit is a missing source path until proven otherwise.
Media.io fit: Media.io CLI exposes Nano Banana 2 through the Claude Code plugin and skills. Claude Code owns paths; Media.io returns the edited still.
In this article
What Nano Banana 2 Is For Inside Claude Code
Use Nano Banana in Claude Code when a product, face, or layout must stay. The model should change scene or styling, not invent a new object.
If there is no source worth keeping, GPT Image 2 is usually the better first model.
- Pass the real source path.
- Say what must stay.
- Write to a new filename until approval.
- Keep the original in git.
Set Up the Claude Code Image Plugin Before You Prompt
A Claude Code image plugin that is not installed will look like Claude "cannot generate images." That is a setup problem.
Use the complete Claude Code setup prompt: CLI, marketplace plugin, skills, browser auth, and INSTALL-HELP.
Run the First Edit Against a File in the Working Tree
The first nano banana Claude Code job should change one thing on a real PNG. If that fails, stop and fix connection.
| Claude Code already has | Call | Avoid |
| A source file to keep | Nano Banana 2 | Describing the object instead of passing the file |
| No source | GPT Image 2 | Forcing an edit model to invent identity |
When you use Nano Banana in Claude Code this way, the session can immediately open the output path.
Hand the File Back Into the Repo
Claude Code should not leave untitled downloads. Use the project image folder and a stem that includes the shot.
- Identify the source file.
- Write the allowed change.
- Generate to a new name.
- Open the file in the session for QA.
Number variants. Do not overwrite the source until a human says so.
Use Media.io CLI so Claude Code Can Call Nano Banana 2
After Media.io CLI and the Claude plugin/skills are connected, Claude Code can send the source image to Nano Banana 2. Keep Claude Code image generation as the broader setup page.
If You Want Claude Code to Set Media.io Up for You
Copy This Complete Setup Prompt into Claude Code
Show a real terminal or agent session, the returned output path or status, and the generated result.
If Claude Returns a Prompt Instead of an Image, Fix Tools First
That symptom is usually missing plugin, skills, or auth, not a weak brief.
| Symptom | First check |
| Text plan, no pixels | Plugin/skills/auth |
| New object | Source path missing |
| Wrong folder | Destination not explicit |
Repair setup, then rerun the same edit row.
FAQs About Claude Code Nano Banana
-
Can I use Nano Banana in Claude Code natively?
Claude Code can plan the edit and choose files, but pixels come from a connected model such as Nano Banana 2 through Media.io CLI. -
What is Nano Banana 2 best at in Claude Code?
Source-image editing where product identity, character, or layout should survive. -
How do I use Nano Banana in Claude Code with no source file?
You can still generate, but GPT Image 2 is usually the better first model when nothing needs to be preserved. -
Why does Claude Code return a prompt instead of an image?
The image tool is probably not connected. Check CLI, plugin, skills, and browser authentication. -
Where should the edited file go?
Beside the source or in the project image folder, with a new name until approval. -
Do I need a separate Nano Banana tab?
No. After setup, Claude Code can call the model in-session.
Use Nano Banana 2 When Claude Code Already Has the Source
If the working tree contains the asset you must keep, Nano Banana 2 is the Claude Code image model to call. Fix tools before you rewrite the brief.
