VAF 0.1.0a17: VAF is on PyPI
In 0.1.0a17, pip install --pre vaf installs the framework as a library; desktop and server still come from the installers.
0.1.0a17 is out. VAF ships to PyPI with every release and installs with pip install --pre vaf. On the base dependencies, vaf --version and vaf prompt run normally. A command that needs an optional component, for example vaf run --web, names the extra it needs, such as vaf[server], instead of crashing on an import error. For the desktop and server installers nothing changes.
pip install -U --pre vafvaf update only takes effect inside a VAF source tree. In a pip install the command names pip install -U --pre vaf instead. Before, it offered to turn the folder into a git repository, and that could leave the Python environment broken.
Two bugs are fixed:
- Some tool calls from the local model used to sit in the chat as plain text and never ran. The app understood the way they were written for one model family only. With every other local model, a calendar event, for example, was never created, and no error message came up. That wording is now understood for every local model.
- A workflow that ran to the end is now reported that way. Runs in their own process lost their outcome before it reached the browser. The steps were all ticked green, the document existed, the chat reported success, and the panel still read FAILED.