REGENT is an MCP server that hands an AI controlled root access to an OpenWrt router. You describe what the network should do in ordinary words, and it works out which commands that takes, in which order, and which service has to reload before the change means anything. A three-level access gate keeps reading always available while walling writes and destructive actions behind explicit permission, and a watchdog restores the configuration by itself whenever a change severs the very link it travelled over. Built for routed client mode, it joins an upstream Wi-Fi network and shares that connection onward with the VPN and ad-blocking the upstream cannot provide

Key Features

• Diagnosis, Not a Dump: Reads the whole configuration in one call and reports what is broken and why it stops traffic, instead of a listing to interpret by hand
• Whole Recipes: Composite intents like "share the uplink with clients" run as one ordered change across several config files, so the model never has to reassemble the steps itself
• Insurance Against Lockout: Before any risky change the config is snapshotted and a deferred restore is armed on the router, cancelled only once connectivity is confirmed — otherwise the router puts itself back
• Three Levels of Access: Reading always works; changing needs the write gate open; rebooting, flashing, and resetting need the gate and a separate confirmation on each call
• Secrets Stay In: Wi-Fi passwords, VPN keys, and subscription links are stripped before anything reaches the model, the command log, or the system log

Future Features

• apk Support: Package handling on OpenWrt 24.10 and newer, where opkg became apk
• Wider Device Coverage: Verification beyond the single TP-Link Archer C59 confirmed so far
• Guest Network: A separate isolated Wi-Fi brought up in one intent

Contributions are encouraged to enhance REGENT. Developers can fork the repository, create feature branches, and submit pull requests to collaborate on the project's evolution