Finished agents still show as Working

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

On Windows, after subagents finish (turn_ended: success in their transcripts), the Agents sidebar and the Working pill still show them as running. Stop and Stop All do not clear the entries. Reload Window does not clear them. Opening the chat shows “Worked for …”, so the turn is done, but the list still says the agent is working. This matches the zombie Working state already reported. The UI should reconcile with turn_ended and drop any entry that has no live process.

Steps to Reproduce

On Windows, open a project in Cursor and start an Agent chat.
Have that agent launch several background subagents (multitask / Task). In this case they were audit workers, and each one finished its job.
Wait until each subagent transcript ends with turn_ended and status success. Opening the chat shows Worked for … (here, about 1–4 minutes).
Look at the Agents list and the Working pill without sending a new message.
Expected: finished agents leave the running state.

Actual: they still show as in progress, after the chats already say the work is done. Stop, Stop All, and Reload Window do not clear them.

Expected Behavior

I believe its mostly a display issue. The sub agents show that they are still either working or starting tought they are not or they are already finished.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.22.7 (user setup)
VS Code Extension API: 1.128.0
Commit: 37076c6c3f9e253c0fa2305197e45befd13a2260
Date: 2026-09-24T05:01:24.589Z
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: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

See bottom: ‘Working 6’. Probably a terminal or something still running.

Hey @Christophe_Dsouza, thanks for the report and the screenshot.

You’re right that this is a display issue. Your subagents did finish, and nothing is still running behind those rows. It’s the same issue as the earlier “zombie Working” thread. We’re already tracking it, and I’ve added your report to it.

In the meantime, starting a new chat for your next batch of subagents gives you a clean Agents list, since the stale rows are tied to that one parent chat.

If you get a moment, could you tell me whether sending any short message in the parent chat (the one with the stuck list) clears the rows? That helps us narrow down where the state gets stuck.

Hi @Colin ,

Same display bug on Linux, the night of 11–12 October 2026 (local time), in Cursor Desktop Multitask Mode.

Three child cards stayed Working after turn_ended success:

  • Review Task 1 skeleton (b2693fa5, 23:36). An earlier attempt, a40ba96b, died at 23:34 on an Other Models usage limit and was marked error. The retry finished; that Working card stayed.

  • Review Task 5 parameters (75a70c65, 23:38).

  • Review Task 12 PIN vault (f83949fa, 23:37).

Parent agent 9915fed9 ended success at 23:58 with nothing in flight, but its tool rows stayed backgrounded/running. No live process; the terminals folder was empty; the Gradle daemon was asleep. The parent transcript never recorded child completion, so the spinner had no event to clear.

A short message in the parent chat does not clear the rows. After these three cards had already finished, this same parent chat sent several follow-ups: a check of whether any subagent was still running, a search for an existing forum topic, and this discussion of the bug. The three cards are still shown as Working.

Related issues: zombie Working subagent tasks and subagent panel stuck on Starting up.

Thanks!