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

Offen

#56 erstellt am 03.9.2026 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@aliarain arbeitet bereits daran.

Seit 07.9.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

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

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.

Vorherrschende Sprache: Shell
Sterne: 80
Forks: 2
PR-Merge-Kennzahlen: Keine gemergten PRs in 30 T.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus CommandCodeAI/desktop

install.sh: asset matcher still greps for CommandCodeAI/gui — Linux/macOS installs can never resolve a release Offen

Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 85/100

CommandCodeAI/desktop#107 · Erstellt am 23.9.2026
[Feedback]: add copy block under a code block Offen

enhancement

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100

CommandCodeAI/desktop#94 · Erstellt am 18.9.2026
[Feedback]: Add Expand & Collapse for changes Offen

enhancement

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100

CommandCodeAI/desktop#66 · 1 Kommentar · 2 Reaktionen · Erstellt am 15.9.2026
[Feedback]: Guard against CPU saturation from concurrent background work Offen

Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 30/100

CommandCodeAI/desktop#109 · 1 Kommentar · Erstellt am 23.9.2026
[Bug]: Drop-to-attach overlay stays stuck after interrupted drag Offen

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 30/100

CommandCodeAI/desktop#108 · 1 Kommentar · Erstellt am 23.9.2026

Alle Issues in CommandCodeAI/desktop