Not able to send any message

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

:lady_beetle: Bug Description

When sending a message in Cursor chat (Ask or Agent mode), the input text disappears but no output is returned. The chat panel stays empty.

:high_voltage: Expected Behavior

After pressing Enter (or clicking the green send button), the selected model (e.g., GPT-5, Claude-Sonnet) should process the input and return a response in the chat panel.

:red_circle: Actual Behavior

Input disappears after sending.

No response appears.

Developer console shows errors like:

[Background Composer] timed out getting tasks from agent
[Background Composer] preferred remote not found

.cursor-server process uses very high CPU.

On htop, multiple .cursor-server tasks are running at the same time, consuming resources.

:test_tube: Steps to Reproduce

Open Cursor (Pro plan).

Create a new chat (Ask mode, GPT-5 or Claude).

Type hi and send.

Observe: text disappears, no response comes back.

:desktop_computer: Environment

OS: macOS (MacBook Air)

Cursor version: latest (from cursor.com)

Plan: Pro

Steps to Reproduce

just type in chat something

Expected Behavior

Give output

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.46 (Universal)
VSCode Version: 1.99.3
Commit: b9e5948c1ad20443a5cecba6b84a3c9b99d62580
Date: 2025-10-14T01:21:46.830Z (3 days ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.6.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. It looks like a network issue that’s preventing streaming responses from reaching the client.

Please try:

  • Run network diagnostics: Cursor Settings → Network → Run Diagnostic, then share any errors
  • Enable HTTP 1.1 fallback: Cursor Settings → Network → enable HTTP 1.1 (or “Disable HTTP/2”).
  • Test on a different network: if possible, try a mobile hotspot to check if it’s ISP‑related
  • Open DevTools and check the console/network tabs for errors

Let me know the diagnostic results and whether switching to HTTP 1.1 helps.