Copilot TUI hogs CPU
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Describe the bug
When I open copilot TUI, it hogs one CPU (~6-7% on a 16 core machine).
After I run a prompt, that number multiplies to e.g. 2, 3 or 4 CPUs hogged while the TUI sits idle.
Affected version
GitHub Copilot CLI 1.0.83.
Steps to reproduce the behavior
- start copilot TUI, observe CPU usage (sometimes i need to type a bit in the prompt box for the issue to appear)
- run a prompt or two, observe CPU usage
Expected behavior
copilot TUI CPU usage is negligible while the program sits idle.
Additional context
Ubuntu 24.04, x86_64, GitHub Copilot CLI 1.0.83..
Logs below. I opened a session, typed in the prompt box (already 1 CPU hogged at that point), then gave a plan command. after the plan.md was written and the TUI was idle, it used 3-4 CPUs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report on Ubuntu 24.04 with GitHub Copilot CLI 1.0.83, first observing an idle TUI and then running one or two prompts. Inspect the supplied process-1788769402724-57168.tar.gz logs and compare CPU usage before and after the prompt. Done means idle TUI CPU usage is negligible after opening and using the prompt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- cli, operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100