The Context Used indicator shows the context of the Subagent

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Context Used indicator shows the context of the subagent.

Steps to Reproduce

At least after a failure in the Subagent’s operation (loss of connection) and continuation through the new prompt, most likely the indicator shows the context window that the Subagent had, and not the one that the Agent currently has

Operating System

Windows 10/11

Version Information

Version: 2.5.0-pre.11.patch.0 (system setup)
VSCode Version: 1.105.1
Commit: 88286e028b1f8be77ef302ef5c338191c984aef0
Date: 2026-01-25T08:29:31.223Z
Build Type: Stable
Release Track: Nightly
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.22631

Does this stop you from using Cursor

No - Cursor works, but with this issue

How to disable/defer "Chat context summarized." interruptions?
3

The indicator fails from the moment a new request is sent until the moment of the first edit_file.

4

Hey, thanks for the report.

This is an interesting bug. The indicator is showing a “frozen” sub-agent context after it crashes. The team is actively working on sub-agent stability in nightly, so your report is really timely.

Can you share the Request ID from one of these cases? That’ll help the engineers pinpoint the moment when the indicator stops updating.

For context, you’re right that after the first edit_file the indicator “wakes up” again. That’s a good sign the issue is with the UI state update after the crash, not with the agent context itself.

6

I decided to work only privately “to be safe”, but the bug consistently reoccurs when using chat. It’s noticeable when there’s a significant difference between the Agent and Subagent contexts.

1 Like