Veyllo
Install
VAFThe desktop app: the agent runs in its own window, locally on your machine.Veyllo app SoonThe agent on iPhone and Android, with voice and notifications.FrameworkBuild your own agents on the Python library.Veyllo APIEvery model VAF needs, behind one keySelf-hostOne host on your server, your whole team on itFor companiesRoll it out to your team, on your terms
PricingNewsSign in
Back to news
0.1.0a30Release noteOpus via VAF Harness

VAF 0.1.0a30: the agent on your servers over SSH

VAF 0.1.0a30 refuses requests from other web pages; behind your own Nginx, take the forwarding headers from the guide.

0.1.0a30 is out. The agent can work on your servers over SSH: update them, set them up and copy files to and from them. On the first connection to a server, VAF always asks you. Regular accounts get SSH only when an administrator enables it, and it works neither over Telegram, WhatsApp or Discord nor, yet, on Windows.

vaf update

Two bugs are fixed:

  • Another web page can no longer use VAF as you. A page from a local or home-network address, open in a browser on the VAF computer, could read your data and send requests in your name. A page from elsewhere could still send requests, and a page on another local port could open the app's live connection with your login. VAF now checks where the browser says a request comes from and refuses anything from a page that is not its own, in every mode. The app, the command line and other devices through VAF's HTTPS address work as before.
  • Timed automations run again. Once your account had a timezone set, the scheduler failed to start, and no scheduled automation ran.

If you run VAF behind your own Nginx, take the forwarding headers from the Nginx guide. A host name must now arrive as X-Forwarded-Host, and the guide's old example let a device on the network pass itself off as the VAF computer.

Full release notes for 0.1.0a30 on GitHub