warpdotdev
Waiting for a password notification
Pre-submit Checks
- [x] I have searched Warp bugs and there are no duplicates
- [x] 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
Since today, I've a lot of notifications saying 'Blocked .... is waiting for a password', tbh each time I run a command that last more than ~3 seconds.
To reproduce
Version : v0.2025.11.18.12.24.stable_02 MacOS Sequoia 15.6.1 AI disabled
Expected behavior
No notifications as it was
Screenshots, videos, and logs
No response
Operating system (OS)
Select an OS
Operating system and version
15.6.1
Shell Version
No response
Current Warp version
v0.2025.11.18.12.24.stable_02
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
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
i can confirm this bug
i also think that the appoarch in general is strange. why does Warp count the time since the command's start instead of the last time the command output something to the terminal?
Also seeing this v0.2025.12.03.08.12.stable_03
Just because my script is taking a while != it waiting for a password :/
I can also confirm this bug. It has started happening not so long time ago. I'm on v0.2025.11.19.08.12.stable_03.
Oddly it only happens with git log. Most of the times, I need to close the terminal tab. However, in some rare ocasions, it goes away by scrolling down, after which, it allows me to quit the log normally. Another workaround that always works is opening a new tab, doing a git log in this new tab, and then closing this new tab normally. Afterwards, the first tab magically starts working again. What I usually do is just to close the tab and open a new one. It's annoying.
Hope this helps to repro it.
