›_ Codex Issues
Codex Issues / #5907

The summary message generation without `git` and files collection

Resolved 💬 2 comments Opened Oct 29, 2025 by oneslash Closed Nov 11, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 10 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #4746
  • #4935
  • #5143
  • #5596
  • #5598

Powered by Codex Action

etraut-openai contributor · 9 months ago

Thanks for the bug report. We've shared the feedback with the team members who are responsible for training our codex models. We're tracking this feedback and similar reports so we can make the model more robust in future iterations.

If you see other model behavior that you'd like to report, please use the recently-added /feedback command in the CLI. That will provide us with additional details including logs and conversation text.