10 hours of thinking
Resolved 💬 7 comments Opened Nov 16, 2025 by Iydah Closed Jan 6, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
Latest Build
What subscription do you have?
Pro
Which model were you using?
GPT-5.1-Codex-Medium
What platform is your computer?
Windows (WSL)
What issue are you seeing?
Asked codex to analyse the project for maintainability issues and then went to sleep, it's been thinking for Working (10h 19m 44s • esc to interrupt)
What steps can reproduce the bug?
Uploaded thread: 019a897f-d9f8-7aa2-8a66-e1521910c900
What is the expected behavior?
Maybe not to think for 10 hours straight
Additional information
_No response_
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I'm also experiencing absurd thinking times. Averages like 30 minutes. With no tool usages or new thoughts being emitted.
I had to revert to the 0.57 package as this absurd thinking times make the 0.58 unusable for me. Definitely will not be upgrading until the next version is released.
Reverting to 0.57 fixed it for me. I'm also on WSL if that helps.
For me, reverting the VS Code extension version worked. We reported it at #6623
, but it was closed without any explanation. They told us to use a /feedback command that doesn’t even exist in the extension yet…
I updated to 0.61 and this seems actually to be an issue related to UNDO and it tracking directories with large numbers of files. 0.61 warned me " Repository snapshot encountered large untracked directories: ... This can slow Codex; consider adding these paths
to .gitignore or disabling undo in your config." The thing is though is that the paths that it mentioned are already in .gitignore for this project so I'm not sure what else I can do other than disable the undo feature.
Edit:
A bit more digging and I think this can be disabled in the config.toml with:
This appears to have stopped the issue.
We've removed the experimental
/undofeature in the latest version of the CLI, so you no longer need to disable it.