# Subagents freeze after 3.19.13 update?

**URL:** <https://forum.cursor.com/t/subagents-freeze-after-3-19-13-update/171233>\
**Category:** Bug Reports\
**Tags:** chat, agents-window, subagents\
**Created:** [September 10, 2026, 8:23am UTC](https://forum.cursor.com/t/subagents-freeze-after-3-19-13-update/171233 "2026-09-10T08:23:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![NoMames](https://avatars.discourse-cdn.com/v4/letter/n/3da27b/32.png) [@NoMames](https://forum.cursor.com/u/NoMames)\
**Post date:** [September 10, 2026, 8:23am UTC](https://forum.cursor.com/t/subagents-freeze-after-3-19-13-update/171233/1 "2026-09-10T08:23:21Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Just installed the 3.19.13 update.

Agent Window

Subagents often show ‘Stopped’ while the main agent shows ‘Waiting for subagent’. I can’t check the details of the subagent and it’s always ‘This chat could not be loaded.’

Have to send “Continue” on the main agent to solve the freeze and then I can load the subagent chat.

### Steps to Reproduce

Ask an agent to assign a subagent

### Operating System

Windows 10/11

### Version Information

Version: 3.19.13 (user setup)  
VS Code Extension API: 1.128.0  
Commit: dd066f332fcea7382764400fde902f61920648d0  
Date: 2026-09-04T17:41:16.065Z  
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.20348

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [September 10, 2026, 8:56am UTC](https://forum.cursor.com/t/subagents-freeze-after-3-19-13-update/171233/7 "2026-09-10T08:56:25Z")

</div>

Hey there, thanks for the detailed report!

Quick unblock: your “Continue” trick is the right move, and reloading the window (Cmd/Ctrl+Shift+P → Developer: Reload Window) also clears it. The subagent is usually still running in the background, so the “Stopped” / “could not be loaded” is a display issue, not the subagent actually quitting.

This isn’t anything on your end, it’s an issue we’re tracking, and I’ll post back here when there’s an update.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [September 12, 2026, 8:56am UTC](https://forum.cursor.com/t/subagents-freeze-after-3-19-13-update/171233/8 "2026-09-12T08:56:46Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.