Processes still run after installing the script on Mac OS Sonoma

[Krasnomakov]

Trial proxy and AUSP processes appeared to be running after the script was installed.

[term7]

Could you please specify which exact processes you mean? We did update the KillSiri script to terminate the following processes (on our test machine we previously missed com.apple.siri-distributed-evaluation):

com.apple.siri.embeddedspeech
com.apple.SiriTTSService.TrialProxy
com.apple.siri-distributed-evaluation
siriactionsd
sirittsd
SiriAUSP
SiriTTSSynthesizerAU
siriknowledged
siriinferenced
assistantd

SiriTTSService.TrialProxy (a specific trial proxy service used by Siri) has been successfully terminated on our test machine (MacOS Sonoma 14.5). We do not want to terminate every process called trial proxy - only the one that is used by Siri. Also on our machine there are still two AUSP processes running, which our script did not terminate because it is not looking for them: MauiAUSP and MacinTalkAUSP

As far as we know both processes relate to text to speech functionality which can also be used as a tool that is not necessarily connected to Siri. If you have more detailed information, i.e. documentation about the processes you have still running on your machine and what these processes exactly do in relation to Siri, please send us a link to this documentation. If they are important for Siri we will consider including them in our little script...

[Krasnomakov]

I can see these two periodically. Sometimes they work, and sometimes don't.

com.apple.SiriTTSService.TrialProxy
SiriAUSP

[term7]

Yes, that is expected behaviour (to some extend).

We have not found a way to disable Siri permanently since it is respawned by MacOS periodically. If you want to disable Siri permantly you have to disable Apple's System Integrity Protection (SIP), which is something we would not recommend for security reasons. What our script does: it sets up a LaunchDeamon and a LaunchAgent that check whenever Siri is creating log files etc. in specific folder locations (working folders for Siri). As soon as this happens, a script checks for all the processes related to Siri that we mentioned earlier - and terminates them. It then proceeds to delete all content (log files, etc.) in the Siri working folders, which forces Siri to recreate them once it becomes active again - which in turn will trigger our script once more...

This is a cat and mouse game. It also means that some processes related to Siri will become active every now and then.

Furthermore you should not only rely on this script to switch off Siri, but also go into your System Settings and turn off everything that is related to Siri as well.

However, attempting to disable Siri just in your System Settings wont stop all Siri processes, since they are baked into MacOS - which is the whole reason why we wrote this script in the first place: to terminate Siri processes that are respawned even though we did everything we could to disable Siri in our System Settings...

Is this helpful for you in any way?