Offline use and local data
What can run locally
Section titled “What can run locally”With a supported model and backend already available, the native core can inspect local GGUF files, plan placement, load a model and stream chat through its private loopback runtime. The current chat path is not a cloud-model fallback. A failed local load does not silently send your prompt to a hosted provider.
The app’s renderer has connect-src 'none'; network and file operations are brokered by the native host. This restriction does not mean every host operation is network-free. Explicit backend installation can download components, and opening an allowed external link launches your browser.
Prepare before disconnecting
Section titled “Prepare before disconnecting”- Obtain the exact model artifact and any required complete file set.
- Install the selected backend while connectivity is available.
- Test a complete load, generation, Stop, recovery and unload cycle.
- Record the qualified model, engine and settings.
- Disconnect and repeat the workload you actually need.
The engineering installer bundles the pinned native runtime. Availability of a CPU or CUDA backend still depends on the delivered artifact and the state reported by System. Do not assume a merely discovered model has already been loaded or qualified offline.
Where information lives
Section titled “Where information lives”Normal Windows data is stored under %APPDATA%\RegesARC. Settings and conversations are local JSON; runtime data has a separate subdirectory. Existing model files remain in their selected locations. The app does not encrypt conversation JSON or automatically remove operating-system backups.
Diagnostics include hardware, model metadata, paths and runtime log excerpts. Review an export before sharing it. Redaction reduces accidental token exposure but is not a guarantee that every potentially sensitive string in an upstream log has been removed.
Boundaries for future features
Section titled “Boundaries for future features”Remote MCP servers, browser tools, model downloads and remote-device linking necessarily introduce network decisions. An eventual offline mode must make those boundaries visible and reject unavailable operations rather than claim they remain local. Credential storage, network scopes and tool permissions are separate release gates.
This documentation site uses local static assets and a local Pagefind search index after delivery. It has no embedded hosted chat or analytics dependency. External links still leave the site, and the first visit or uncached navigation requires the documentation files to be available.