The Next VPN Works Prototypes: A 14-Week Beta for AI Agents and a Real Gateway Pilot for Scope

On October 1, 2026, the plan was a 14-week Beta for AI agents and a gateway pilot for Scope. A week later the project took a different turn: it rebuilt VPN Works as one core with plugins first. Here’s what became of each part of the plan.

The Beta plan was a list of additions to the Agent: a WireGuard route, limits on files, walls that report, macOS, one-step installs, recipes for real agents, and four weeks of real agents running under vpnw every working day. Scope’s part was a pilot on a real company gateway.

Before adding more, the project looked at what it had: five engines that each worked and didn’t add up to one thing. Adding seven features to one of them would have made that worse. So the platform came first, and the Beta’s items now land as platform releases, one at a time.

Done

A WireGuard route, inside vpnw. Exactly as planned: brought up inside vpnw’s own process, no root, no new network interface, nothing changed for other programs. Shipped in 0.4.0 on October 9. WireGuard paths

A platform to build the rest on. Not in the plan at all, and the reason the plan changed. Shipped in 0.3.0. What moved where

Still to Do

Limits on files. Still needed: vpnw limits the network only.

Walls that report. A program that tries to go around vpnw still fails quietly. Recording those attempts as events would fit the platform well.

macOS. vpnw runs on macOS now, WireGuard included, but it can’t seal a program there. That’s still the hardest open problem.

One-step installs and CI recipes. Ready-built binaries exist for Linux and macOS; packages and CI steps don’t yet.

Real agents, every day. Still the test that matters most, and still to come.

Scope’s gateway pilot. Waits for gateway mode, where vpnw guards every device behind a machine.

No Dates

The new plan has an order and no dates. Each release ships when its tests pass. Roadmap