Hazel 5 on Clean Big Sur Install Can't Kill HazelHelper

I recently did a clean install of Big Sur on my MBP. I'm a multi-year Hazel user, but choose to re-create all rules to reduce potential for issues. All seems to be working on the Hazel front.

However, I would like to kill the HazelHelper process and unable to do so. Using both Activity Monitor and the command line, I've attempted to both quit/force quit HazelHelper and hazelnotifyd and after they briefly appear to stop (and the Hazel icon in the menu bar disappears) it automatically restarts and the menu bar item reappears. I have done this multiple times in a row with no success.

Is there some other process that is running that is causing this behavior? It there another preferred way to kill/stop the Hazel helper without completely uninstalling?

Thank you.

Is there a reason you want to kill them? They are necessary for things to run.

I'm having the same problem on 10.13.6, following your rules to restore my lost rules in Hazel 4. Can't kill HazelHelper and thus am not able to restore my settings from before the update to version 5...

In my workflow, I use Hazel when I am in particular work environments where it handles tasks that are unique to that environment.

So, pre-5, I would start-up the Hazel process when I was in that environment and it would process/monitor rules that were applicable. When I am not in that environment, I don't use Hazel and, in general, I prefer not to have any service active in the background when there is no need for that service.

I have and continue to use an automation tool (Alfred) to allow me to quickly switch the needed services/apps/settings/etc. when I enter/leave that environment.

I realize this type of workflow is non-standard, and understand that Hazel cannot realistically support every situation. I also recognize that there is a "pause" where it no longer processes but the service is still active/running in the background. So, I am willing to handle starting and stopping the service on my own.

It just appears there is another process watching for this process that restarts it every-time it is stopped. I suspect I can stream logging messages in Console to find out which one is doing it, but I thought I'd ask.

Thank you again for your time and consideration and I appreciate you clarifying the question.

Is there a reason why you can't start/stop Hazel instead of killing the process? The process itself is managed by launchd (which handles processes in the OS). There is a way to disable it but I still don't see the need to kill the process itself.

The applications I use that also have a helper app (1) provide an independent GUI option not to load at login (so if you want to disable for a number of reasons at launch without uninstalling) and (2) support either starting or stopping them fully from the command line/activity monitor

This was just a new twist for me. The only way I could find to remove the XXXXXXXXXX.com.noodlesoft.HazelHelper from the list of services being managed by launchd was to completely remove the entire Hazel app.

If that is designed as intended, no problem. I just wanted to make sure I wasn't missing something. I love everything you've done with the new version and I'm sure it was a ton of work. Hats off to the great effort! It just didn't fit my workflow requirements so I wanted to reach out and clairfy.

Have a great day!

You can do that via launchd bit in general, I would recommend against it. If you find the helper using up any measurable resources while stopped, please let me know but I think you make things more difficult if you insist on killing the process.

Ok, thanks, understood. I appreciate your time and help.