mani mount

The whole tree is visible immediately; file contents stream in lazily on first touch. Two backends, one idea: --finder hands the vault to Finder through Manifa Vault.app on macOS, while mounting at a path uses FUSE and is Linux-only — and the released binary doesn't include it, see the Linux platform page for the --features fuse build step.

Usage

mani mount [OPTIONS] <VAULT> [PATH]

Arguments

<VAULT> — The vault name or id to mount
[PATH] — Where to mount it (an existing empty directory). Refused with --finder, which hands the vault to Finder rather than to a path

Options

mani mount --finder

macOS: make the vault available in Finder through the File Provider extension instead of mounting it at a path. Writes only the vault's non-secret coordinates — the Vault Key is served to the extension by the running daemon over an app-group socket, never written to disk (#105 / #304)

mani mount --timing

Print a per-phase timing breakdown to stderr (same as MANIFA_TIMING=1). Useful for diagnosing a slow sync / clone

mani mount --json

Emit a machine-readable result envelope instead of human text (works on every command). Success prints {"ok":true,"value":…}; failure prints {"ok":false,"error":{"code":…,"message":…}} with a differentiated exit code. Stable field names for scripting/agents

mani mount --quiet

Suppress progress and chatter — print only results and errors (alias: -q)

mani mount --no-color

Never colorize output (also honored: the NO_COLOR env var). Color is off automatically when output isn't an interactive terminal

mani mount --help

Print help (alias: -h)