[Bugs] We need to come up with a way to prevent users from shooting themselves in th...
Open
Bugs
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
**Mood:** 😔
**Category:** Bugs
We need to come up with a way to prevent users from shooting themselves in the foot in regards to cpu/memory usage across multiple sessions of copilot
---
| Field | Value |
| --- | --- |
| App version | 0.2.28 |
| OS | macOS 26.5.1 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 5 |
Contributor guide
Research direction
Start at the /chat path and reproduce the CPU and memory impact across multiple Copilot sessions using app version 0.2.28 on macOS. Determine what resource-usage behavior should be prevented and how success can be measured; the issue does not name files, tests, thresholds, or a specific implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100