screencapturekit-rs
Safe, idiomatic Rust bindings for Apple ScreenCaptureKit, high-performance screen, window, and audio capture on macOS.
Could not verifysource: GitHubhomepageRustApache-2.0commit a46de0a44d67
Rust, Apache-2.0 licensed. The project labels itself: apple, ffi, macos, macos app, rust, screen capture, screen recording and screencapture.
Argusic could not get screencapturekit-rs running. An Argusic agent installed it in 25 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Rust toolchain (rustc/cargo 1.99.1) is installed, but the project does not build or test in this Linux container because the Swift/Xcode macОS toolchain and a non-macOS stub path do not exist here
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 10 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.
- cargo build fails: apple-metal v0.10.4 build script panics 'Failed to build Swift bridge: No such file or directory' because no Swift/Xcode toolchain exists in this Linux container12 minutes
- DOCS_RS=1 (the build.rs escape hatch) still fails on Linux: rustc E0455 'link kind framework is only supported on Apple targets' in apple-cf v0.11.7 (6 sites: cg/affine.rs:108, cg/display.rs:7, cg/display.rs:24, cg/mod.rs:21, cv/buffer.rs:25, cv/metal_texture_cache.rs:18)8 minutes
- cargo test (clean checkout) fails in apple-metal-0.10.4/build.rs:49:39 'Failed to build Swift bridge: No such file or directory'5 minutes
- Install time
- 25 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cargo build, DOCS_RS=1 cargo build, DOCS_RS=1 cargo doc --no-deps --features async, cargo test, and cargo test in a clean /tmp copy: every run returned non-zero with the errors above, so no test or binary was produced (not verified)
- Model tokens used
- 136,110
- Exact commit tested
- a46de0a44d67
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
4: DOCS_RS=1 cargo doc -> apple-cf E0455 (6 errors)
5: DOCS_RS=1 cargo build after apple-metal DOCS_RS pass -> apple-cf E0455
2026-10-28T10:30:28.204472Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce…
exec
/bin/sh -lc 'export PATH="$HOME/.cargo/bin:$PATH"; cd /work/repo && mkdir -p /tmp/cleanbuild && cp …
succeeded in 66091ms:
1 Failed to build Swift bridge: Os { code: 2, kind: NotFound, message: "No such file or dir…
1 thread 'main' (13799) panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf…
Clean checkout fails identically at the first dependency (`apple-metal` build script). I have all t…
tokens used
136,110
Clean checkout fails identically at the first dependency (`apple-metal` build script). I have all t…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
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
- Took 25 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 apple projects Argusic has installed and timed, screencapturekit-rs was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 20.00 | 0.04 | |
| Argusic Runner | 1/3 | Did not run | 0.00 | 0.04 |
Topics (from GitHub)
appleffimacosmacos-apprustscreen-capturescreen-recordingscreencapturescreencapturekitswiftvideo-capture
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/screencapturekit-rs)Questions
- Does screencapturekit-rs run?
- Argusic could not verify that screencapturekit-rs runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test screencapturekit-rs?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a46de0a44d67. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test screencapturekit-rs?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does screencapturekit-rs take to install?
- 25 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 screencapturekit-rs need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing screencapturekit-rs?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does screencapturekit-rs compare with the alternatives?
- Of the 4 apple projects Argusic has installed and timed, screencapturekit-rs was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for screencapturekit-rs?
- 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.