fcp

A significantly faster alternative to the classic Unix cp(1) command, copying large files and directories in a fraction of the time.

Runssource: GitHubRustBSD-3-Clausecommit f8db0603ff0f

Rust, BSD-3-Clause licensed. The project labels itself: cli, command line, command line tool, fast, rust and unix.

fcp runs. An Argusic agent installed it in 0.4 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Rust 1.100.0 installed via rustup, fcp 0.2.2 builds and passes all 18 integration tests (debug+release), the binary correctly copies files and directories, handles symlinks, fifos, sockets, permissions errors, duplicate source detection, and self-copy prevention

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
864
forks
25
open issues
16
watchers
4
size
1 MB
created
last push

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.

  • character_device test requires `expect` (Tcl expect utility) which is not installed
  • 2 tests (linux, large_files) are #[ignore] by default — large file fixtures would be expensive to hydrate
Install time
under a minute
Cold machine to finish
7 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
cargo test --test tests -- --skip character_device exited 0, 18 passed 0 failed; fcp --version printed 0.2.2; fcp copied /tmp/fcp_test_source to /tmp/fcp_test_dest and content matched; fcp correctly rejected self-copy with error message
Model tokens used
98,549
Exact commit tested
f8db0603ff0f
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

/bin/sh -lc 'cd /work/repo && . "$HOME/.cargo/env" && mkdir -p /tmp/fcp_testdir && cp /tmp/fcp_test…
 succeeded in 0ms:
hello world
exec
/bin/sh -lc 'cd /work/repo && . "$HOME/.cargo/env" && ./target/release/fcp /tmp/fcp_test_source /tm…
 succeeded in 0ms:
Cannot overwrite file '/tmp/fcp_test_source' with itself '/tmp/fcp_test_source'
exit: 1
Now let me produce the final report.
tokens used
98,549
Now let me produce the final report.

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 0.4 minutes, faster than the median of the 127 comparable projects Argusic has measured.
  • Recovered from all 2 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 BSD-3-Clause, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 128 cli projects Argusic has installed and timed, fcp was the 11th fastest to reach a running state, and 117 of 128 reached one at all.

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 0.4 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.02
Argusic Runner1/3Runs with mocks92.000.09

Topics (from GitHub)

clicommand-linecommand-line-toolfastrustunix

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/fcp.svg)](https://argusic.com/subject/fcp)

Questions

Does fcp run?
Yes. fcp runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test fcp?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f8db0603ff0f. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test fcp?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does fcp take to install?
0.4 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 fcp need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing fcp?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does fcp compare with the alternatives?
Of the 128 cli projects Argusic has installed and timed, fcp was the 11th fastest to reach a running state, and 117 of 128 reached one at all.
Where is the evidence for fcp?
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.

Discussion