What version of the IDE extension are you using?
Version: 1.119.0 (user setup) Commit: 8b640eef5a6c6089c029249d48efa5c99adf7d51 Date: 2026-05-05T11:23:50-07:00 Electron: 39.8.8 ElectronBuildId: 13870025 Chromium: 142.0.7444.265 Node.js: 22.22.1 V8: 14.2.231.22-electron.0 OS: Windows_NT x64 10.0.26200
What subscription do you have?
Pro
Which IDE are you using?
VS code
What platform is your computer?
No response
What issue are you seeing?
If a run is interrupted—either because the main agent is stopped or due to a compaction issue—any spawned parallel agents disappear along with their context. For a Pro subscription, losing important project context in this way is highly damaging. It not only consumes rate limits through the use of spawned agents, but also causes the loss of work and context those agents generated. The main agent may need to redo completed work or may lose awareness of those explorer/worker agents entirely.When this occurs, the consumption of rate limits is non-refundable and effectively lost. We are losing valuable usage limits even though the generated context is neither actually used nor recoverable. The context created by spawned agents simply disappears.
What steps can reproduce the bug?
Spawn sub agents, have a compaction issue, or other main agent hang and stop the run.
What is the expected behavior?
No response
Additional information
No response
What version of the IDE extension are you using?
Version: 1.119.0 (user setup) Commit: 8b640eef5a6c6089c029249d48efa5c99adf7d51 Date: 2026-05-05T11:23:50-07:00 Electron: 39.8.8 ElectronBuildId: 13870025 Chromium: 142.0.7444.265 Node.js: 22.22.1 V8: 14.2.231.22-electron.0 OS: Windows_NT x64 10.0.26200
What subscription do you have?
Pro
Which IDE are you using?
VS code
What platform is your computer?
No response
What issue are you seeing?
If a run is interrupted—either because the main agent is stopped or due to a compaction issue—any spawned parallel agents disappear along with their context. For a Pro subscription, losing important project context in this way is highly damaging. It not only consumes rate limits through the use of spawned agents, but also causes the loss of work and context those agents generated. The main agent may need to redo completed work or may lose awareness of those explorer/worker agents entirely.When this occurs, the consumption of rate limits is non-refundable and effectively lost. We are losing valuable usage limits even though the generated context is neither actually used nor recoverable. The context created by spawned agents simply disappears.
What steps can reproduce the bug?
Spawn sub agents, have a compaction issue, or other main agent hang and stop the run.
What is the expected behavior?
No response
Additional information
No response