Back to news
VAF 0.1.0a19: a built-in client replaces the mail dashboard
In 0.1.0a19, devices on the network have to sign in: with network access on, any of them used to reach pages and APIs without a token.
0.1.0a19 is out. The built-in mail client is now the only one. Mail lives in a local per-user store and opens offline; sending runs over SMTP, not the providers' REST APIs. A sent message is held for 15 seconds and can be withdrawn.
pip install -U --pre vafThree bugs are fixed:
- Devices on the network have to sign in. With network access on, the built-in HTTPS proxy passed every device on as the computer itself: pages and APIs stood open without a token, user management, logs and the security dashboard included.
- VAF's own settings folder is closed to the file tools, the machine's owner included. It holds every connected API key, the sign-in secret and every conversation, and asking the agent for a file got in there. Skills and workflows you create stay readable.
- A switch to a cloud provider frees roughly 3.4 GB. The local model used to stay on the graphics card even when the next run went to the cloud. A call, a running task or a sub-agent still keeps the model.
The mail endpoints under /api/email are gone: message list, search, body, categories, category change, sender-rule backfill and per-account sync. Mail comes from /api/mail. Sign-in and account management under /api/email are unchanged.