Where does the bug appear (feature/product)?
Cursor CLI
Describe the Bug
Stop and Stop All do not clear background agents stuck on “Starting up” after an unavailable model, and they return after Cursor is fully quit
Product: Cursor Desktop, Agents panel
Environment
OS: Windows 10 (build 26200)
Workspace: d:\prj\hw\tes\release-tech-1\ue4
Chat id: 6aeef096-983c-44d9-b7ec-6b3d7a318d57
Date observed: 2026-09-30
Summary
Two background agents stay under Working, both on “Starting up”. Stop on each one does nothing. Stop All, then Confirm, does nothing. Quit Cursor completely and open it again, and both are back in the same state.
Agents
Triage deferred inbox results
Extract bug 1 plan from side-chat
Steps to Reproduce
Steps
A chat starts a background subagent with run_in_background: true and model grok-4.7-medium.
That slug is not one the Task tool can launch. The Grok slug available in this session is grok-4.7-high.
The Agents panel shows both entries as Working / Starting up. They never run and never show an error.
Stop each entry on its own.
Stop All, then Confirm.
Quit Cursor completely and start it again. Open the same workspace.
Expected Behavior
An unavailable model fails immediately and names the slug that was rejected. Stop and Stop All remove the entries. A full quit does not restore them.
Actual:
Both entries remain on “Starting up”. Stop on each worker does nothing. Stop All plus Confirm does nothing. After a full shutdown they load again as Working / Starting up.
Evidence
The parent transcript records both launches as background Task calls with model grok-4.7-medium and run_in_background true. No tool result for either call was written back into the chat. This workspace’s state.vscdb has no separate queue row for those titles, so the pending work appears to live on the chat itself, which is why a restart brings it back and why Stop has nothing it can cancel.
Operating System
Windows 10/11
Version Information
This is a local Cursor agent running Grok 4.7 in d:\prj\hw\tes\release-tech-1\ue4. Chat id: 6aeef096-983c-44d9-b7ec-6b3d7a318d57.
The two entries stuck on Starting up are background workers this chat launched, not separate Cursor processes:
Triage deferred inbox results
Extract bug 1 plan from side-chat
Both were started with model grok-4.7-medium, which this session cannot launch. They never returned a result. Stop and Stop All do not clear them, and a full quit restores them because the unfinished launches are stored on this chat.
Does this stop you from using Cursor
No - Cursor works, but with this issue