The VM runs a Node server that handles the natural language parsing, calls the API and formats the results.
The persistent VM thing is also worth explaining because it's not obvious why it matters. Most serverless setups spin up on request and tear down after. That means no persistent state, cold start latency and you can't install arbitrary system dependencies. The VM sidesteps all of that — it's just a computer that stays on.
Real limitations I want to be upfront about: — The App Store is curated right now. You can customise after deploying but you can't push arbitrary code yet. — It's not open source.
One thing I didn't mention in the post: you can build your own apps on top of this infrastructure. The VM handles the runtime — you bring the logic. There's also multi-agent support if you're building something with multiple moving parts.
Genuinely curious whether the VM-per-app model feels like the right primitive to people here, or whether it's solving a problem most developers don't actually have.