Experimental CLI

Local FUSE Mount

Expose one local commit through a read-only FUSE mount in a source build that enables the optional fuser feature.

Experimental, local, and feature-gated

Published npm binaries do not promise this command surface. The mount reads objects already present in the local repository; it does not contact a remote, partially clone a repository, or hydrate missing data over a network. Startup and read latency depend on the repository, machine, FUSE implementation, and access pattern.

Build requirements

Build from source with the fuser feature and install the FUSE implementation required by your operating system. Exact OS setup is outside the Dits compatibility promise.

cargo build --locked --release -p dits --features fuser
./target/release/dits mount --help

`dits mount`

Resolves HEAD or the local ref selected by --commit, loads its manifest, and blocks while serving a read-only mount. The --cache-mb value configures the in-process RAM cache; the disk cache lives below .dits/cache.

dits mount <MOUNT_POINT>
dits mount <MOUNT_POINT> --commit main --cache-mb 256

Read-only is not an access-control boundary

The FUSE mount is configured read-only, but visibility to other local users depends on operating-system permissions and FUSE configuration. Protect the repository and mount point with normal OS controls. Verify important reads against the original fixture before relying on this experimental path.

Unmount and inspect the disk cache

dits unmount <MOUNT_POINT>
dits cache-stats

cache-stats counts local files and bytes in .dits/cache. It does not report a remote cache, bandwidth, hit-rate guarantee, or live RAM statistics after the mount exits.

Not implemented

Network partial clone or remote chunk hydration.
Windows native virtual-drive support in the published package.
Guaranteed instant mount, open, seek, or playback behavior.
A supported editor-integration or production VFS contract.

See the VFS experiment boundary, installation status, and status and roadmap.