Timeout and Error After Long-Running Prompt
Status Fixed / completed
Maintainer reply ✓ Yes — igorkofman
Activity 7 comments · opened Feb 24, 2025 · closed Mar 25, 2025
💡 Likely answer: A maintainer (igorkofman, collaborator)
responded on this thread — see the highlighted reply below.
Bug Description
it ran for over 700 seconds and in the end I had to interrupt and nothing, then I wrote another prompt and am getting an error
Environment Info
- Platform: macos
- Terminal: WarpTerminal
- Version: 0.2.8
- Feedback ID: bff1f242-d7b1-4360-b74d-a15070121382
<img width="1158" alt="Image" src="https://github.com/user-attachments/assets/48b970d7-f45b-4425-a23e-ec93681239e9" />
7 Comments
I am having same issues all the time on a large repo
<img width="1397" alt="Image" src="https://github.com/user-attachments/assets/93e3802d-8ee5-44dd-8f7c-c2fb677c97ec" />
It basically never completes.
Would be very beneficial to have a verbose mode that tell us what's happening, including any console output or model interaction.
SHELL=/bin/bash claudeIs that what it is then? Good catch, I'm using fish.
Hi folks, is this better for you in the latest version?
Yeah haven't had this since...
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.