codex - 💡(How to fix) Fix Codex App keeps a stale inline image in chat until the same file is rendered in the diff panel [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17315Fetched 2026-04-11 06:17:58
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.406.31014 (Build 1395)

What subscription do you have?

Not relevant

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

When an inline image in an assistant response is overwritten with new content at the same local path, the conversation can keep showing the old image.

I can reliably verify this by opening the diff panel and locating the same image there. Once the image renders in the diff panel, going back to the conversation makes the stale image update to the correct content.

This suggests the file on disk is already correct, but the chat view is holding a stale render/cache entry for the same image path.

What steps can reproduce the bug?

  1. Have Codex render a local image inline in an assistant response.
  2. Overwrite that image file with new content at the exact same path and filename.
  3. In the conversation, observe that the inline image still shows the old version.
  4. Open the diff panel and find the same image.
  5. Once it renders there, return to the conversation.
  6. The image in the chat now updates to the correct content.

What is the expected behavior?

The inline image in the conversation should refresh when the file contents change, even if the path stays the same.

Additional information

  • The path does not change; only the file contents change.
  • The diff panel can already render the correct updated image from the same path.
  • This looks like a chat-view-side cache/render invalidation issue for same-path images.
  • This may be a regression; I do not remember seeing this in earlier app versions.

extent analysis

TL;DR

The issue can likely be resolved by implementing a cache invalidation mechanism for inline images in the conversation view when the file contents change at the same path.

Guidance

  • Investigate the image rendering and caching logic in the conversation view to identify why the stale image is being displayed.
  • Verify that the diff panel's image rendering logic can be used as a reference to update the conversation view's image rendering.
  • Consider adding a file system watcher or a similar mechanism to detect changes to image files and invalidate the cache accordingly.
  • Review earlier app versions to confirm if this is a regression and identify potential changes that may have introduced the issue.

Example

No specific code snippet can be provided without more information about the Codex App's internal implementation.

Notes

The exact solution may depend on the specifics of the Codex App's architecture and image rendering mechanisms. Further investigation is needed to determine the best approach.

Recommendation

Apply a workaround by implementing a cache invalidation mechanism for inline images in the conversation view, as this is likely to resolve the issue without requiring a full version upgrade.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING