copilot cli in wsl spinning on the cpu with an unresponsive tui

[neerajsi-msft]

Describe the bug

I experienced unresponsiveness and 100% cpu usage while using the copilot cli. I had a long session going with claude opus 4.6 1M, so maybe the large amount of state was causing issues.

I collected a short trace of the process with edge devtools.

The symptoms are 100% cpu usage in "MainThread", as displayed by top.

wsl-github-copilot-mainthread-spinning.gz.

Affected version

GitHub Copilot CLI 1.0.10

Steps to reproduce the behavior

This is reproing whenever the model is running and "thinking" or doing some other local agent actions.

I have attached the devtools trace.

Expected behavior

No response

Additional context

No response

[danparisi]

In my case, it happens about twice a day thet copilot cli execution over WSL completely freeze my laptop and I'm forced to restart. This is really frustrating. I guess it is the same bug, I also see high CPU percentage usage.

[ilsubyeega]

this happens on non-WSL, linux/nixos here. using 100% of single core, investigating this with gpt5.4 suggests TTY redraw/spinner/render loop related.

For reproducing, do some session and then scrolling will also give you full cpu100% horse power usage

[examon]

This should be resolved as of v1.0.13, which includes render and polling optimizations that significantly reduce CPU usage during streaming. If you're still seeing high CPU usage specifically when scrolling through long sessions, that may be a separate issue - please feel free to reopen or file a new issue in that case.