Install

Download Vibe Vault for Mac, Linux, and Windows.

Native Mac app via DMG or Homebrew. CLI, MCP, and desktop shells on Linux and native Windows. Secrets stay local; no cloud account.

Preview Mac distribution: this build is ad-hoc signed and is not Apple-notarized yet. macOS may require Control-clicking the installer and choosing Open. The app and vault remain local-first.

Native app

Install the latest desktop experience.

The DMG includes the Vibe Vault app plus its CLI, MCP server, and Chrome native messaging host. It currently supports Apple Silicon Macs running macOS Sonoma or later.

01
Download the DMG

Get the current build directly from Vibe Vault.

02
Install Vibe Vault

Open the DMG and run Install Vibe Vault to place the app in Applications.

03
Approve the preview build

If Gatekeeper blocks the first launch, Control-click Vibe Vault in Applications, choose Open, then confirm.

CLI-only option

Install the command-line tools with Homebrew.

This is the recommended path when you only need the CLI, MCP server, scanner, git guard, or native host used by the Chrome importer.

01
Install
brew tap finsavvyai/tap
brew install vibevault
02
Run the scanner first
vibevault scan
vibevault scan --git-only
vibevault guard install
03
Prepare Cursor or MCP clients
vibevault cursor prepare
vibevault mcp install --client all
vibevault browser install --browser chrome --extension-id nfeigikipagiccmhlolgfbeienkckbpc
Homebrew installs the stable command-line release. The DMG above contains the latest desktop build.

Linux

Build or install CLI, MCP, and Gtk desktop.

Linux uses the same VaultCore as macOS. The master key uses libsecret when a session keyring is present, otherwise a mode-0600 file. Unlock with a session lease instead of Touch ID. Desktop builds need Swift 6+ and Gtk 4. CI publishes tarball, deb, and AppImage artifacts on every main push.

01
CLI and MCP (Docker)
bash scripts/build-linux.sh
bash scripts/package-linux-cli.sh
KIND=cli bash scripts/package-linux-deb.sh
# build/vibevault-linux-<arch>.tar.gz
# build/vibevault_<version>_<arch>.deb
tar -xzf build/vibevault-linux-*.tar.gz
cd vibevault-linux-* && ./install.sh
02
Desktop shell (Gtk 4)
bash scripts/build-desktop-linux.sh
bash scripts/package-linux-desktop.sh
KIND=desktop bash scripts/package-linux-deb.sh
DOWNLOAD_APPIMAGETOOL=1 bash scripts/package-linux-appimage.sh
# build/VibeVaultDesktop-linux-<arch>.tar.gz
03
Unlock before reads
vibevault session unlock --minutes 30
vibevault license status

Windows

Native CLI, MCP, MSI, and WinUI desktop.

Install Swift for Windows, then build CLI and MCP with DPAPI-protected master keys. CI publishes a zip and MSI. The WinUI desktop shell is optional. WSL2 remains a Linux-toolchain fallback.

01
Install Swift for Windows

Use the current toolchain from swift.org/install/windows.

02
Build CLI, MCP, and MSI
git clone https://github.com/lunaos-ai/luna-vault
cd luna-vault
powershell -File scripts/build-windows.ps1
powershell -File scripts/package-windows-cli.ps1
powershell -File scripts/package-windows-msi.ps1
03
Unlock and scan
vibevault session unlock --minutes 30
vibevault scan
vibevault mcp install --client all
Vault data lives in %APPDATA%\vibe-vault. Desktop: powershell -File scripts/build-windows.ps1 -Desktop. WSL2 fallback: bash scripts/build-wsl.sh.

Source

Build from source if you want to inspect locally.

The MIT-licensed CLI, VaultCore package, MCP server, and browser host are public. Use this path for code review or local development.

git clone https://github.com/lunaos-ai/luna-vault
cd luna-vault
swift build -c release --product vibevault
swift build -c release --product vibevault-mcp
swift build -c release --product vibevault-browser-host

Distribution status

Developer ID notarization is still pending.

Apple requires Apple Developer Program membership to request Apple-issued signing certificates. Developer ID distribution also requires a Developer ID certificate and notarization before Gatekeeper-safe public distribution.

Available now

The latest native DMG is available as a clearly labeled preview build.

Gatekeeper

The first launch may require the documented Control-click and Open flow.

Next milestone

Developer ID signing, Apple notarization, stapling, and automated update verification.