IssueRaiser

Add setting to disable the auto-resolve in 60 seconds for questions

### What version of Codex CLI is running? codex-cli 0.141.0 ### What subscription do you have? Plus ### Which model were you using? gpt-5.5 ### What platform is your computer? Linux 7.0.3-arch1-2 #1 SMP PREEMPT_DYNAMIC Fri, 01 May 2026 15:49:22 +0000 x86_64 GNU/Linux ### What terminal emulator and version are you using (if applicable)? Alacritty ### Codex doctor report ```json not available ``` ### What issue are you seeing? Codex will automatically accept the recommended answer to a question within 60 seconds. ### What steps can reproduce the bug? 1. Go to plan mode 2. Write a plan prompt that will make Gpt to ask you a question 3. Notice you have a 60 second delay to answer the question ### What is the expected behavior? There should be a setting to disable the 60-second auto-resolving. ### Additional information _No response_

Posted by antoyo on Jun 18, 2026, 7:54 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

github (Healthcare)

Add setting to disable the auto-resolve in 60 seconds for questions

antoyoJun 18, 2026, 7:54 PM

### What version of Codex CLI is running? codex-cli 0.141.0 ### What subscription do you have? Plus ### Which model were you using? gpt-5.5 ### What platform is your computer? Linux 7.0.3-arch1-2 #1 SMP PREEMPT_DYNAMIC Fri, 01 May 2026 15:49:22 +0000 x86_64 GNU/Linux ### What terminal emulator and version are you using (if applicable)? Alacritty ### Codex doctor report ```json not available ``` ### What issue are you seeing? Codex will automatically accept the recommended answer to a question within 60 seconds. ### What steps can reproduce the bug? 1. Go to plan mode 2. Write a plan prompt that will make Gpt to ask you a question 3. Notice you have a 60 second delay to answer the question ### What is the expected behavior? There should be a setting to disable the 60-second auto-resolving. ### Additional information _No response_

Comments (0)

No comments yet. Start the discussion.

Comment on this issue