Sometimes some commands that gpt5 enters ends up just being stuck on that command until i stop it with ctrl+C, how can i prevent it from happening?
#Warp getting stuck
glacial moss
still nightBOT
Hi @glacial moss. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
This is a known issue in Warp, especially when using GPT-5 or other agentic AI models. Users have reported that commands entered by the agent can get stuck, requiring you to manually stop them with Ctrl+C. This can happen with long-running commands, commands that open pagers (like git branch -a), or when the agent is waiting for input but doesn't make it clear to the user.
What you can do:
- If a command gets stuck, pressing Ctrl+C is currently the main way to regain control. Sometimes, pressing Enter may also work, but this is not always reliable Warp says it runs command, but just hangs.
- For commands that open pagers (like less or more), try pressing q to exit the pager, as this can sometimes resolve the stuck state git branch -a command gets stuck.
- There is a known visual bug where the "Execute" or "Continue" buttons may not appear if the planning step title is too long or the window is too narrow. Try widening your Warp window to see if the buttons become visible planning step getting stuck when using GPT-5 as planning model.
- The Warp team is aware of these issues and is working on improvements, including better handling of long-running and interactive commands, and making the UI more robust in these scenarios git branch -a command gets stuck, planning step getting stuck when using GPT-5 as planning model.
Currently, there is no permanent fix or setting to prevent this from happening, but improvements are in progress. If you encounter this frequently, you may want to follow the related GitHub issues for updates or try using a different model if possible.