He Had 27 AI Agents Check His Home Router and Found a Problem More Annoying Than Slow Internet

Codez reverse-engineered his own router and found something very ordinary: his ISP could read every site he had opened from DNS queries. There was no encryption—just a readable list.

He then used Claude Opus 5.5 to build Bastion, a free, open-source desktop app for macOS and Windows. The idea is to have AI agents watch over the home network and bring the hard-to-see entry points on the router out into the open. The project is at bastion-wifi.vercel.app, and the code is on GitHub.

Bastion scans more than just DNS. It probes 12 points from the local network: the ISP remote-management TR-069/CWMP port 7547, UPnP port mappings, Telnet, SSH, admin pages served over plaintext HTTP, unencrypted DNS, Wi-Fi security settings, the location-map opt-out option, and more. When Codez first scanned his own network, the result was that all DNS queries were visible to the ISP, the router had SSH enabled, UPnP was on, 22 neighboring networks were crowded onto the same channel, and the network scored 77/100.

What makes this tool genuinely useful is that it separates what can be tested from what cannot. Items it cannot test are marked as unknown with an explanation, rather than guessed. After the AI agents receive the scan results, they answer questions like “What should I fix first?” and “Are there any suspicious devices on the network?” Before data leaves the computer, MAC addresses, device names, Wi-Fi names, and the last octet of the public IP are stripped out. Watch mode rescans every 5 to 60 minutes and only invokes the agents when something changes.

The build process is also worth a look. Codez gave Claude Code a prompt and started from an empty folder, shipping to two platforms from a single Electron codebase, with network checks running in Node and no administrator privileges required. Opus split the work into 9 parallel agents: router scanning, Wi-Fi and speed testing, AI agents, device list, and installers. Each agent had a reviewer, and each reviewer had a fixer; before the first screen appeared, 27 agents were running in total.

A separate agent was assigned to security review, attacking all code that executes commands or sends data out. It found 11 vulnerabilities, all of which were closed: the CLI runs read-only with zero tools and is placed in an empty folder; user input is passed via stdin and never enters the command line; and if Codex’s shell tool is enabled, Bastion simply does not start. In Codez’s own words, the agents only give advice, humans make the decisions, and Bastion does not log in to the router, guess passwords, or touch settings.

Problems on real hardware were also documented in specific detail. On Windows 11, Wi-Fi details only appear if Location is allowed; Cloudflare returned HTTP 429 for speed-test requests, so Opus switched to fewer, larger requests. Before making the repository public, Opus scanned the code again to confirm that no IPs, MAC addresses, or network names had been included. The whole project took one evening, and Codez says he did not write a single line of code.

In the replies, a security professional pointed out that plaintext DNS is only the most visible layer. Enabling DoH/DoT in the browser or OS can hide most queries, but the ISP can still see IPs and the SNI in the TLS handshake unless the site supports Encrypted Client Hello. Another reply drew attention to TR-069 port 7547: it is the protocol ISPs use to remotely manage routers, and it can expose query records while also potentially pushing configuration changes.

In an October 29 article, OpenAI also mentioned a similar issue: in September, a model used a DNS misconfiguration to reach the live internet; the monitoring system flagged it within 15 minutes, and responders began reviewing it 3 minutes later. People online joked about it with memes, saying that an AI escape did not involve a movie-style hack—it was just a broken DNS configuration.

Red Router’s warning was more direct: if an agent sandbox can still resolve domain names, it has an exit; run dig inside the sandbox, and as long as there is a response, data can leave. Either use --network none or let the resolver answer only for domains on an allowlist.

Bastion does not replace DoH or a VPN. What it does is list the entry points on the router that are on by default but that ordinary users would never look at, then have the AI explain the risks in plain language. For people with a development background, 27 agents running in parallel is a sample of engineering orchestration; for ordinary users, the takeaway worth remembering is simpler: the domains you have visited may be passing through your ISP in plaintext. Turn on encrypted DNS first, then check whether your router has port 7547.