Switching from Cloud to Local in Agents Window erases/loses unsubmitted prompt

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the Agents Window view in an active chat, I had typed a follow-up prompt to the cloud agent. I realized that a skill I wanted to include in the prompt was unavailable in Cloud, so I wished to switch to continue this conversation on Local. With this prompt in the text box, the act of switching to continue on local basically refreshes/reloads the UI and completely erases/loses the unsubmitted prompt.

Steps to Reproduce

Open a Cloud Agent chat in Cursor IDE Agents Window, start typing a prompt, without submitting it, click the Continue on dropdown, and select Local instead of Cloud. The UI will refresh/reload and your prompt will be gone and unrecoverable.

Expected Behavior

A prompt sitting in the “Send follow-up” textbox should be persisted in the UI state/cache and survive a change of the “Continue on” from Cloud to This Mac and vice versa. As a user, I do not expect a dropdown/toggle change like that to cause me to lose a long prompt I spent 15 minutes typing, as it looks to only be changing a parameter that applies the next time I submit a turn to the chat.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.10.20
VS Code Extension API: 1.125.0
Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0
Date: 2026-07-07T07:03:33.071Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

Composer 2.5 Fast

For AI issues: add Request ID with privacy disabled

bc-2723d7b5-94c9-4779-996c-23e40de0813c

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hey there, thanks for the writeup and recording.

You’re right, this is a bug on our side. Switching the Continue on target (Cloud ↔ This Mac) with an unsent draft in the box shouldn’t wipe it - the draft is meant to carry over. It’s a known issue, and a fix is already in the works that should land in an upcoming Stable update.

Until then, two ways to avoid losing a prompt:

  1. Set Continue on to where you want to run (Cloud or This Mac) first, then type your prompt.
  2. If you’ve already typed it, select all and copy (Cmd+A, Cmd+C) before switching, so you can paste it back.

I’ll follow up here once the fix ships.

8

Thanks for the insight Mohit. Yes I learned the hard way here, and do usually copy big prompts before I send, and got burnt the one time I didn’t.

Looking forward to the fix, it will be a solid UX improvement and creature comfort (less worry).

9

Do you see the new local chat in the ide editor? Becuase I’m only seeing the cloud there.

10

This is from the Cursor Desktop Agents window, though I can attest that there are various discrepancies between IDE vs. Agents vs. Cloud view of the same chat transcript across the board. However, that is not the scope of this bug report or issue.