Hey, thanks for the report and for sharing your workaround. The port forwarding window fix is pretty unusual, so let’s try a few standard steps to see if we can sort this out more reliably.
Quick things to try:
Disable HTTP/2 (most common fix):
Press Ctrl+, → search for “HTTP/2” → enable “Disable HTTP/2” → restart Cursor.
Check extensions:
Run cursor --disable-extensions in your terminal to see if any extension is causing the issue.
Network diagnostics:
Open Cursor Settings → Network → Run Diagnostics and share the results.
Questions:
Does this happen in other repositories, or only in this one?
Are you using any VPN, corporate proxy, or security software?
Do you have any MCP servers configured?
The most successful fix so far has been disabling HTTP/2. Let me know if that helps.
I replicated the situation (I can’t use cursor --disable-extensions because I need to connect to a remote Windows host), and I found that when I open this repository, the cursor’s status bar disappears—the very bottom one
Thanks for the additional details - this helps narrow it down to an interaction between the terminal and extensions in your remote Windows environment.
Since you can’t run cursor --disable-extensions on the remote machine, could you help us debug this with a few diagnostic steps?
Diagnostic steps:
See which extensions are running: press Ctrl+Shift+P → “Developer: Open Process Explorer” → share a screenshot of the processes (especially any extensionHost entries)
Console errors: open Help → Toggle Developer Tools → Console tab, then open a terminal in the problematic repo and share any red errors that appear
Extension list: share your installed extensions (local and remote) from the Extensions sidebar
Quick test: try temporarily disabling extensions one by one (especially anything related to shell / terminal / Git) to see if one of them is causing the crash
Also, let me know if there’s anything unusual about this repository (very large, special workspace settings, custom shell config).
workbench.desktop.main.js:4065 [composer] submitChatMaybeAbortCurrent errored!
Error: [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash (“/”) character
(Optional PS)
Btw, does this detailed log analysis count as me working for Cursor? >.< Maybe I should get a “Bug Hunter” badge!