That is, you will need to clone our repository, 'build' the extension, switch the browser to Developer Mode, and only in this case you will be able to use the tools for debugging filters. But there is a caveat: you need to install the extension in an 'unpacked' form. The point is that you can still get information about which rule triggered. Every day, billions of people use Google to find reliable information, get to their destination, connect with loved ones, and more. Instead, filter developers will have to use the mechanism recommended by Chrome developers. The current version of the prototype does not implement a filtering log. By comparing the Chrome statistics with the results of the old engine, we will get a rough picture of how requests are processed. AdGuard also speeds up page loading, allows you to manage DNS servers and web requests, and has in-app support. With them, you can block ads in browsers and apps, prevent websites and companies from tracking you, and protect yourself from phishing and malware. It won't do anything with the requests, only show which rules may have been applied. AdGuard offers apps for Android, iOS, Windows, and Mac. So, when you open the filtering log, an engine that works by the rules of Manifest V2 will be launched. But we can come up with a peculiar alternative, which we plan to do in the final version of the extension. Due to the fact that Chrome itself now blocks requests and shares statistics only with extensions unzipped and installed in Developer Mode, we can't implement the filtering log as we used to.

Adguard chrome web store