VAF 0.1.0a33: sandbox environments for building and testing

0.1.0a33 is out. The agent can create a container of its own for a task, run commands and edit files in it, and copy the results to your folders. The network each environment gets is a choice, and an administrator can cap it. Given a project environment, the coding sub-agent builds, tests and runs its dev server inside it.

vaf update

Two security holes are closed:

• In server mode, VAF no longer answers API calls from outside the local network. The login screen still loads, but nothing behind it answers. The local-network check used to hold for the chat only. With the access port reachable from the internet, say through a forwarded router port or on a rented server, a stranger could call the API. On a machine without an admin account yet, that stranger could create one.
• Each person has their own container for the Python sandbox and the coding sub-agent's test runs, without root. Exports come only from the run's own folder, and a run gets the key that lets sandbox code call VAF tools through its environment variables. All accounts used to share one container running as root. One account's code could read another's working folder and copy files out of it, and the key sat in a command line any other run could read.

Full release notes for 0.1.0a33 on GitHub ↗