From ec22ab9738b010ec1f35a84e4c4aaa3873eef060 Mon Sep 17 00:00:00 2001 From: Kunyao Liu Date: Thu, 18 Jun 2026 15:54:04 -0700 Subject: [PATCH] [skills] avoid duplicate generated image Markdown --- codex-rs/skills/src/assets/samples/imagegen/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/codex-rs/skills/src/assets/samples/imagegen/SKILL.md b/codex-rs/skills/src/assets/samples/imagegen/SKILL.md index 4285e5e641..615f276bff 100644 --- a/codex-rs/skills/src/assets/samples/imagegen/SKILL.md +++ b/codex-rs/skills/src/assets/samples/imagegen/SKILL.md @@ -38,7 +38,7 @@ Built-in save-path policy: - Save-path precedence in built-in mode: 1. If the user names a destination, move or copy the selected output there. 2. If the image is meant for the current project, move or copy the final selected image into the workspace before finishing. - 3. If the image is only for preview or brainstorming, render it inline; the underlying file can remain at the default `$CODEX_HOME/*` path. + 3. If the image is only for preview or brainstorming, present the image result exactly once through the active tool surface's native image presentation; the underlying file can remain at the default `$CODEX_HOME/*` path. Do not repeat that same output as a Markdown image, including after validation. A distinct locally post-processed artifact may still be linked with Markdown. - Never leave a project-referenced asset only at the default `$CODEX_HOME/*` path. - Do not overwrite an existing asset unless the user explicitly asked for replacement; otherwise create a sibling versioned filename such as `hero-v2.png` or `item-icon-edited.png`. @@ -110,7 +110,7 @@ Assume the user wants a new image unless they clearly ask to change an existing 11. For transparent-output requests, follow the transparent image guidance below: generate with built-in `image_gen` on a flat chroma-key background, copy the selected output into the workspace or `tmp/imagegen/`, run the installed `$CODEX_HOME/skills/.system/imagegen/scripts/remove_chroma_key.py` helper, and validate the alpha result before using it. If this path looks unsuitable or fails, ask before switching to CLI `gpt-image-1.5`. 12. Inspect outputs and validate: subject, style, composition, text accuracy, and invariants/avoid items. 13. Iterate with a single targeted change, then re-check. -14. For preview-only work, render the image inline; the underlying file may remain at the default `$CODEX_HOME/generated_images/...` path. +14. For preview-only built-in work, rely on the active tool surface's native image presentation. After optional validation, do not embed that same output path in Markdown or send another image presentation. A distinct locally post-processed artifact may still be linked with Markdown. 15. For project-bound work, move or copy the selected artifact into the workspace and update any consuming code or references. Never leave a project-referenced asset only at the default `$CODEX_HOME/generated_images/...` path. 16. For batches or multi-asset requests, persist every requested deliverable final in the workspace unless the user explicitly asked to keep outputs preview-only. Discarded variants do not need to be kept unless requested. 17. If the user explicitly chooses or confirms the CLI fallback, then use the fallback-only docs for model, quality, size, `input_fidelity`, masks, output format, output paths, and network setup.