gpt-image-edit

作成者: runcomfy-com

Edit images with OpenAI GPT Image 2 (the `/edit` endpoint of ChatGPT Images 2.0) on RunComfy — bundled with the model's documented prompting patterns so the skill gets sharper output than naive prompting against the same model. Documents GPT Image Edit's strengths (preservation language, multilingual in-image text editing, multi-reference up to 10 images, layout / typography precision), the schema, and when to route to Nano Banana Edit / Flux Kontext / GPT Image 2 t2i instead. Calls...

npx skills add https://github.com/runcomfy-com/skills --skill gpt-image-edit

GPT Image Edit — Pro Pack on RunComfy

runcomfy.com · Edit endpoint · Text-to-image sibling · GitHub

OpenAI GPT Image 2 — /edit endpoint (ChatGPT Images 2.0 image-to-image) on the RunComfy Model API. Strongest in its class at preserving identity through targeted edits and rewriting embedded text in any script (Latin, kana, CJK, Cyrillic, Arabic).

npx skills add agentspace-so/runcomfy-skills --skill gpt-image-edit -g

When to pick this model (vs siblings)

You wantUse
Edit multilingual / embedded text in imageGPT Image Edit
Identity preservation through translated headline variantsGPT Image Edit
Layout-precise edit (move headline, swap CTA, etc.)GPT Image Edit
Up to 10 reference imagesGPT Image Edit
Batch up to 20 images consistentlyNano Banana Edit
Single-shot precise local edit, source-fidelity-firstFlux Kontext
Generate from scratch with GPT Image 2sibling gpt-image-2 skill
Batch SKU galleries with stable identityNano Banana Edit

Prerequisites

  1. RunComfy CLInpm i -g @runcomfy/cli
  2. RunComfy accountruncomfy login opens a browser device-code flow.
  3. CI / containers — set RUNCOMFY_TOKEN=<token> instead of runcomfy login.

Endpoints + input schema

openai/gpt-image-2/edit

FieldTypeRequiredDefaultNotes
promptstringyesEdit instruction. Lead with preservation, end with the change.
imagesstring[]yesUp to 10 publicly-fetchable HTTPS URLs. First is primary; rest are auxiliary.
sizeenumnoautoauto (preserve input), 1024_1024 (1:1), 1024_1536 (2:3 portrait), 1536_1024 (3:2 landscape).

size=auto preserves the input ratio — strongly recommended unless the edit explicitly changes framing.

How to invoke

Single-ref preservation edit:

runcomfy run openai/gpt-image-2/edit \
  --input '{
    "prompt": "Keep the person'\''s face, pose, and brand mark unchanged. Replace the background with a soft warm-grey studio sweep and a gentle floor shadow.",
    "images": ["https://.../portrait.jpg"]
  }' \
  --output-dir <absolute/path>

Multilingual text rewrite (preserve everything except the headline):

runcomfy run openai/gpt-image-2/edit \
  --input '{
    "prompt": "Keep the photograph, layout, and brand mark exactly as in the input. Replace only the in-image headline. The new headline reads \"今日のおすすめ\" in bold Japanese kana, same position and font weight as before.",
    "images": ["https://.../poster-en.jpg"]
  }' \
  --output-dir <absolute/path>

Multi-ref composition:

runcomfy run openai/gpt-image-2/edit \
  --input '{
    "prompt": "Compose subject from image 1 into the room from image 2. Match the lighting and color palette of image 2. Keep image 1 subject identity (face, pose, clothing) unchanged.",
    "images": ["https://.../subject.jpg", "https://.../room.jpg"]
  }' \
  --output-dir <absolute/path>

Prompting — what actually works

Lead with preservation goals. Always: "Keep [face / pose / clothing / brand / framing] unchanged." Then state the change. The model honors what's stated up front.

Multilingual text — quote the characters, name the script. "the headline reads \"コーヒー\" in bold Japanese kana", "the label says \"АРОМА\" in Cyrillic, white on black", "the right-margin caption reads \"تخفيض\" in Arabic right-to-left". Don't paraphrase — quote.

Directional language for spatial edits. Concrete spatial scopes work: "move the headline from top-right to bottom-center", "remove the leftmost object only", "replace the watermark in the bottom-right corner".

Multi-ref numbering. When passing multiple images, refer to them by number: "subject from image 1, lighting from image 2, color palette from image 3". The model routes cues correctly.

Use size: "auto" to preserve input ratio. Only override when the edit explicitly changes framing (e.g. cropping a 16:9 to 1:1).

Anti-patterns:

  • Long compound edit instructions ("change A and B and C and D") → drift increases per added scope.
  • Missing preservation goals → model subtly rewrites the face / brand / framing.
  • Paraphrasing in-image text instead of quoting it → text comes out different.
  • Asking for size outside the 3 fixed values + auto → 422.

Where it shines

Use caseWhy GPT Image Edit
Multilingual ad localizationOne source asset → many language variants of the same headline
Brand-safe headline / CTA swapsLayout precision + preservation language hold the rest stable
Multi-ref composition (subject from one, scene from another)Numbered refs route cues correctly
Layout-precise repositioningDirectional language ("top-right to bottom-center") honored
Identity preservation across signage editsStrongest in class for face / brand preservation through targeted edits

Sample prompts (verified to produce strong results)

Background swap with full preservation (page example):

Turn the background into a bright minimal white-to-soft-gray studio
sweep with gentle floor shadow; add a large headline in-image that
reads "OPEN STUDIO" in a bold clean sans-serif, high contrast, centered;
keep the main person or product, pose, and face identity unchanged

Multilingual variant:

Keep the photograph, layout, lighting, and brand mark exactly as in the
input. Replace only the in-image headline.
The new headline reads "コーヒー" in bold Japanese kana, same position
and font weight as before.

Multi-ref composition:

Compose subject from image 1 into the kitchen from image 2.
Match the warm window light and color palette of image 2.
Keep subject identity (face, pose, clothing) from image 1 unchanged.

Limitations

  • size: 3 fixed values + auto — anything else 422s.
  • images: up to 10 — first is primary, rest are auxiliary cues.
  • Long compound prompts drift — split into multiple passes when needed.
  • For batch consistency across many SKU images, Nano Banana Edit (up to 20) is better.
  • Photorealism on portraits — Nano Banana Pro wins head-to-head.

Exit codes

codemeaning
0success
64bad CLI args
65bad input JSON / schema mismatch
69upstream 5xx
75retryable: timeout / 429
77not signed in or token rejected

Full reference: docs.runcomfy.com/cli/troubleshooting.

How it works

The skill invokes runcomfy run openai/gpt-image-2/edit with a JSON body matching the schema. The CLI POSTs to https://model-api.runcomfy.net/v1/models/openai/gpt-image-2/edit, polls the request, fetches the result, and downloads any .runcomfy.net/.runcomfy.com URL into --output-dir. Ctrl-C cancels the remote request before exit.

Security & Privacy

  • Token storage: runcomfy login writes the API token to ~/.config/runcomfy/token.json with mode 0600 (owner-only read/write). Set RUNCOMFY_TOKEN env var to bypass the file entirely in CI / containers.
  • Input boundary: the user prompt is passed as a JSON string to the CLI via --input. The CLI does NOT shell-expand the prompt; it transmits the JSON body directly to the Model API over HTTPS. No shell injection surface from prompt content.
  • Third-party content: image / mask / video URLs you pass are fetched by the RunComfy model server, not by the CLI on your machine. Treat external URLs as untrusted; image-based prompt injection is a known risk for any image-edit / video-edit model.
  • Outbound endpoints: only model-api.runcomfy.net (request submission) and *.runcomfy.net / *.runcomfy.com (download whitelist for generated outputs). No telemetry, no callbacks.
  • Generated-file size cap: the CLI aborts any single download > 2 GiB to prevent disk-fill from a malicious or runaway model output.

runcomfy-comのその他のスキル

video-inpainting
runcomfy-com
Region edits across video frames on RunComfy via the `runcomfy` CLI — remove an object that appears across many frames, clean up wires or watermarks, replace a region with matching motion. Routes across Wan 2-7 edit-video (default, prompt-driven region edits with spatial language), Lucy Edit Restyle (identity-stable region-aware restyle), and Seedream 4-0 edit-sequential (when treating the clip as a frame stack). Picks the right route based on whether the change is prose-driven,...
videocreativemedia
runcomfy-cli
runcomfy-com
We need to translate the given English text into Japanese. The text describes a CLI tool called runcomfy-cli. The instruction says to preserve the name "runcomfy-cli" but only if it appears in the source text. The source text mentions "runcomfy" and "runcomfy CLI" but not "runcomfy-cli" exactly. However, the directory item type is "agent skill" and the name to preserve is "runcomfy-cli". The instruction says "Do not include the name unless it appears in the source text." The source text has "runcomfy" and "runcomfy CLI". The name to preserve is "runcomfy-cli". Since it's not exactly in the source, we should not add it. But the instruction says "Translate only the text inside <text>." So we translate the entire content inside <text> without adding or removing anything except translation. The name "runcomfy-cli" is not inside the text, so we don't include it. However, the text includes "run
creativemediaapi
image-to-video
runcomfy-com
We need to translate the given English text into Japanese, preserving the name "image-to-video" and other technical terms like model names, URLs, etc. The instruction says: "Do not include the name unless it appears in the source text." The name "image-to-video" appears in the source? Actually, the source text starts with "Animate any still image on RunComfy — this skill is a smart router..." The name "image-to-video" is not explicitly in the source text; it's given as the directory item name. The instruction says "Do not include the name unless it appears in the source text." So we should not add "image-to-video" to the translation. Also, preserve product names: RunComfy, HappyHorse 1.0 I2V, Wan 2.7, Seedance 2.0 Pro, etc. Preserve technical terms: i2v, audio_url, lip-sync, multi-modal, etc. Translate the rest naturally into Japanese. Let's break down the text: "Animate
creativevideomedia
flux-2-klein
runcomfy-com
RunComfy上でFlux 2 Klein(Black Forest Labs製のFlux 2高速蒸留版)を使用して画像を生成します。このスキルには、モデルのドキュメント化されたプロンプトパターンがバンドルされており、同じモデルに対する単純なプロンプトよりもシャープな出力が得られます。Flux 2 Kleinの強み(サブ秒レイテンシ、マルチリファレンスブランドスタイリング、宣言的主語優先プロンプト)、ステップ数戦略(高速反復は4~8、仕上げは約25)、9Bと4Bバリアントのトレードオフ、Flux 2 Proへのルーティングのタイミングなどを解説しています。
creativeimageresearch
ai-avatar-video
runcomfy-com
We need to translate the given English text into Japanese, preserving the specified name "ai-avatar-video" and other technical terms. The instruction says: "Translate only the text inside <text>. Do not include the name unless it appears in the source text." The name "ai-avatar-video" does not appear in the source text, so we don't include it. We must preserve product names, protocol names, URLs, numbers, technical terms. No extra commentary. The text describes creating AI avatar videos using runcomfy CLI, listing models: ByteDance OmniHuman, Wan-AI Wan 2-7, HappyHorse 1.0, Seedance v2 Pro. Also mentions user intents. We need to translate naturally into Japanese, keeping terms like "runcomfy CLI", "ByteDance OmniHuman", "Wan-AI Wan 2-7", "HappyHorse 1.0", "Seedance v2 Pro", "audio_url", "Arena #1 t2v / i2v", "U
videocreativemedia
nano-banana-edit
runcomfy-com
We need to translate the given English text into Japanese, preserving the name "nano-banana-edit" and other technical terms. The instruction says: "Translate only the text inside <text>. Do not include the name unless it appears in the source text." The name "nano-banana-edit" appears in the source text? Actually, the source text mentions "Nano Banana Edit" and "nano banana edit" but not exactly "nano-banana-edit". However, the directory item type is "agent skill" and the name to preserve is "nano-banana-edit". The instruction says "Do not include the name unless it appears in the source text." So we should not add it if not present. But the source text has "Nano Banana Edit" (capitalized) and "nano banana edit" (lowercase). We should preserve those as they appear. Also preserve "RunComfy", "Google Nano Banana 2", "GPT Image 2 edit", "Flux Kontext", "Nano Banana 2 t2
creativeimageapi
wan-2-7
runcomfy-com
We need to translate the given English text into Japanese, preserving the name "wan-2-7" and other technical terms. The instruction says: "Translate only the text inside <text>. Do not include the name unless it appears in the source text." The name "wan-2-7" appears in the source text, so we should keep it as is. Also preserve "RunComfy", "Wan-AI", "HappyHorse 1.0", "Seedance 2.0", "Kling", "LTX 2", "runcomfy run wan-ai/wan-2-7/text-to-video", "CLI", "audio_url", etc. No extra commentary. Just a direct translation. Let me translate paragraph by paragraph. First sentence: "Generate text-to-video with Wan 2.7 (Wan-AI's flagship motion model) on RunComfy." -> "RunComfy上でWan 2.7(Wan-AIの主力モーションモデル)を使用して
creativevideomedia
lipsync
runcomfy-com
Lip-sync a face to a specific audio track on RunComfy via the `runcomfy` CLI. Routes across ByteDance OmniHuman (audio-driven full-body avatar from a portrait + audio), Sync Labs sync v2 / Pro (state-of-the-art mouth sync onto a video), Kling lipsync (audio-to- video and text-to-video with synced speech), and Creatify lipsync. The skill picks the right endpoint for the user's actual intent — portrait still + audio (avatar-style), source video + audio (mouth- swap on existing footage), or...
creativevideomedia