VGA — LOCAL RUNTIME

This download contains the application code, bundled SDKs and one copy of the interface assets in dist/. It contains no keys, wallets, credentials, balances, local catalogs or execution history.

START ON WINDOWS
1. Install Node.js 22 or newer and ensure node is on PATH.
2. Extract the entire ZIP into your own folder. Keep connector-server.cjs and dist/ together.
3. Run Start-VGA.ps1 in PowerShell.
4. Open http://127.0.0.1:4391/ in your browser.
5. Run Check-VGA.ps1 in a second PowerShell window to inspect local readiness. The optional -CheckConnections switch performs read-only service checks.

START ON OTHER SYSTEMS
From the extracted folder, run node connector-server.cjs, then open the same local URL. For readiness, run node check-vga.cjs. Optional read-only connection checks: node check-vga.cjs --check-connections.

YOUR LOCAL DATA
The server listens on 127.0.0.1. Create your own vault and agent wallets after starting. Newly created catalogs and the encrypted vault are stored in data/ next to the runtime; this folder is intentionally absent from the ZIP. Download the encrypted backup before funding a wallet. Keep the vault password separately: there is no password recovery. Do not upload your data/ directory, backups, API keys or wallet-service credentials to a public site.

The public website is a preview and entry point. Wallet creation, keys, signatures, credentials and runtime records stay in your local runtime. Open the local app for operations. Each money-moving action requires its exact local approval; startup and wallet creation do not send funds.

API credentials entered in the app remain in server memory and clear on restart. Any environment variables that you choose to configure are supplied separately by you; no secrets file is distributed. Stop the server with Ctrl+C.

See CONNECT-AGENTS.txt for wallet permissions, bridges, testnet missions, marketplace and finite schedules. See NATIVE-AGENTS-SETUP.txt for NEAR mainnet, Starknet and local Zallet setup. Zcash receiving/inspection is available after local setup; autonomous outbound native ZEC spending is disabled.

The runtime includes its required SDKs. No node_modules directory or package installation is required to start it. dist/ holds the local interface; root assets are omitted to avoid duplicate copies.
