Hi @stable night. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#Warp UI & ai response been very slow
fleet matrixBOT
I'm sorry to hear you're experiencing these issues. Based on the knowledge sources, there are several known performance problems affecting Warp's UI and AI responsiveness that others have reported as well.
Known Issues
General UI Sluggishness
Multiple users have reported slow UI, including tabs taking 5–10 seconds to open and random CPU/memory spikes. Warp has acknowledged these issues and pushed patches for some of them. [Latest release issues]
AI/Agent Freezing
Warp is known to intermittently freeze and become unresponsive when opening or running agents. The likely cause involves main-thread filesystem watcher processing during agent workflows — when agents edit or generate many files, it can trigger synchronous path operations that block the UI. [Warp freezes with agents]
Long Conversation Slowness
If you've been having extended AI conversations, there's a known bug where very long conversations cause severe UI sluggishness or freezing due to text rendering performance issues. Switching to a new conversation reportedly restores responsiveness. [Text rendering performance]
AI Rate Limit Errors
Some users have also encountered RESOURCE_EXHAUSTED (429) errors from the underlying AI API, which can make AI responses fail or stall. [AI resource exhausted]
What You Can Try
- Update Warp — Several of the reported bugs have been patched in recent releases.
- Start a new conversation — If slowness is tied to a long AI conversation, starting fresh may help.
- Check your credit/budget — There's a known issue where Warp can freeze or become unresponsive when the usage budget is exceeded. [Warp freezes after budget exceeded]
- Report the issue — You can submit a bug report with logs via Warp's feedback mechanism. Including a debugging ID for AI issues helps the team expedite fixes.
These are active, open issues that Warp's team is working on. I'd recommend filing a bug report directly so your specific case (including credit usage) is tracked.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
stable night
i'm on the latest version of warp
stable night
1. **Update Warp** — Several of the reported bugs have been patched in recent re...
i'm on the latest version of warp
@fleet matrix i'm on the latest version of warp
fleet matrixBOT
Let me check the knowledge base for you again. One moment! :books:
Thanks for confirming. Being on the latest version doesn't necessarily mean all issues are resolved, as some of the bugs described in the knowledge sources are still open and actively being investigated.
Here are the most relevant steps you can take right now:
Recommended Actions
1. Collect a CPU Sample
Since you're experiencing slowness, the most useful thing you can do is capture a CPU sample while the issue is occurring and submit it as a GitHub issue. This is exactly what Warp's team needs to diagnose the root cause. [Collecting CPU samples]
On macOS:
- Reproduce the slowness in Warp.
- Open Activity Monitor, select the Warp process, and click Sample Process.
- Save the sample and attach it to a new GitHub issue.
2. Try Starting a New AI Conversation
If your AI slowness is happening in a long-running conversation, switching to a new one may restore responsiveness, as text rendering performance degrades in very long conversations. [Text rendering performance]
3. Check Your Usage/Credits
There's a known issue where Warp can freeze or become unresponsive when the usage budget is exceeded. Given you mentioned using your own credits to diagnose the problem, it's worth verifying your credit balance in the billing section. [Warp freezes after budget exceeded]