Agent session won't terminate - Stop inneffective, messages queued, usage drains

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m seeing a bug where Cloud Agent sessions appear to complete but never fully shut down, which blocks new messages and continues consuming API usage.

Steps to Reproduce

1)Start a Cloud Agent session on repo veznero/internal (branch snap-summary).
2)Agent finishes and displays a full response (UI shows “Worked for 15s” / “Thought for 2s”).
3)Type a follow-up message in the same Composer/Agent thread.
4)Message shows “1 Queued · ⏎ to send” instead of sending immediately.
5)Click Stop — nothing happens; session appears still active.
*Sidebar shows agent runs still active (e.g. 26m, 2h).

Expected Behavior

1)When the agent response is complete, the session should terminate.
2)Stop should immediately cancel any remaining work.
3)New messages should send without queuing behind a finished session.
4) !!!Usage should not continue draining after the response is displayed!!!

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.8.11 (user setup)
VS Code Extension API: 1.105.1
Commit: e56ad3440df06d22ca7501e65fd518e905486ef0
Date: 2026-06-18T01:40:18.333Z
Layout: glass
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: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Composer 2.5

Additional Information

My usage is constantly being consumed by an unprompted agent. Hitting the stop button does nothing. Agent continues stating “Planning next moves” or “This is taking longer than expected”. I don’t want to close the session because there is still useful context I don’t won’t to have to relay in a new prompt.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @Jonathan_Edwards,

I believe this is a UI issue with the Agents window: the cloud agent actually finishes (or the VM gets reaped), but the Agents window never transitions the chat to a terminal state.

Could you try the following?

  • Run Ctrl + Shift + P > Developer: Reload Window.
  • Check cursor.com/agents to confirm the true state of the agent.

Also worth noting: agents are billed by tokens, not by VM usage, so you shouldn’t be burning through any API usage while this is happening.