when i come to this page, the return to cursor bottom is invalid. and the cursor client is still unlog in. If i close the client, click return to cursor bottom, the client will open, but it still unlog. how can i solve this problem?
Hi there!
We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.
To help us investigate and fix this faster, could you edit your original post to include the details from the template below?
Bug Report Template - Click to expand
Where does the bug appear (feature/product)?
- Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
- Terminal & commands
- Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
- MCP & tools
- Cloud Agents & Automations (cursor.com/agents, scheduled/event)
- BugBot & Code Review
- Cursor CLI
- Cursor Mobile
- Remote (SSH / Dev Containers / WSL)
- Account, billing & login
- Something else…
Describe the Bug
A clear and concise description of what the bug is.
Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!
- …
- …
- …
Expected Behavior
What is meant to happen here that isn’t working correctly?
Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)
Operating System
- Windows 10/11
- MacOS
- Linux
Version Information
- For Cursor IDE: Menu → About Cursor → Copy
- For Cursor CLI: Run
agent aboutin your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......
CLI:
CLI Version 2026.01.17-d239e66
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
- Yes - Cursor is unusable
- Sometimes - I can sometimes use Cursor
- No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Hey, I see a screenshot of the “All set! Feel free to return to Cursor” page, but the client is still stuck on Log In. This usually happens for 2 reasons: the cursor:// protocol handler isn’t working, or the client’s traffic is blocked by a proxy or HTTP/2. Try this:
-
Check the protocol handler:
- Paste this into your browser address bar: cursor://anysphere.cursor/test
- You should see an “Open Cursor?” prompt and the app should focus. If nothing happens, reinstall Cursor using the latest installer and run it once as Run as administrator, then launch it normally and try logging in again.
-
Proxy for the client itself:
- In Cursor open Settings
Ctrl+,, search for proxy - Http: Proxy, set your local proxy address, for example http://127.0.0.1:7890
- Http: Proxy Support, turn it on
- In Cursor open Settings
-
If it still won’t log in, in Settings search for HTTP/2 and enable Disable HTTP/2, or in settings.json set “cursor.general.disableHttp2”: true.
-
Retry the login: click Log In in the client, complete the steps in the browser, then return to the client.
Related threads with working fixes:
- Desktop app stuck on login screen after successful browser authentication
- Login failed on Windows 11
If it still doesn’t help, please send:
- Cursor version: Menu > About Cursor > Copy
- Windows 10 or 11
- Result of Settings > Network > Run Diagnostics
- What happened when you tested cursor://
Let me know how it goes.
Thanks for your help;
In fact, when I input cursor://anysphere.cursor/tes Afterwards, it was indeed possible to open the corsur client. But when I click on the software interface and press Ctrl+on the keyboard, there is no response from the software interface and I cannot enter the settings interface.
