Hello! Thank you very much for your response! We greatly appreciate the chance to discuss Apple's technologies with their engineers!
[quote='798218022, DTS Engineer, /thread/760964?answerId=798218022#798218022']
If you run a tool from Terminal, then Terminal is considered the responsible code and, as a system app, it’s not subject to local network privacy.
[/quote]
I have conducted more experiments and have attached the new results to FB14581221 (bundled_as_cli_term). If you run the bundled application for the first time through the terminal, a prompt will appear for the Terminal.app. This is not the case for me, but the results of the experiment don't match your expectations:
[quote='798218022, DTS Engineer, /thread/760964?answerId=798218022#798218022']
If you run an executable as a launchd daemon, it runs as root and local network privacy does not apply to code running as root.
[/quote]
Here my experiments also show different results - if the bundled application is launched as a launchd daemon, the prompt will appear, even though the app runs with root privileges (see "bundled_as_daemon" in the attachments for FB14581221):
The latter scenario has an impact on the user experience of my application and I would like to prepare carefully for changes in the macOS. It would be helpful if you could provide information about the expected outcomes of the scenarios mentioned.