Claude Code freezes with Virus Protection turned on

Hello,

I am not familiar with the tools mentioned, so I will write just a general speculation. Sorry.

Could it be that F-Secure is flagging the access pattern as ‘malicious’? No warnings or something like that is shown so. Any idea what could cause this and how to avoid it? I would prever not to tun off the Virus Protection every time I use Claude ;)

…

The problem is that Claude Code is freezing sometimes.

Just scanning/analyzing maybe. Processes, activities. In the background. Because it could be suspicious a bit or 'unknown'. Maybe requesting 'reputation' for something (within F-Secure Security Cloud), checking.

I mean, by "freezes" - did you mean something completely unusable then? For how long? From which point as 'starting point' (like launch, some certain action)?

Have you tried waiting to see what happens (like if F-Secure suddenly decided to show something)? Or how do you usually handle situations like this?

Is there can be anything that gets updated and occasionally necessitates a thorough re-analysis by F-Secure (other their own intelligence and databases)?

The workaround is probably to use File and Apps exclusion list (Excluding files or folders from scanning) or to report situation via official F-Secure support channels as a way to provide some diagnostic logs (so, they can improve something if this trouble is F-Secure based).

I would try to understand if there are improvements from frequency of use or the ability to wear out these freezes if they are related to F-Secure attempting to perform an analysis and flagging system activity as suspicious during usage or within those timeframes.

By the way, did you try to disable only certain options/settings in Virus Protection before completely turning it off? Just to know (maybe) what is exactly a main reason.

Well, that sounds like an overload too. Maybe resources of any type RAM, CPU, network or disk.

Because this does not happen when F-Secure Virus Protection is disabled… probably the reason for this is tool's activities. F-Secure might be weighing whether or not to block something, then deciding that everything is fine - resulting in no notifications or troubles other than a "delay".

It makes sense that such actions (or any other background stuff which may be suspicious or 'treated' as such) would force real-time scanning to remain vigilant and check all activities, but it is not entirely clear whether such an impact is expected. I mean, I will wait one-three minutes as part of my own expectations, but I am not sure that it is the best way to keep it for everyone.

If you can't find any way to adjust tool's own settings or its routine to be more 'friendly' with F-Secure - then, probably, I will suggest to contact their support via web-chat: https://www.f-secure.com/en/support as a way to suggest logs for analysing.

To use exclusions (which will likely work if to find a proper place/path or item/file to exclude) is always just a workaround; and is generally not recommended.

In my experience, I have two applications that sometimes "hang" for a while - I think no more than a minute - and I think this only happens when F-Secure is active on the system. If I use a version of this software without updates, such freezing gradually disappears. Or perhaps it happens if I use the software more frequently. The "information" is likely stored in the local cache (or sort of things), so F-Secure no longer scrutinizes it as closely.

Anyway, sorry for my speculation. Good if there will be any official reply. I think developers can also use such tools too and encounter related troubles (unless it is pinned to something like hardware).