<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Beta on VPN Works</title>
    <link>https://vpnw.com/tags/beta/</link>
    <description>Recent content in Beta on VPN Works</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vpnw.com/tags/beta/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Next VPN Works Prototype: A 14-Week Beta That Puts Real AI Agents Under vpnw</title>
      <link>https://vpnw.com/the-next-vpn-works-prototype-a-14-week-beta-that-puts-real-ai-agents-under-vpnw/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/the-next-vpn-works-prototype-a-14-week-beta-that-puts-real-ai-agents-under-vpnw/</guid>
      <description>&lt;p&gt;The Alpha answered one question. Can a small program seal an AI agent in and control every connection it makes? On Linux, on one machine, with a stand-in agent, the answer was yes. The next prototype, the Beta, takes on the harder question: does it hold up with real agents doing real work, on the machines where agents actually run?&lt;/p&gt;&#xA;&lt;p&gt;The Beta is planned at about 14 weeks with two or three people. It keeps the same engine and the same four commands: run, trace, guard and learn. What it adds is what real use needs, from a WireGuard route and limits on files to more systems and packages that install in one step. Then three coding agents that developers use every day work under it for four weeks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
