The copilotd daemon used to connect to my WSL environment sits at 20-30% CPU ...
Open
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
The copilotd daemon used to connect to my WSL environment sits at 20-30% CPU _per instance_ while _idle_. This seems excessive.
---
| Field | Value |
| --- | --- |
| App version | 1.1.10 |
| OS | Windows 10.0.26200 |
| Theme | Notionish |
| Path | / |
| Tenure | Week 10 |
Contributor guide
Research direction
Start by reproducing the reported idle CPU usage for the copilotd daemon in the WSL environment on the listed app version and Windows version, checking usage per instance. Done means identifying and addressing the excessive idle usage, then confirming that each instance no longer sits at 20–30% CPU.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100