Desktop app
Install it, sign in, and the agent is in its own window.
- Your data and keys stay on your machine
- Local models, or one API key for everything
- Schedules, memory and tools built in
The open-source AI agent with persistent memory and tools for web, code and files. Fully self-sufficient in-house, or with models from the cloud.
18,700+ downloads·Open source, AGPL-3.0·macOS, Windows & Linux
VAF runs on your machine, on your own server, or as a framework inside your code. Memory and keys live where the agent runs.
Install it, sign in, and the agent is in its own window.
VAF runs as a host on your own server, reached at your own address instead of through a hosted platform.
One import brings the whole agent, with memory, tools and sub-agents. Your own tools are plain Python files; MCP servers plug in on top.
You ask in plain language, and the main agent plans the work and delegates each part to the specialist sub-agents below.
The agent learns your tools, reads its way into your documents and keeps going while you do something else. On your own machine.
Whole documents go into long-term memory, contracts and reports of several hundred pages included. What the agent learned from them is there in every later conversation, not only the one the file arrived in.
At set times or continuously in the background, unattended. Once at noon on the 23rd, every day at 5 pm, or without stopping. The result is ready when the run ends.
The agent teaches itself new tools, custom ones included: it runs them, reads the results and adjusts until it can use them on its own. Every run makes it surer of them.
Local model, your own server, or one API key for every provider. You decide where the data lives and which model does the work. No per-seat subscription.
The agent breaks a job into steps and hands off whatever can run in parallel. An agent-to-agent protocol lets it work alongside further instances, and alongside agents from other providers such as Claude, Codex or OpenCode.
What it means to run an agent on your own machine, and why local-first matters for privacy, cost and control.
Read the explainer →The desktop app runs on this framework, and you build on the same primitives. Install it from PyPI and ship your own agents, tools and products on top.
Your machine. Your data.
Your agent.
VAF needs models for text, vision and speech. Normally that means an account with every provider, every key wired in by hand, a separate invoice per provider and no combined view. The Veyllo API bundles that into one key and one bill.
Two steps: clone the repository and run the installer. You pick the platform; VAF sets up the rest: container runtime, Python and Node.
Read the code, follow the commits, and raise issues that reach the developers directly.
VAF's daily spend limit stopped too late because the cached share went uncounted on Anthropic; 0.1.0a26 counts it.
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.
In 0.1.0a23 a foreign client joins with one standard-library file; the sha256 and CA fingerprint in the invitation are what verify it.
The desktop app installs everything it needs; the Veyllo API supplies the models.