Install and update

Use the web app for browser access and GitHub Releases for Android and Desktop downloads.

Web app

1. 1
   Open the app.

   Go to gitvault.giofahreza.com/app/.

2. 2
   Unlock or onboard.

   Existing browsers unlock locally. New browsers must create, link, or restore a vault.

3. 3
   Check Settings.

   The web version should match the latest deployed release tag after GitHub Pages updates.

Android APK

1. 1
   Open GitHub Releases.

   Use the latest release.

2. 2
   Download the universal APK.

   gitvault-vX.Y.Z-universal.apk works on most devices.

3. 3
   Allow APK installation.

   Enable install from unknown sources for the browser or file manager you use.

4. 4
   Open GitVault.

   Existing installs should keep local data. New installs must link or restore.

Desktop archives

1. 1
   Choose the archive for your OS.

   Download the Windows x64 ZIP, Linux x64 tarball, or macOS ZIP from the same release page.

2. 2
   Verify its checksum.

   Use the matching platform checksum file before running the application.

3. 3
   Extract the complete archive.

   Keep GitVault, its libraries, assets, and the bundled gitvault_mcp bridge together.

4. 4
   Open GitVault.

   Linux requires GTK 3, AppIndicator, and Secret Service libraries. Unsigned macOS builds can require explicit approval in Privacy & Security.

Release assets

• Universal APK Easiest Android download and recommended for most users.
• ABI APKs Smaller downloads for specific device CPU architectures.
• Windows x64 ZIP Complete Windows runner and bundled stdio bridge.
• Linux x64 tarball Complete relocatable Flutter bundle and stdio bridge.
• macOS ZIP Application bundle and stdio bridge; the release is not notarized.
• SHA256SUMS files Separate checksum lists for Android, Windows, Linux, and macOS downloads.

Verify the version

Open Settings, then About. The app version should match the release tag after the web or APK build has been deployed.

Upgrade habits

• Sync first Run sync before upgrading a device with important unsynced edits.
• Keep recovery available Confirm the recovery phrase is available before replacing phones or browsers.
• Wait for Pages Web deployment can lag a release while GitHub Pages finishes deploying.