Technology1 min read

Show HN: Auto Dismiss Mac OS "Allow <app> to find devices on local networks?"

By · Published by Everything Blog

In short

The tool operates as a background launchd agent written in a single Swift file with no external dependencies, ensuring it consumes zero CPU while idle. Leveraging macOS Accessibility permissions, it detects prompt windows generated by UserNotificationCenter and clicks "Don't Allow" within a fraction of a second. Users retain flexibility through customizable grace periods, an allowlist, and temporary pause commands, and they receive notifications naming the affected applications. Permissions can still be adjusted manually afterward within standard System Settings.

Key points

  • The open-source tool runs persistently across reboots as a launchd agent while consuming…: The open-source tool runs persistently across reboots as a launchd agent while consuming no CPU during idle periods.
  • The utility exclusively clicks "Don't Allow" and never grants network access or modifies…: The utility exclusively clicks "Don't Allow" and never grants network access or modifies underlying operating system files.
  • Users can delay automated dismissals using customizable grace periods or manage exception…: Users can delay automated dismissals using customizable grace periods or manage exceptions via an integrated allowlist.

Sources checked by our analysis pipeline: 1

Auto-dismisses the macOS prompt:

Allow "Google Chrome" to find devices on local networks? This will allow the app to discover, connect to, and collect data from devices on your networks.

It presses Don't Allow for you, within a fraction of a second, every time. Zero CPU while idle. Survives reboots. One Swift file, no dependencies.

macOS (Sequoia and later) shows this prompt the first time an app touches the local network. The decision is supposed to be remembered. For many apps it isn't, so the prompt comes back on every launch, often for apps you aren't even using:

- Chromium browsers (Chrome, Brave, Edge, Island, Arc) copy their own app bundle into a random temp folder at launch so the code signature survives in-place updates. macOS keys the Local Network decision to that random path, so the next launch looks like a brand-new app. Your Privacy settings fill up with duplicate "Google Chrome.app" rows that no longer point at anything.

- Apps with versioned install paths (anything that installs into

.../versions/1.2.3/

) get a new row per update. - Misattributed…

Technology