platform binaries running in background session is not owned by any user since they're running as root, are there any general guidelines on how TCC should work with system process. It's fairly clear now that user involvement is needed for TCC, but how does TCC work with system process? Anybody have an idea?

Have you found a solution to this? I've running into same issue since Big Sur released, the error message I've got is like: Refusing TCCAccessRequest for service kTCCServiceBluetoothAlways from client ... in background session I've been searching around and haven't found a solution for this problem, like you said, if TCC can block bluetooth permission for platform binaries in the background session, all plugins need bluetooth access would stop working. If we can't found solution from this forum, anybody knows where else could we look for help?