All docs ▾
Getting started
Using Vex
FAQ
The questions that decide trust, answered with links.
The seven questions from the landing page, plus a few that come up once people are actually running Vex. Every answer ends somewhere you can check it.
Can Vex move funds without me?
Not by default. In restricted mode every fund-moving action creates an approval you must click, fail-closed: an error means no trade, not a silent one. Full mode skips the generic gate for a session you configure; the Safety Contract still applies, and you choose per session.
Where do my keys live?
On your machine. Wallets are generated locally and sealed in AES-256-GCM keystores under a scrypt-derived master key. No custodian, no server-side signing, no cloud backup. Deleting the config directory deletes your keys, so export backups first.
Does it depend on the cloud?
Inference runs through your own OpenRouter key, on your own account. Your wallet, approvals and signing stay inside the app on your machine; memory, embeddings and the database run in local Docker containers whose ports bind to 127.0.0.1, never the LAN. Crash reporting is strictly opt-in and off by default.
Is it open source?
Source-available: free to read, audit and run for personal self-custody. Redistribution, forks and commercial use aren't licensed, so no, not OSI open source, and we won't call it that. The code is public because trust should be checkable.
What does it cost?
The app is free to use. You pay your own inference (OpenRouter) and gas. Vex takes a 25 bps fee on successful swaps, bridges and launches, charged only when the action succeeds and never on one that reverts or fails. Quotes, reads and research are free.
What do I need to run it?
macOS 13+, Windows 10/11 x64, or Ubuntu 22.04/24.04; Docker with Compose 2.23.1 or newer (Windows needs the WSL2 backend); an OpenRouter API key; and a one-time ~333 MB model download on first run.
Where do I buy $VEX, and what is it for?
Through Virtuals Protocol on Robinhood Chain. The Buy link on this page goes to the official listing. The 25 bps fee funds $VEX buyback and burn; the app never requires the token. Verify the contract address against the one posted by @ProjectVEXai before you trade.
What happens if I ignore an approval from Studio?
It expires. When an external coding agent calls a mutating tool through Vex Studio, the approval appears in the Vex app and waits up to 1 hour; the installer writes a longer tool-call timeout into each client’s own config so the call survives that window rather than dying first. Ignore it and the intent is settled as rejected when it expires: no funds move, and the calling agent gets a refusal rather than a silent success. The same thing happens if you lock Vex, quit it, or edit the project’s scope while an approval is pending. Fail-closed is the default everywhere in Vex.
Can I use my own RPC endpoints?
Yes. config.json in your config directory takes localChainRpcUrls and pendleRpcUrls overrides, keyed by chain id, so those protocol clients talk to your nodes instead of the bundled defaults. The same file holds chain configuration and the service base URLs, and an entry that is empty or malformed is dropped rather than trusted.
How do I move Vex to a new machine?
Export your keystores and copy the backups/ directory before you touch anything on the old machine. Those files, plus your master password, are the only way back to your wallets. The export is wallet-only by design: it carries the encrypted keystores and a sanitised manifest of addresses and labels, and it deliberately does not copy config.json. Install Vex on the new machine, run through the first-run wizard, and import the exported keys rather than generating fresh ones. The exported keystores stay encrypted, so the master password has to travel with you, in your head or your password manager.
Your conversations, memory and embeddings live in the local Postgres and do not travel with the keys; a new machine starts with an empty memory unless you export knowledge first.
What if I lose my master password?
Then the vault and the keystores are gone, including the backups, and nobody, us included, can recover them. The password is derived into a key with scrypt and held only in memory; it is never written to disk, and there is no server holding a copy to reset it against. This is stated plainly in the security model as explicitly out of scope, rather than hidden behind a support promise we could not keep.
One more, because it is the question that costs people money: nobody from Vex will DM you first, and nobody will ever ask for your seed phrase or master password. Anyone who does is not us.