- Network
- VPN · Gotham VPN
- DNS · 28 ms
- Night Drive’s own proxy
- Server
The app’s proxy isn’t answering.
For proxy and VPN users
Behind a system proxy, every app looks like the proxy app. Kilobat puts each app’s traffic back where it belongs, shows which node it went through, and tells you when the proxy, the VPN or your DNS lets you down.
brew install seifip/kilobat/kilobatThe app’s proxy isn’t answering.
# Which rule and node Telegram took
$ kilobat proxy routes --app Telegram
# Do DNS or IPv6 skip the tunnel?
$ kilobat vpnWith a system proxy, apps talk to the proxy core on your own Mac, and the core makes the real connection out. Monitors that only see sockets charge it all to the core. Kilobat follows each loopback connection back to the app that made it.
Health › Where traffic leaves checks the proxy and the VPN together, and Why can’t it connect? adds a Proxy app step.
Apps talk to 127.0.0.1, so monitors charge it all to the core.
Each app is charged for its own traffic; the core reads “Carries other apps’ traffic” and nothing is counted twice. Free
A system proxy still points at an app that isn’t running.
Named as a dead system proxy, with what to switch off. Free
DNS goes to the café’s router, or IPv6 skips the tunnel.
Checked against the tunnel and named as a leak. Free
A proxy in TUN mode and a VPN both want the default route.
Flagged as two tunnels fighting. Free
One node in the group stopped answering.
Each group’s current node is timed, and the dead one named. Free
macOS content filters never see connections to 127.0.0.1.
Kilobat says so, and suggests TUN mode or the proxy’s own rules. Free
Routes
With a Clash-compatible proxy, each app’s row shows the node it went through, such as “via HK-01 · 2 direct”, and its tooltip lists each host, node and rule. Kilobat reads the API address and secret from the proxy app’s own config and never shows the secret.
# Proxy apps, their mode and TUN, and what’s wrong
$ kilobat proxy
# Which rule and node an app took
$ kilobat proxy routes --app Telegram
# How fast each group’s current node answers
$ kilobat proxy test
# The VPN, and whether DNS or IPv6 skip it
$ kilobat vpnPer-app routes need a Clash-compatible API; everything else works with any of them. AI agents get the same through the MCP tools get_proxy_status, test_proxy_nodes and check_vpn. Read the docs.
kilobat proxy, vpn and the MCP toolsPro is $19 once for two Macs, with a 7-day free trial and 14-day refunds. Free for students.
No. Kilobat only reads: the system proxy setting, the proxy app’s config and its local API. It never switches nodes, edits rules or touches the VPN. When something needs changing, it tells you what to change in your proxy app.
With a system proxy, apps connect to Clash on 127.0.0.1, and Clash makes the real connection out. Monitors that only see sockets charge it all to Clash. Kilobat matches each app’s loopback connection to the proxy port and counts it as that app’s internet traffic.
Kilobat finds Shadowrocket on a Mac with Apple silicon and counts traffic through it for the right app. Shadowrocket has no Clash-compatible API, so the per-app node and rule aren’t shown for it.
Everything on this page is free: the attribution, the routes, the checks, the CLI and the MCP tools. Blocking, profiles, budgets and history are part of Pro, $19 once, with a 7-day free trial.
brew install seifip/kilobat/kilobat