Image Handling Issue

Bug Report: Image Handling Issue

Environment

• Codex CLI Version: v0.135.0
• Subscription: ChatGPT Go
• Model: GPT-5.5 (xhigh)
• Platform: Darwin 25.5.0 arm64 (macOS)
• IDE: Antigravity IDE
• Codex Doctor Report: Not available
• Uploaded Thread: 019e838c-d92d-7633-ba6d-8be4914e417a

Description

When I submit a prompt that references an image but do not explicitly attach or select one, Codex appears to access and process unrelated images from my local machine rather than requesting an image, using a placeholder, or proceeding without image input.

This behavior may result in incorrect output generation and raises privacy concerns because local images that were not intentionally provided may be inspected or considered during task execution.

Steps to Reproduce

1. Open Antigravity IDE with Codex.
2. Create a new task.
3. Enter a prompt that references an image (for example, "Create a landing page using the provided image").
4. Do not attach or select any image.
5. Submit the prompt.
6. Observe Codex's behavior.

Actual Behavior

• Codex appears to search through or process local images that were not explicitly attached to the task.
• The task proceeds as though image input was available.
• No prompt is shown requesting an image upload or image URL.
• No warning or error message is displayed.

Expected Behavior

When no image is explicitly attached or selected, Codex should:

• Process only the information provided in the prompt.
• Request an image upload or image URL if image input is required.
• Leave image placeholders empty when appropriate.
• Access only images that were explicitly attached or selected by the user.
• Never automatically scan or process unrelated local images.

Impact

• Incorrect output generation.
• Unexpected behavior when prompts reference images.
• Potential privacy concerns due to processing of unintended local files.
• Reduced confidence in file-selection boundaries.

Additional Information

• The issue occurs immediately after task submission.
• No image was intentionally attached or selected.
• The behavior appears reproducible with multiple prompts that reference images.
• This may indicate that the image selection mechanism is searching local files instead of restricting itself to user-provided inputs.
• I have reviewed issue #24301. While related, my issue appears to concern image discovery/selection behavior rather than screenshots capturing the wrong application window.