Disclaimer Adguard for Mac is not an open-source project. We use GitHub as an open bug tracker for users to see what developers are working on.
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.
Changelog
Improvements
- Introduced compatibility lists specifically for AdGuard for Mac #5
- Removed the Block Java setting #1705
- Updated AdGuard icons and logos, copyright year, and capitalization #1706
Fixes
- Scrollbar malfunction in the Filtered applications tab
#1192 - A bug causing the main app window to automatically pop up during macOS startup #1699
- Inaccurate titles within AdGuard’'s Settings/Preferences screens #1734
- Erroneous User rules filter timestamp is hidden until modified #1737
- Unexpected Noname entries in Filtered Applications menu #1772
- Firefox filtering state not retained in AdGuard for Mac v2.20 beta build #1774
- Excessive disk writes caused by the
agflm_standard.dbjournal mode #1710 - Text and icon colors of the Settings tabs do not match system behavior #1696
CoreLibs (Filtering engine)
- Updated CoreLibs to v.1.22.29 #1754
Improvements
- Prevented domain leaks for Local.adguard.org resolution while protection is turned on #1854
- Added support for filtering of HTTP/3 proxies #1957
- Refined the Do Not Track utility to avoid dispatching DNT/GPC headers to incompatible browsers
#1982 - Enabled HTTP/3 filtering out of the box for Beta and Nightly testing channels #2014
- Turned on HTTP/3 filtering by default for all stable release users #2015
- Synchronized verification caching rules to match Chrome’'s implementation standards #2025
- Added full support for filtering HTTP/2 proxy connections #2054
- Changed the evaluation of iframe size for content script injections
#2059
Fixes
- Parsing errors occurring within
match_context_createroutines #124 - Freezing of Firefox with a Host contacted, waiting for reply status due to locked TCP socket connections #2058
- Latency issues in QUIC/HTTP/3 processing leading to automatic fallbacks to HTTP/2
#2062 - OCSP validation routines failing to properly block connections targeting compromised or revoked SSL certificates
#2069
Scriptlets (JavaScript enhancement for filtering rules)
- Updated Scriptlets to v2.4.2
Improvements
- Added the
google-ima3-dairedirect rule [#239](AdguardTeam/Scriptlets#239) - Introduced the
trusted-json-setscriptlet #308 - Expanded JSON-focused scriptlets to support advanced JSON path queries #522
- Enhanced
log-addEventListenerwith a parameter to manage overridingaddEventListener#551
Fixes
cancelBubblecauses unexpected errors intrusted-click-element#555
ContentScript
- Updated ContentScript to v3.2.0
DnsLibs (DNS filtering engine)
- Updated DnsLibs to v2.10.1 #1742
Improvements
- Added ability to update upstreams list without reloading filters #248
Fixes
- Crash caused by segmentation error during DNS proxy setup on MIPS routers #136
- Missing TCP filtering within Apple Network Extensions #264
- Intermittent failures during DNS-over-TLS upstream availability checks #263
- Missing AdGuard certificate issues on
hitomi.la#2055