Codex does not monitor and thus not re-read files if they change externally
Resolved 💬 1 comment Opened Nov 13, 2025 by guidedways Closed Nov 13, 2025
What version of Codex is running?
v0.58.0-alpha.7
What subscription do you have?
Pro
Which model were you using?
gpt-5-codex-high
What platform is your computer?
macOS
What issue are you seeing?
Please see uploaded session
- My last prompt to codex was over 8 hours ago where it made a bunch of changes to a file.
- I later went over the code and manually made a large number of edits.
- I asked codex to compare this file with another file (
Task+Attachments.swift) for analysis - and I see the following, suggesting it only read the one file and not the one it last worked on:
• Explored
└ Read Task+Alarms.swift
• Comparing Task+Attachment and Task+Alarms (39s • esc to interrupt)
This is incorrect, it seems unlike Claude Code it does not monitor files on disk, does not realize they've changed and does not re-read even when it was asked to in subtle terms 'compare' (implying it should make sure it's read it).
What steps can reproduce the bug?
Uploaded thread: 019a7761-25de-7d72-8378-1d9bef74d758
What is the expected behavior?
Claude for instance monitors files for any change and will always re-read the portion / full file etc as needed if it's determined its version is stale. This is the correct expected behavior.
Additional information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗