feedback
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
last
What subscription do you have?
plus
Which model were you using?
gpt-5.6-sol xhigh
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What terminal emulator and version are you using (if applicable)?
VS code
Codex doctor report
NOT available because the codex used up the entire limit due to an error (froze a task that had been running for hours (he made this bug TWICE) there was no reaction even to "esc")
What issue are you seeing?
froze a task that had been running for hours (he made this bug TWICE)
What steps can reproduce the bug?
Uploaded thread: 01a00ce2-65c0-7282-a3f2-f07f13a1b7a8
What is the expected behavior?
No response
Additional information
There is only one screenshot, but here is an example of how it hung on the task and constantly displayed a smaller amount of time. Two hours of execution passed, and it wrote for 56 minutes and did not respond to any keys to end the session (task).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the uploaded thread 01a00ce2-65c0-7282-a3f2-f07f13a1b7a8 and the attached screenshot, then reproduce the long-running task on Windows with the reported model and terminal setup. Done means the hang is understood and the task responds correctly to interruption instead of consuming the full usage limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100