Codex edits files in a way that is not picked up by "gulp.watch"/filesystem watcher

What version of Codex is running?

codex-cli 0.46.0

Which model were you using?

gpt-5-codex High

What platform is your computer?

Linux 6.12.10-76061203-generic x86_64 x86_64

What steps can reproduce the bug?

On a javascript repo of mine, I have an always-running process in a terminal pane that serves the dev server and watches for javascript changes to minify and output to the web directory, with a gulpfile:

// Task to minify all JS files
gulp.task('minify-js', function() {
  return gulp.src(['js/*.js'])
    .pipe(uglify())
    .pipe(gulp.dest('web/'));
});

// Task to watch JS files and run minify-js on changes
gulp.task('watch-js', function() {
  gulp.watch('js/*.js', gulp.series('minify-js'));
});

If I, as a person, modify a file in "js/foo.js", it gets automatically detected and the entire minification pass runs (and writes "web/foo.js", "web/bar.js", etc.) This has always "just worked(TM)"

With Claude Code and cursor-agent, whenever the agents modify "js/foo.js", the automatic minifier would pick it up right away.

However, I recently switched to Codex, and it seems like Codex is modifying those js files in a way that's somehow _not_ being picked up by "gulp.watch"

Am I misdiagnosing or is it possible Codex is using some mechanism to modify files that results in breaking a file change watcher? (I don't know how Gulp.watch internals work)

What is the expected behavior?

_No response_

What do you see instead?

_No response_

Additional information

_No response_