I am having issues as well. We are using a Gitea CI binary that accesses a few local IP addresses through TCP. If we run it from Terminal itself it works fine /Applications/DevTools/act_runner -c config.yaml daemon (no "local network" permission dialog either. It just works) But as soon as we run it through a LaunchAgent the local IP addresses become inaccessible: Error: unavailable: dial tcp 192.168.1.239:10890: connect: no route to host The dialog for allowing local network access doesn't appear either. The config file is located in ~/Library/LaunchAgents and is setup like this: <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>org.gitea.act_runner</string> <key>LowPriorityBackgroundIO</key> <false/> <key>LowPriorityIO</key> <false/> <key>KeepAlive</key> <true/> <key>RunAtLoad</key> <true/> <key>ProcessType</key> <string>Interactive</string> <key>WorkingDirectory</key> <string>/Applications/DevTools</string> <key>StandardErrorPath</key> <string>logs/ci.err.log</string> <key>StandardOutPath</key> <string>logs/ci.out.log</string> <key>ProgramArguments</key> <array> <string>/Applications/DevTools/act_runner</string> <string>-c</string> <string>config.yaml</string> <string>daemon</string> </array> <key>SessionCreate</key> <true/> </dict> </plist> Is this related to this particular issue? And if so, would there be a workaround in this case?