This is exactly the things we are aiming for, as Portmaster is intended to be as easy to use as possible. We currently already have special support for AppImag

This is exactly the things we are aiming for, as Portmaster is intended to be as easy to use as possible. We currently already have special support for AppImage and Snap packages on Linux and Windows Store apps and "svchost.exe services" on Windows. Additionally, we can detect common interpreters on Linux and correctly match the script file instead of the interpreter. The support for these systems is implemented as "tags", which are attached to a process internally in Portmaster. These tags are then used to match a settings profile. You can find the implementations here: https://github.com/safing/portmaster/tree/develop/process/tags https://github.com/safing/portmaster/tree/develop/process/ta... We almost had an implementation ready for what you want (matching the parent process), but we had to abort due to some difficulties in matching: The questions we could find a good answer for, was where do we put the information whether which binaries are merged into / inherit from the parent? The ideal scenario from a UX perspective would be to declare it on the parent as an "include all sub-processes" option. But this would mean we would need to fully resolve all parent processes including their settings every time we evaluate a process. We deemed this to be too slow and too complex for a quick and clean solution. If you or anyone else has a great idea, I'd be happy to have a call to discuss.