[Bug]: Sophos CPU usage skyrockets after adding a repository folder to desktop app

Aperta
#56 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@aliarain ci sta già lavorando.

Dal 7/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

bug
GUI version

0.1.26

Operating system

macOS (Apple silicon)

Reproduction steps

With Command Code Desktop installed but not adding a repository, Sophos is essentially idle:

com.sophos.endpoint.scanextension 0.1%
SophosEventMonitor 0.1%
SophosCryptoGuard 0.1%

After adding a repository and using Command Code with it, Sophos CPU usage progressively increases.

For example:

com.sophos.endpoint.scanextension 133.2%
SophosEventMonitor 74.2%
SophosCryptoGuard 165.2%

and shortly afterwards:

com.sophos.endpoint.scanextension 154.2%
SophosEventMonitor 73.6%
SophosCryptoGuard 189.3%

So Sophos reaches roughly 370–420% combined CPU.

Removing the repository from Command Code immediately brings Sophos back to approximately 1–3% CPU.

I reproduced the same behaviour after reinstalling Command Code Desktop.

No issues with the CLI

Expected behavior

Adding a repository, including one containing tens of thousands of files and normal dependency/build directories, should not cause the system's antivirus/security software to enter a sustained hundreds-of-percent CPU state.

I would expect Command Code's indexing/file-watching logic to avoid unnecessary directories such as node_modules, build output, coverage, etc., particularly when they are excluded by .gitignore.

Actual behavior

This looks like an interaction between Command Code Desktop's repository discovery/indexing/file-watching behaviour and Sophos Endpoint's on-access scanning.

I do not know whether the underlying issue is excessive filesystem activity generated by Command Code, Sophos's handling of that activity, or an interaction between the two.

The fact that removing the repository immediately stops the Sophos CPU storm makes the repository/indexing behaviour in Command Code the most obvious place to investigate.

Happy to provide additional diagnostics if useful.

Screenshots, recordings, or sanitized logs
Image

Here is a video where I open the app, let it run without doing anything, the CPU goes up, then as soon as I close it, Sophos CPU usage drops immediately

https://github.com/user-attachments/assets/3d53447f-cb07-48b6-857f-fafc0c05c579

Safety check
  • I removed credentials and private project information from this report.
Lingua principale
Shell
Stelle
80
Fork
2
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CommandCodeAI/desktop

Tutte le issue di CommandCodeAI/desktop

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.