1.3 RC

Disclaimer AdGuard CLI is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

AdGuard CLI continues to expand its capabilities and move closer to our full-featured desktop apps. With v1.3, it becomes more powerful, more flexible, and easier to manage.

This release introduces DNS filtering and Encrypted ClientHello (ECH) support, adds userscripts and userstyles, and refines the update workflow to make it clearer and more consistent.

Added DNS filtering support

With DNS-level filtering enabled, unwanted domains, including ads, trackers, and malicious websites, are blocked before a connection is established. This adds an extra layer of protection and stops unwanted traffic at the earliest stage, preventing it from reaching your device.

Please note: DNS filtering is disabled by default.

To enable it, run the following command:

adguard-cli config set dns_filtering.enabled true

To disable it, run the following command:

adguard-cli config set dns_filtering.enabled false

Please note: By default, AdGuard CLI uses the system DNS server or AdGuard Non-filtering DNS server. You can manually choose a different server with the following command:

adguard-cli config set dns_filtering.upstream '[server address]'

To switch back to the default server, run the following command:

adguard-cli config set dns_filtering.upstream default

Encrypted Client Hello

Although HTTPS encrypts the content of your traffic, the name of the server you are communicating with is usually still visible. ECH encrypts this part of the connection as well, helping to prevent ISPs, DPI systems, and other intermediaries from seeing which domains you access.

Added userscript and userstyle support

You can install and manage userscripts and userstyles directly from the command line. Management commands follow the same logic as filters, so enabling, disabling, and removing userscripts works in a familiar way.

Other improvements

We’ve also made several minor fixes and unified the logic behind adguard-cli filters update and adguard-cli check-update. Both commands now use the same update-check mechanism and provide detailed, human-readable progress output.

Changelog

Improvements

• Added DNS filtering support #90
• Added full userscripts/userstyles support #118
• Added Encrypted Client Hello (ECH) support #111

CoreLibs (Filtering engine)

• Updated CoreLibs to v1.21.6

Improvements

• Enabled HTTP/3 filtering by default #2015

Fixes

• Do Not Track feature sends both DNT and GPC even on browsers which does not support them #1982
• Do not leak local.adguard.org resolution after enabling protection #1854
• MWITools does not work in AdGuard #2001

Scriptlets (JavaScript enhancement for filtering rules)

• Updated Scriptlets to v2.2.15

Improvements

• trusted-click-element — added support for React elements that don’t respond to native clicks #542

Fixes

• prevent-addEventListener scriptlet throws error when null is used as event type #539

AdGuard VPN CLI Install-Scripts:

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/release/install.sh | sh -s -- -v - for installing from Release channel

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/beta/install.sh | sh -s -- -v - for installing from Beta channel

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/nightly/install.sh | sh -s -- -v - for installing from Nightly channel

1.3

Disclaimer AdGuard CLI is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

AdGuard CLI continues to expand its capabilities and move closer to our full-featured desktop apps. With v1.3, it becomes more powerful, more flexible, and easier to manage.

This release introduces DNS filtering and Encrypted ClientHello (ECH) support, adds userscripts and userstyles, and refines the update workflow to make it clearer and more consistent.

Added DNS filtering support

With DNS-level filtering enabled, unwanted domains, including ads, trackers, and malicious websites, are blocked before a connection is established. This adds an extra layer of protection and stops unwanted traffic at the earliest stage, preventing it from reaching your device.

Please note: DNS filtering is disabled by default.

To enable it, run the following command:

adguard-cli config set dns_filtering.enabled true

To disable it, run the following command:

adguard-cli config set dns_filtering.enabled false

Please note: By default, AdGuard CLI uses the system DNS server or AdGuard Non-filtering DNS server. You can manually choose a different server with the following command:

adguard-cli config set dns_filtering.upstream '[server address]'

To switch back to the default server, run the following command:

adguard-cli config set dns_filtering.upstream default

Encrypted Client Hello

Although HTTPS encrypts the content of your traffic, the name of the server you are communicating with is usually still visible. ECH encrypts this part of the connection as well, helping to prevent ISPs, DPI systems, and other intermediaries from seeing which domains you access.

Added userscript and userstyle support

You can install and manage userscripts and userstyles directly from the command line. Management commands follow the same logic as filters, so enabling, disabling, and removing userscripts works in a familiar way.

Other improvements

We’ve also made several minor fixes and unified the logic behind adguard-cli filters update and adguard-cli check-update. Both commands now use the same update-check mechanism and provide detailed, human-readable progress output.

Changelog

Improvements

• Added DNS filtering support #90
• Added full userscripts/userstyles support #118
• Added Encrypted Client Hello (ECH) support #111

CoreLibs (Filtering engine)

• Updated CoreLibs to v1.21.6

Improvements

• Enabled HTTP/3 filtering by default #2015

Fixes

• Do Not Track feature sends both DNT and GPC even on browsers which does not support them #1982
• Do not leak local.adguard.org resolution after enabling protection #1854
• MWITools does not work in AdGuard #2001

Scriptlets (JavaScript enhancement for filtering rules)

• Updated Scriptlets to v2.2.15

Improvements

• trusted-click-element — added support for React elements that don’t respond to native clicks #542

Fixes

• prevent-addEventListener scriptlet throws error when null is used as event type #539

AdGuard VPN CLI Install-Scripts:

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/release/install.sh | sh -s -- -v - for installing from Release channel

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/beta/install.sh | sh -s -- -v - for installing from Beta channel

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/nightly/install.sh | sh -s -- -v - for installing from Nightly channel

1.3.33 nightly

• [Fixed] "Address already in use" on macOS while reloading protection in 1.3 nightly #121

1.3.29 nightly

Minor fixes

1.3.28 nightly

This nightly contains stability fixes for release

1.3.22 nightly

• [Feature] Add DNS filtering support to AdGuard CLI #90
• [Other] [AG CLI] Add support for Encrypted Client Hello (ECH) #111
• [Feature] Add full userscripts/userstyles support #118

1.2.34 nightly

Minor fixes

1.2.2 RC

Disclaimer AdGuard CLI is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

We fixed an issue reported by users and updated our libraries while we were at it. Now, nothing will interfere with ad blocking.

AdGuard VPN CLI Install-Scripts:

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/release/install.sh | sh -s -- -v - for installing from Release channel

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/beta/install.sh | sh -s -- -v - for installing from Beta channel

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/nightly/install.sh | sh -s -- -v - for installing from Nightly channel

1.2.2

Disclaimer AdGuard CLI is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.

We fixed an issue reported by users and updated our libraries while we were at it. Now, nothing will interfere with ad blocking.

AdGuard VPN CLI Install-Scripts:

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/release/install.sh | sh -s -- -v - for installing from Release channel

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/beta/install.sh | sh -s -- -v - for installing from Beta channel

curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/nightly/install.sh | sh -s -- -v - for installing from Nightly channel

1.2.29 nightly

• [Fixed] Cannot connect when the proxy has been manually configured #112
• [Fixed] crashes with a core dump #110
• [Other] Show "how to install certificate" link in `adguard-cli config` when https_filtering changed/mentioned #106