In AdGuard for Mac v2.20, we’ve renewed the app’s visual style, changed the UX workflow related to system permissions in macOS, added new browsers to the default filtering list, updated our filtering engines, and fixed a number of bugs.
System permissions for AdGuard
AdGuard requires
Files and Folders permission to install and verify AdGuard Browser Assistant in Chrome, Edge, and Gecko-based browsers.
In macOS 27, access to third-party browser profile folders has been restricted. Previously, when access was denied, AdGuard displayed a
Not supported status, which didn’t make it clear for users that the issue could be resolved by granting additional permissions.
In AdGuard for Mac v2.20, we’ve improved this workflow:
- The Not supported status is replaced with an Allow access button on the Assistant tab. It opens Files and Folders settings, where you can grant the required permission. Once access is granted, you can install the Assistant
- A notice is added to the main window. It appears if your default browser isn’t Safari and AdGuard doesn’t have access to its folder, and takes you to the Assistant tab
- The Enable Browser Assistant notice now appears when the Assistant isn’t installed in your default browser. You can dismiss it by clicking on the > button
- The first-launch wizard now uses the same Allow access button
These changes should make AdGuard for Mac more convenient for users who prefer third-party browsers on macOS.
Other changes
We’ve expanded the list of browsers filtered by default, adding popular names like DuckDuckGo and Naver Whale. Also, AdGuard for Mac now supports LibreWolf. Plus, we’ve set up a
Compatibility repository in GitHub, where users can submit their browser support issues, or even open pull requests for us to review and put out the necessary changes in later updates.
We’ve also added Quad9 to the list of DNS providers that support DNS-over-QUIC.
The app’s visual style is being refreshed as well: we renewed the logo and system tray icons, updated the description of the
Block WebRTC setting, and removed the
Block Java setting.
Lastly, we’ve fixed a number of bugs that interfered with the app’s correct functioning and updated CoreLibs and DnsLibs.