799953468/cloudreve-mac
Networking & CommunicationUnofficial macOS sync client that mirrors Cloudreve folders locally so files work in Finder and offline.
What it does
Cloudreve Mac is an unofficial macOS desktop client for Cloudreve sites. It pairs a folder on a Cloudreve site with a local folder so files appear in Finder and remain usable offline, without WebDAV or a mounted network drive. Supported behavior includes two-way sync of files and empty folders, multiple drives with separate local folders and ignore patterns, a menu bar transfer panel, and resumable transfers when the storage backend allows it README. The app is built in C# with Avalonia, and a separate Cloudreve.Sync local-directory tool lives alongside the desktop app desktop app.
Install and connect a drive
The client requires a Cloudreve site running 4.12.0 or later. Packaged builds are listed as Cloudreve-osx-arm64.zip (Apple Silicon) or Cloudreve-osx-x64.zip (Intel) on the Releases page; unzip and open Cloudreve.app — it bundles its own .NET runtime.
To build from source, install the .NET 11 SDK and Xcode Command Line Tools (xcode-select --install), then:
git clone https://github.com/799953468/cloudreve-mac.git
cd cloudreve-mac
rid=osx-arm64 # Use osx-x64 on an Intel Mac.
dotnet publish src/Cloudreve.Desktop -c Release -r "$rid" \
--self-contained true -p:MacBundle=true
open "artifacts/$rid/Cloudreve.app"
Then open Add Drive, enter the site root URL such as https://drive.example.com, and choose Connect. Sign in through the browser, authorize the remote folder, return to the app, name the drive, pick an empty local folder, and finish. The first sync starts immediately and can be followed from the menu bar icon; the app never asks for your site password connect guide.
Sync rules to know
- Editing the same file on both sides produces a conflict; both versions are kept and must be resolved manually.
- Remote deletions and replacements leave the old local copy in
.cloudreve-recovery/inside the paired folder; useCommand+Shift+.in Finder to see it. - Removing a drive from Settings stops sync but keeps local and remote files in place, and does not revoke authorization on the site.
- Deleting a synced file in Finder is not a way to free local space: the app also moves the unchanged remote copy to the site's trash sync behavior.
Requirements and known limits
- Finder shows full local copies, not on-demand placeholders, so the paired remote folder must fit on the Mac's disk.
- Whole-folder renames and moves are not supported; individual file renames are applied without re-uploading when the file is identifiable.
- The session files under
~/Library/Application Support/Cloudreve/store access and refresh tokens in plaintext, not in Keychain; other programs running as the same macOS user can read them, so do not sharedrives.jsonor thefolder-pairstransfer cache when reporting problems README. - Project builds are ad-hoc signed, not notarized by Apple.
- The repository has no project-wide license; third-party artwork, translations, and the Roboto font carry their own notices README.
Contributing and testing
Tests run from the repository root with dotnet test --solution CloudreveMac.slnx -c Release; they use temporary folders and simulated server responses rather than a live Cloudreve account test suite. CI runs the Release suite on test workflow and packages both Mac architectures on tags or manual runs via the release workflow.
HotRepo's take
This is a small, single-author project: the sole HotRepo snapshot is from 2026-11-21, when it was tracked on the new-project list with 107 stars and zero forks in its first recorded window, and it has no GitHub daily rank on record. The README is unusually detailed about conflict handling, recovery folders, and token storage, which gives readers real material for judging the client's behavior. What the record does not establish is adoption or release maturity — the install path mentions packaged builds only if they appear on Releases, so users should check that page before choosing between a downloaded bundle and a source build.
Written by AI from the project's public information and HotRepo's records, updated . The project's own docs are the source of truth.