rclone
"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
Runssource: GitHubhomepageGoMITcommit 7ebef790b49a
Go, MIT licensed. The project labels itself: azure blob, azure blob storage, azure files, backblaze b2, cloud storage, dropbox, encryption and ftp.
rclone runs. An Argusic agent installed it in 8 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Rclone v1.76.0-DEV builds and runs from source with Go 1.26.0; local file copy/check operations work; 1831 unit tests pass, 130 skip, 5 fail due to missing FUSE/Docker/rsync/infrastructure in container
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Missing go binary3 minutes
- FUSE not available - fusermount3 not found
- Docker daemon not available
- rsync not available
- NFS test symlink support missing in container fs
- Install time
- 8 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- go test ./... with RCLONE_CONFIG=/notfound: 1831 passed, 130 skipped, 5 infra-related failures; rclone copy/check on local files confirmed 1 file matched with 0 differences; rclone version returned v1.76.0-DEV
- Model tokens used
- 72,849
- Exact commit tested
- 7ebef790b49a
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
All 5 failures are container environment limitations, not code defects. tokens used 72,849 Now let me compile the final report. Here's a summary of everything I did and observed: **Install**: Downloaded Go 1.26.0 from go.dev, extracted to `/home/runner/go/go/bin/go`, built rclo… **Binary verification**: `/tmp/rclone version` returned the binary and version info correctly. Func… **Test suite**: 1831 passed, 130 skipped, 5 infrastructure-related failures: - `cmd/mount` and `cmd/mount2` — no FUSE (`fusermount3` not found) - `cmd/serve/docker` — no Docker daemon - `cmd/serve/nfs` — no symlink support in this container's tmpfs - `fs/logger` — `rsync` not installed All 5 failures are container environment limitations, not code defects.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 8 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
azure-blobazure-blob-storageazure-filesbackblaze-b2cloud-storagedropboxencryptionftpfuse-filesystemgogolanggoogle-cloud-storagegoogle-driveonedriveopenstack-swiftrclones3sftpsyncwebdav
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/rclone)Questions
- Does rclone run?
- Yes. rclone runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test rclone?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7ebef790b49a. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test rclone?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does rclone take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does rclone need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing rclone?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for rclone?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.