GitHub CLI Crashes when an IDE with GitHub Copilot extension is used

[DefinetlyNotAI]

Describe the bug

Opening github CLI then opening an IDE that also has github copilot in it results in the CLI doing frequent crashes, unexpected behaviour and other issues

Affected version

1.0.3

Steps to reproduce the behavior

1. Open GitHub CLI
2. Open an IDE with GitHub Copilot installed (most likely same account)
3. Once the IDE loads and extensions load ( I am using WebStorm ) go back to the CLI
4. You will find it in a weird state where copilot is closed, but the text remains and the Terminal enters a very weird limbo state where normal functionality breaks such as scrolling or clicking or using ctrl shortcuts (all getting replaced with corrupted text) - The shell is in the corrupted state indefinitely and user must open new shell to use
5. Closing the IDE also resummons the agent via "npm exec" which is very weird behaviour (this happens like after 1 minute of closing the IDE)

20260311-1635-24.1932456.mp4

The video shows an exact proof of concept of the bug

Expected behavior

CLI and IDE not clashing, and CLI doesn't crash when using the IDE

Copilot CLI is wayy better than the webstorm extension which is why I use CLI with WebStorm, and keep the extension for minor IDE-specific stuff

Additional context

Windows 11
Powershell 7
Copilot Installed via winget

Node: v24.12.0
NPM: 11.7.0

[BABYXLB]

Im the same as you , This is a very serious problem

[examon]

This should be resolved as of v1.0.20. Several terminal stability fixes for Windows have shipped since v1.0.3 that address the symptoms you described - terminal corruption, broken shortcuts, and corrupted shell state when running alongside an IDE. Updating to the latest version should resolve these issues. If you're still experiencing problems after updating, please feel free to reopen this issue.

[DefinetlyNotAI]

Amazing this got fixed in my side, just for the sake of my curiosity what was the cause of the issue and how was it fixed?

[DefinetlyNotAI]

@examon I don't have perm to re-open the issue for some reason

The issue came back in v1.0.27 - Same exact symptoms/reasons

I will open a new issue about this!