VAF 0.1.0a24 and 0.1.0a25: hands-on control of the browser
A fresh install of 0.1.0a24 never gets past the splash screen; 0.1.0a25 builds the interface and frees the next update too.
0.1.0a24 and 0.1.0a25 are out. The browser VAF runs for the agent can now be driven by hand as well. The globe in the chat opens the Chromium window with its own tabs and address bar, live rather than a screenshot every 1.5 seconds. A login made there by hand is one the agent reads from the same browser store on its next run.
pip install -U --pre vafOne feature is new:
- A usage view names the tokens spent, the request count and one estimated cost, with a table of accounts beside them; vaf usage prints the same figures in a terminal. The token counts come from what the providers reported for calls they billed; the cost comes from a price list that ages. Costs and other accounts stay with the administrator.
One bug is fixed:
- Search in the long-term memory throws fewer of its own candidates away. The vector lane passed five into the merge and the keyword lane twenty; both now feed the same depth, and the keyword cap is 2,000 sections instead of 400. On the project's fixed question set the right memory came first in 18 of 26 cases instead of 12.
A fresh install of 0.1.0a24 does not build its interface; the window stops at the splash screen. An update also blocked every later one. 0.1.0a25 repairs both; anyone stuck updates again.
VAF has been on PyPI since 0.1.0a17; since 0.1.0a25 an installation set up from there builds its interface too.