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
First of all, I'm really enjoying the AI-powered terminal integration - it's genuinely useful. However, every time I try to log in, I hit the dreaded "Something went wrong." error message. I've tried every suggestion out there: whitelisting domains, using incognito mode, clearing cache... you name it. Nothing consistently works.
Occasionally, it logs me in for no apparent reason, but whenever I actually need it to work, it turns into a painful guessing game.
The Warp terminal has been so helpful that I'm seriously considering subscribing to the individual plan. Unfortunately, this persistent login issue is a dealbreaker until it gets resolved.
Suggestion:
Please consider implementing a more reliable login method - anything other than magic link email authentication. This current method seems to fail more often than not, at least for me.
To reproduce
Receive the authentication link in e-mail and click the link.
Expected behavior
Successful authentication on Warp Terminal.
Screenshots, videos, and logs
Operating system (OS)
Windows
Operating system and version
Windows 11 and Endeavour OS (Plasma X11). Tried Firefox and Chrome
Shell Version
Unrelated, but here it is: bash 5.2.37(1)-release (x86_64-suse-linux)
Current Warp version
v0.2025.05.21.08.11.stable_01 (same problem on previous version)
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
2025-05-22
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
This error is showing up in your browser, yes? Can you look at the JavaScript console and see if there are any messages in there that might help us better understand what's going wrong?
This error is showing up in your browser, yes? Can you look at the JavaScript console and see if there are any messages in there that might help us better understand what's going wrong?
This is the page "Something went wrong.", the console and the network tab on dev tools:
Pre-submit Checks
Describe the bug
First of all, I'm really enjoying the AI-powered terminal integration - it's genuinely useful. However, every time I try to log in, I hit the dreaded "Something went wrong." error message. I've tried every suggestion out there: whitelisting domains, using incognito mode, clearing cache... you name it. Nothing consistently works.
Occasionally, it logs me in for no apparent reason, but whenever I actually need it to work, it turns into a painful guessing game.
The Warp terminal has been so helpful that I'm seriously considering subscribing to the individual plan. Unfortunately, this persistent login issue is a dealbreaker until it gets resolved.
Suggestion:
Please consider implementing a more reliable login method - anything other than magic link email authentication. This current method seems to fail more often than not, at least for me.
To reproduce
Receive the authentication link in e-mail and click the link.
Expected behavior
Successful authentication on Warp Terminal.
Screenshots, videos, and logs
Operating system (OS)
Windows
Operating system and version
Windows 11 and Endeavour OS (Plasma X11). Tried Firefox and Chrome
Shell Version
Unrelated, but here it is: bash 5.2.37(1)-release (x86_64-suse-linux)
Current Warp version
v0.2025.05.21.08.11.stable_01 (same problem on previous version)
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
2025-05-22
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
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
The text was updated successfully, but these errors were encountered: