This reference explains how to run the Vibgrate CLI behind a proxy or fully offline. It is for developers in locked-down corporate networks, air-gapped environments, or CI runners with restricted egress.
Proxied networks
The CLI honors your shell's standard outbound HTTPS proxy configuration. If your environment already routes HTTPS through a proxy, a normal scan works without extra flags:
vg
If only some commands need network access (such as vg push to Vibgrate Cloud), the local scan itself does not depend on the proxy at all — scans run locally.
Offline mode
When you want to guarantee no network calls, run in offline mode:
vg scan --offline
Offline mode uses only local artifacts and caches. This is the right setting for air-gapped machines and for verifying that a scan does not reach the network.
Code-map queries are offline after first use
Vibgrate Graph is designed to work offline. Build the code map once, then query it without the network:
vg build
vg ask
The semantic index uses a local model downloaded once into a shared cache; after that, vg ask and vg serve are fully offline. You can precompute the index ahead of time:
vg embed
Bypassing the cache
If you suspect a stale cache is affecting results, recompute without it:
vg scan --no-cache
Uploads in restricted networks
Uploading to Vibgrate Cloud does require network access. In CI, authenticate with a DSN token from vg dsn create rather than the interactive vg login flow, and allow egress only to the dashboard host.
Related
- Environment variables reference
- The
vg serveandvg libcapabilities (Vibgrate AI Context, Free Dev Docs Library) - Vibgrate Cloud upload guide