gpt-image-edit

We need to translate the given text from English to Vietnamese, preserving the name "gpt-image-edit" as instructed. The text describes an agent skill for editing images using OpenAI GPT Image 2 on RunComfy. We must not include any labels or extra commentary. The translation should be natural and accurate. Key points to preserve: product names (OpenAI GPT Image 2, ChatGPT Images 2.0, RunComfy, Nano Banana Edit, Flux Kontext, GPT Image 2 t2i), technical terms (endpoint, prompting patterns, schema, routing), and numbers (2, 2.0, 10). Also preserve the name "gpt-image-edit" if it appears in the source? The instruction says "Do not include the name unless it appears in the source text." The name "gpt-image-edit" is not in the provided <text>; it's only in the directory item type. So we should not add it. The text inside <text> does not contain "gpt-image-edit". So we just translate

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.

Thêm skills từ 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
Run any model on RunComfy from the command line. The `runcomfy` CLI is one binary, one auth, hundreds of model endpoints — image generation, image edit, video generation, image-to-video, lip-sync, face swap, video edit, inpainting, outpainting, extend, ControlNet, relight, upscale, LoRA training and more. Submit a request, poll for status, download the output. This skill teaches the agent how to install, authenticate, discover model schemas, invoke models, stream / poll / no-wait, script in...
creativemediaapi
image-to-video
runcomfy-com
Làm sống động bất kỳ hình ảnh tĩnh nào trên RunComfy — kỹ năng này là một bộ định tuyến thông minh, khớp ý định của người dùng với mô hình i2v phù hợp trong danh mục RunComfy. Chọn HappyHorse 1.0 I2V (Arena #1, âm thanh gốc, bả
creativevideomedia
flux-2-klein
runcomfy-com
Tạo hình ảnh với Flux 2 Klein (biến thể nhanh được chưng cất của Flux 2 từ Black Forest Labs) trên RunComfy — tích hợp sẵn các mẫu prompt đã được ghi chép của mô hình để kỹ năng đạt đầu ra sắc nét hơn so với prompt thông thường trên cùng mô hình. Ghi lại các điểm mạnh của Flux 2 Klein (độ trễ dưới giây, tạo kiểu thương hiệu đa tham chiếu, prompt ưu tiên chủ ngữ khai báo), chiến lược số bước (4–8 để lặp nhanh, ~25 để hoàn thiện), sự đánh đổi giữa biến thể 9B và 4B, và thời điểm chuyển hướng sang Flux 2 Pro /...
creativeimageresearch
ai-avatar-video
runcomfy-com
We need to translate the given text from English to Vietnamese, preserving the specified name "ai-avatar-video" and other technical terms. The instruction says to translate only the text inside <text>, and 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. So "RunComfy", "runcomfy CLI", "ByteDance OmniHuman", "Wan-AI Wan 2-7", "HappyHorse 1.0", "Seedance v2 Pro", "UGC", etc. should remain as is. Also "audio-driven", "full-body avatar", "mouth sync", "portrait", "t2v", "i2v", "in-pass audio", "multi-modal cinematic", "reference audio", "reference subject" are technical terms; we should keep them in English or find appropriate Vietnamese translations? The instruction says "preserve technical
videocreativemedia
nano-banana-edit
runcomfy-com
We need to translate the given text from English to Vietnamese, preserving the name "nano-banana-edit" and other technical terms. The instruction says to translate only the text inside <text>, and not include the name unless it appears in the source text. The name "nano-banana-edit" appears in the source? Actually the source has "nano-banana-edit" in the first line? Wait, the source text starts with "Edit images with Google Nano Banana 2 ..." and later mentions "Nano Banana Edit's strengths", "Nano Banana 2 t2i", "nano banana edit", etc. The name to preserve is "nano-banana-edit" (with hyphens). In the source, it appears as "Nano Banana Edit" (without hyphens) and "nano banana edit". But the instruction says "Name to preserve: nano-banana-edit". So we should keep that exact string if it appears. However, in the source text, it's written as "Nano Banana Edit" (capital
creativeimageapi
wan-2-7
runcomfy-com
We need to translate the given text from English to Vietnamese, 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 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. Translate the rest naturally. The text is a description of an agent skill. We need to output only the translation, no extra labels. Let's translate: "Generate text-to-video with Wan 2.7 (Wan-AI's flagship motion model) on RunComfy. Documents Wan 2.7's strengths (multi-reference conditioning, audio-driven lip-sync
creativevideomedia
lipsync
runcomfy-com
We need to translate the given text from English to Vietnamese, preserving the specified name "lipsync" and other technical terms like RunComfy, runcomfy CLI, ByteDance OmniHuman, Sync Labs sync v2 / Pro, Kling lipsync, Creatify lipsync. Also preserve URLs, numbers, etc. The instruction says to translate only the text inside <text>, and not include the name unless it appears in the source text. The name "lipsync" appears in the source text as "Lip-sync" at the beginning, so we should translate that as "Khớp môi" or similar? But the instruction says "Preserve product names, protocol names, URLs, numbers, and technical terms." "lipsync" is a technical term, but it's also the name to preserve. The instruction says "Name to preserve: lipsync" and "Do not include the name unless it appears in the source text." It appears as "Lip-sync" (capitalized, hyphenated). Should we preserve the exact form "Lip
creativevideomedia