You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It happens all the time with npm when it runs commands randomly it just get's stuck running a command. At the moment I had it address some changes to drizzle orm to migrate and it got stuck using bunx, which I was hoping it would not given that my issues where with npm.
What is the expected behavior?
To stop running the command after at least 5 minutes of waiting for a simple drizzle migration command or simple commands in general if there is an error. Given the capabilities I would expect to be able to stop address the issue and then attempt it again.
What do you see instead?
It gets stuck and to test I explained the fix which was in the drizzle.config but it just kept running it immediately even after I told it to first fix it. I could've just do it myself but I wanted to see if it was a bug and apparently it is. It does not seem to have a proper timer when running commands and can just get stuck for over 30mins when the command does not produce anything. Not that big of a deal but it is insanely annoying when trying to let it run agentic tasks.
If you run into problems like this in the future, please use the /feedback slash command to upload the session and file a new bug report with the thread ID. That will help us investigate.
Activity
etraut-openai commentedon Nov 26, 2025
If you run into problems like this in the future, please use the
/feedbackslash command to upload the session and file a new bug report with the thread ID. That will help us investigate.