Manifa

macOS

Installing

curl -fsSL https://manifa.dev/install | sh

The installer detects your chip and pulls the right release: aarch64-apple-darwin (Apple silicon) or x86_64-apple-darwin (Intel). No Xcode or Rust toolchain needed for the CLI itself.

The CLI

Every command works exactly as documented in the CLI reference — login, init, vault create, sync, watch, daemon start, env, device, recovery all behave identically to Linux. Your device's local keypair (generated on mani device enroll / first mani init) is stored in the macOS Keychain; its private half never touches disk in plaintext and never leaves the device. See vaults and devices for what that keypair is for.

mani mount itself — the FUSE-based on-demand-files command — is Linux-only and exits with an error on macOS. The macOS equivalent is the Finder extension below, which is a separate integration built on Apple's File Provider framework rather than FUSE.

Finder integration (in development)

Manifa has a working File Provider extension that presents a vault in Finder the same way iCloud Drive or Dropbox do: the whole tree appears immediately and takes almost no disk space, and a file's bytes stream in the moment you open it. It shares its core with mani mount — the same Rust placeholder model and chunk-decryption logic — wired to Finder through Swift instead of to the Linux kernel through FUSE:

Finder ──► fileproviderd ──► FileProviderExtension (Swift)
                                   │  enumerate / stat / fetch / decrypt
                                   ▼
                             Rust core (C-FFI): placeholders + crypto
                                   ▲  ciphertext (presigned GET)
                                   │
                             Tigris CAS + Convex control plane

This isn't shipped as an installable app yet. There's no packaged, signed binary you can download — running it today means building it yourself:

  1. Build the Rust core as a universal static library (aarch64 + x86_64).
  2. Create an Xcode project (a container app + a File Provider Extension target) and wire the Swift sources into it.
  3. Sign it with your own Apple Developer identity and add an App Group entitlement shared between the container and the extension.
  4. Provision a vault's keys and manifest into that App Group's container directory, then register a NSFileProviderDomain so it shows up in Finder's sidebar.

None of that can be scripted headlessly — it needs a real signing identity and Xcode. If you want to try it, the full step-by-step (exact build commands, entitlements, and the App Group file layout) is in the macos/ directory of the source repository. There's no mani mount --finder CLI shortcut yet; writing the provisioning files by hand is currently the only path in.

Uninstalling

rm $(which mani)

This only removes the binary — your account, vaults, and recovery code are unaffected (they live server-side and on your other devices). To also forget this device, run mani device revoke <this-device> from another enrolled device first.