CLI And Packaging

Avikal has both GUI and CLI distribution paths. The desktop app is the main visual workflow, while the CLI path is intended for advanced users, automation, and terminal-based usage.

Both paths are described as using the same shared Avikal core model where compatible packaging allows it.

GUI Installer

The GUI installer bundles the Electron app and the required backend runtime.

This gives everyday users a desktop interface for Encode, Decode, Rekey, Time-Capsule, Settings, preview sessions, diagnostics, and update checks.

Standalone CLI Installer

Avikal includes a standalone CLI installer path for Windows packaging. The CLI is intended to use the same shared core engine as the GUI.

The landing and download pages also describe CLI availability for macOS, Linux, and automation through the Python CLI path.

Shared Core Reuse

GUI and CLI installers can reuse a compatible installed shared core. This reduces duplicate installation size when both interfaces are installed.

Shared core reuse depends on compatibility. If the installed core is not compatible, the installer path should provide the required runtime for that interface.

Full Bundled Release Model

Production Windows releases are built as self-contained local installers, not small network installers.

This is meant to keep the installed desktop app and backend runtime available locally after installation.

Manual Updates

The Updates tab checks GitHub releases for a newer Avikal version. It does not silently install updates.

Instead, it shows release information and opens the release or download page so the user can review and install manually.

Runtime Visibility

Settings shows whether critical local components are available, including native Rust crypto availability, OpenSSL PQC provider availability, Avikal version, preview root, and log directory.

Users should review runtime status when diagnosing install or environment problems.