Etting -> Connection failed. Please try again, or contact support if the issue persists

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Not able chat or query in the Cursor IDE conversation , getting same error as in screen shot.

Steps to Reproduce

Always getting same error , not able query a conversation.

Expected Behavior

Should be able to query the model

Operating System

Windows 10/11

Version Information

Version: 2.5.20 (system setup)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

4

Hey, this looks like a known Windows-only bug where having the terminal panel visible can cause Connection failed errors.

When the terminal is open, Cursor tries to collect terminal context for chat, but path resolution fails on Windows because of a URI parsing issue.

Two things to try:

  • Hide the terminal panel before you send a chat message. Switch to the Output or Ports tab at the bottom, or close the bottom panel. This should unblock you right away.
  • Update Cursor. You are on v2.5.20 from Feb 19, which is about a month behind. Go to Help > Check for Updates. Several connection fixes have shipped since then, and updating might fix it.

If it still happens after updating, can you:

  • Open Dev Tools via Help > Toggle Developer Tools > Console tab
  • Try sending a chat message with the terminal visible
  • Share any errors from the console here

The team is aware of this issue. Your report helps with prioritization.

Let me know how it goes.

5

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.