The summary message generation without `git` and files collection
Resolved 💬 2 comments Opened Oct 29, 2025 by oneslash Closed Nov 11, 2025
What feature would you like to see?
Currently, Codex at the end of it's work, in order to create a summary message, starts re-reading files, and running git command to see changed files.
I believe this is one of the token burning contributors, and it makes the codex slower to execute. At the same time, if I work in parallel on a feature or bug fix, I create uncommitted changes and sometimes Codex reverts my edits as it thinks that it didn't made them.
There should be a way to keep a list of changes by Codex somewhere locally, so it would not need to re-scan everything again.
Additional information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗