Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
In Design mode, messages can no longer be sent. After typing a prompt and pressing Enter / clicking Send, nothing is submitted. Switching to Agent mode works normally.
Steps to Reproduce
- Open a chat and switch to Design mode
- Type any message (optionally with an image attached)
- Press Enter or click Send
- The message is not sent
Expected Behavior
The message is sent and the agent responds.
Screenshots / Screen Recordings

Operating System
MacOS
Version Information
Version: 3.24.12 (Universal)
VS Code Extension API: 1.128.0
Commit: 37b865941ccb31e2fc90c685157534efca87f960
Date: 2026-10-09T20:56:41.904Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 27.0.0
Does this stop you from using Cursor
Yes - Cursor is unusable
Downgrading to the previous version will avoid this issue.
Version: 3.23.23
VS Code Extension API: 1.128.0
Commit: 2dac2428994fe34f12658d9ecad1541b98db2c00
Date: 2026-10-05T01:43:43.807Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 27.0.0
Hey @sinar_pandora, thanks for the recording.
Staying on 3.23.23 is the right call for now. If you end up back on 3.24.12, screenshot the element yourself (Cmd+Ctrl+Shift+4 copies it to your clipboard), paste it into the regular chat, and describe the change there. Cmd+L runs into the same issue, so I’d skip that one.
It sends fine on a simple page on my end, so something on your page seems to trigger it. If you’re up for one more try on 3.24.12: does Design mode send on example.com? And could you share any lines that show up under Help > Toggle Developer Tools > Console (type DesignMode in the filter) after a failed send on your page?
I’ll post here when I have more to share.
@mohitjain Hi, after re-upgrading, the issue is fixed. I’ll keep tracking it, and if I run into it again, I’ll use the method you suggested to provide debug logs.