Switching between Copilot Chat Sessions Destroys associated Terminal Sessions

[davemcom]

Type: Bug

Switching between Copilot Chat Sessions Destroys associated agent triggered Terminal Sessions

This is a blocker. My primary workflow is now broken. if leaving a session results in the associated terminals being lost, my agents can't do their remote work. And requires human interaction.

This could be VSCode Integrated Terminal manager doing aggressive Garbage Collection.
Copilot Chat: environment variables it adds, like copilot / copilot-debug
VS Code Git: Git askpass and auth plumbing
VS Code Terminal/Workbench: terminal GC, disposal, and session lifecycle

Maybe Terminal garbage collection on agent sessions is too aggressive?

This is an absolute show stopper.

Current version of VSCode shows this as well as the version i'm running here.

VS Code version: Code 1.121.0 (f6cfa2e, 2026-05-19T11:51:53+02:00)
OS version: Windows_NT x64 10.0.26200
Modes:

[vs-code-engineering]

Thanks for creating this issue! It looks like you may be using an old version of VS Code; the latest stable release is 1.124.0. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!