@ character causing lag spike + large use of computer resources
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.825.51511
What subscription do you have?
x20
What platform is your computer?
No response
What issue are you seeing?
Huge lag spike on my computer (not just Codex) when using @ character, and my laptop immediately gets significantly hotter and I see memory gets maxed out. Maybe the search is inefficient and it over-recruits resources?
What steps can reproduce the bug?
Type @ on a thread - though I found that sometimes it works fine for some reason
What is the expected behavior?
No response
Additional information
No response
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
Start by reproducing the issue in Codex App version 26.825.51511: type @ on a thread and observe system lag, heat, memory use, and whether the behavior is intermittent. Trace the @-triggered search or resource usage to identify the regression; done means typing @ no longer causes a significant lag spike or resource exhaustion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100