AdGuardian Term is an open-source, unofficial terminal companion for AdGuard Home — written entirely in Rust. It connects directly to your AdGuard Home HTTP API and renders a live, keyboard-driven dashboard right inside your terminal. Instead of opening a browser to check on your network’s DNS activity, you can launch AdGuardian Term over SSH, inside a tmux pane, or on the same machine running AdGuard Home, and get a real-time view of every query, block event, and filter hit without leaving the command line. It makes no external requests beyond your own AdGuard instance and crates.io (for update checks), runs as a single self-contained binary, and is fully unit-tested.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/lissy93/adguardian-term/llms.txt
Use this file to discover all available pages before exploring further.
Key Features
Real-time Query Monitoring
Fetches and displays all DNS queries as they happen, giving you a live view of exactly what every device on your network is resolving at any given moment.
Block and Allow Stats
Shows a running count of queries that have been allowed, filtered, or blocked by AdGuard Home, so you can gauge how hard your filters are working at a glance.
30-Day History Chart
Renders historical query count data across the last 30 days directly in the terminal, letting you track usage trends and spot unusual spikes in network activity.
Filter Lists
Displays all active filter lists configured in your AdGuard Home instance, showing which ones are actively intercepting the most queries.
Lightweight & Portable
Ships as a zero-dependency executable (or a 12 MB Docker image). No browser, no Electron, no Node.js — just a single Rust binary that runs anywhere.
Docker & Deployment
Run AdGuardian Term as a container with a single
docker run command, or access the dashboard from a browser via the web mode integration.About AdGuard Home
AdGuard Home is a free, open-source, self-hosted network-wide ad and tracker blocker. It works by acting as a DNS server for your local network: when a device tries to resolve a tracking or ad-serving domain, AdGuard Home returns a black-hole address instead, silently blocking the request before any connection is made. Beyond ad blocking, it offers encrypted DNS (DNS-over-HTTPS, DNS-over-TLS, DNSCrypt), parental controls, per-device configurations, custom DNS rules, and malware/phishing domain blocking. AdGuard Home ships with its own web UI, but that requires a browser and a manual page refresh to see what’s happening. AdGuardian Term fills the gap for anyone who lives in the terminal: it polls the AdGuard Home HTTP API on a configurable interval (default: every 2 seconds) and streams the results into a live TUI dashboard — no browser required.Requirements
Before running AdGuardian Term, make sure you have the following in place:- AdGuard Home v0.107.29 or later — AdGuardian Term checks the version reported by your instance on startup and will refuse to run against older versions that lack required API fields.
- Network access to the AdGuard Home HTTP API — AdGuardian Term connects over HTTP (or HTTPS if configured) to the AdGuard Home control API. The machine running AdGuardian Term must be able to reach the AdGuard Home host on its configured port (default:
3000). - AdGuard Home credentials — a username and password configured in AdGuard Home. AdGuardian Term uses HTTP Basic Auth to authenticate every API request.
AdGuardian Term runs entirely locally. Other than an optional version check against crates.io at startup, it makes no outbound requests to any external servers — only to your own AdGuard Home instance.