Bug: image_gen success did not create a new accessible generated image file

Bug: image_gen success did not create a new accessible generated image file

Environment

• OS: Windows
• Workspace: D:\Project\P2
• Codex date/time: 2026-06-18 KST
• Tool path expected by system message:

C:\Users\Youngho\.codex\generated_images\...

What happened

I asked Codex to generate a puppy image and place it under the project tmp folder.

The image_gen tool was invoked for a puppy image, but when Codex searched the default generated image directory, the newest PNG was still an older fantasy village image:

C:\Users\Youngho\.codex\generated_images\019ed90a-9fc3-7452-8585-082ae8b53167\ig_0108d860a7e23a15016a3377da24bc8191841d6c426dabc1cc.png

Copying the "latest" generated PNG into:

D:\Project\P2\tmp\sample-puppy-imagegen-test.png

resulted in the wrong image: a fantasy village, not a puppy.

A second image_gen call also did not produce a new visible PNG under C:\Users\Youngho\.codex\generated_images.

Expected behavior

After a successful image_gen call, Codex should either:

• save the newly generated image under $CODEX_HOME/generated_images/..., or
• return the exact generated file path to the agent.

Actual behavior

The agent had no accessible new generated file path. The latest filesystem artifact remained stale, so the agent copied an unrelated previous image.

Impact

When a user asks Codex to generate an image and place it in a project folder, Codex may silently copy an older unrelated image. This makes image generation path tests unreliable.

Workaround used

Codex replaced the bad copied file with an existing local tmp/sample-puppy.png, but that was not the newly generated image.