I don't want it stop when my current conversation is not over even if my token is not enough
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
codex-cli 0.152.1
What subscription do you have?
I don't want it stop when my current conversation is not over even if my token is not enough
Which model were you using?
gpt-5.6-sol
What platform is your computer?
window
What terminal emulator and version are you using (if applicable)?
No response
Codex doctor report
What issue are you seeing?
I don't want it stop when my current conversation is not over even if my token is not enough
What steps can reproduce the bug?
Uploaded thread: 01a064ea-90ae-7f00-b4f7-44609237f125
What is the expected behavior?
The conversation was stoped when the output was not over.
Additional information
No response
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 reproducing the uploaded thread 01a064ea-90ae-7f00-b4f7-44609237f125 with codex-cli 0.152.1 on Windows, then trace the CLI path that handles token exhaustion and interrupted output. Done means an unfinished conversation does not stop solely because the available token budget is insufficient, with the expected behavior verified by a regression test.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100