-
Notifications
You must be signed in to change notification settings - Fork 631
Warp freezes after the budget is exceeded #8968
Description
Pre-submit Checks
- I have searched Warp bugs and there are no duplicates
- I have searched Warp known issues page and my issue is not there
- I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
- I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions
Describe the bug
Working on project via conversation (have no idea how to transform it to the separate project).
When my budget exceeded during the code preparation, Warp became unresponsive. Didn't know what's going on, because I was not notified about the budget issue, forked the conversation, to restart coding before freeze happened.
At some point after I realized that it is about the budget and couldn't buy extra credits, because the interface was frozen. Finally I managed to do so somehow and after a few restarts Warp became alive again. I bought some extra credits for a 100$ and also set auto reload to avoid issues like that. After some further coding, after clicking on adding custom rule my warp got frozen again. And I'm stuck I cannot go any further. Warp freezes at "starting the shell" or "Warping ...". Restarted computer, etc. For a moment warp became responsive when I managed to logout and login again.
I requested to analyze some code changes made in this project and it is "warping" again :-(
To reproduce
have no idea how to reproduce it.
Expected behavior
No response
Screenshots, videos, and logs
No response
Operating system (OS)
Select an OS
Operating system and version
Windows 10 Pro
Shell Version
powershell
Current Warp version
v0.2026.03.25.08.24.stable_05
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
2026-03-28
Additional context
On the billing and usage section, I can see Add-on credits: 6329 and also usage 1500/1500 in red.
Does this block you from using Warp daily?
No
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None