FUSE on macOS · CLIO Core

1. Install macFUSE

shell

$ brew install --cask macfuse

macFUSE 5 ships the libfuse3 API the adapter builds against. Choose a backend:

Backend	Requires	Setup
FSKit	macFUSE 5.1+ on macOS 15.4+	No kernel extension. The mountpoint must be under `/Volumes`.
Kernel extension	Any supported macOS	Approve the extension once in System Settings, then reboot.

For the kernel extension: open System Settings → Privacy & Security, allow the macFUSE system software, and restart. On Apple Silicon you may first need to allow user-managed kernel extensions from Recovery mode.

2. Build the adapter

shell

$ git clone --recurse-submodules https://github.com/iowarp/clio-core.git
$ cd clio-core
$ ./CI/ci-deps.sh --only-deps release
$ conda activate iowarp
$ cmake --preset release-mac-fuse -DCLIO_CORE_ENABLE_CONDA=ON
$ cmake --build build-mac-fuse -j"$(sysctl -n hw.ncpu)"
$ sudo cmake --install build-mac-fuse

Check that the configure output mentions the FUSE adapter. If macFUSE was not found, the build skips the adapter instead of failing.

3. Mount

FSKit

shell

$ clio_run start &
$ CLIO_WITH_RUNTIME=0 clio_cte_fuse /Volumes/clio-mnt -f -o backend=fskit

Kernel extension

shell

$ clio_run start &
$ mkdir -p ~/clio-mnt
$ CLIO_WITH_RUNTIME=0 clio_cte_fuse ~/clio-mnt -f

The mount appears in Finder like an external volume. Copy files into it, or open them from any application.

4. Unmount

shell

$ umount ~/clio-mnt                     # or /Volumes/clio-mnt
$ diskutil unmount force ~/clio-mnt     # if a process still holds it open

Known limitations

The first mount after installing macFUSE can hang until the extension is approved. Approve it, reboot, and try again.
macOS wheels are for Apple Silicon. The clio_cte_fuse command they install prints Error: clio_cte_fuse binary not found; use the build above.
The macOS mount runs in CI as a probe, not a required check. Linux and Windows get more automated testing.