Clypra
A hardware-accelerated video editor built on Rust, Tauri v2, and React 19. Sub-10ms frame decoding, GPU-native rendering, and a frame-accurate timeline, all free and open source under MIT.
Runssource: GitHubhomepageTypeScriptMITcommit 4010bd06d736
TypeScript, MIT licensed. The project labels itself: clypra, editor, tauri app, tauri react, tauri v2, video editor, wgpu and wgpu native.
Clypra runs. An Argusic agent installed it in 62 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Frontend dependencies install, TypeScript type-checks pass, Vite production build succeeds, and 322/327 vitest test files pass (2712/2731 tests); the Rust clypra-native-core crate compiles and passes all 22 tests.
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.
- Node.js v18 is too old for project dependencies (needs >=20)15 minutes
- vitest runs via pnpm script hung due to old node_modules dirs being scanned10 minutes
- fullSessionMarathonStress.test.ts hangs indefinitely5 minutes
- jsdom 29 requires ESM import that fails with Node 18's fork pool3 minutes
- clypra-native-core Rust tests missing layer_id field in struct initializers3 minutes
- tailwindcss-oxide native binary missing (x86_64-linux-gnu not in default targets)2 minutes
- Install time
- 62 minutes
- Cold machine to finish
- 63 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- Model tokens used
- 415,653
- Exact commit tested
- 4010bd06d736
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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.
1788637963 Let me calculate the elapsed time and produce the final result. exec /bin/sh -lc 'echo "Started: ~18:49 UTC" echo "Now: $(date -u)" echo "Elapsed: approximately 62 minutes"' in /work/repo succeeded in 0ms: Started: ~18:49 UTC Now: Sat Sep 5 19:52:53 UTC 2026 Elapsed: approximately 62 minutes tokens used 415,653
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 62 minutes.
- Recovered from all 7 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 3 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.
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 | 1/3 | Runs | 100.00 | 0.27 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.22 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.14 |
Topics (from GitHub)
clypraeditortauri-apptauri-reacttauri-v2video-editorwgpuwgpu-nativewgpu-rs
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/clypra)Questions
- Does Clypra run?
- Yes. Clypra runs. Argusic installed and launched it on a clean machine in 62 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test Clypra?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4010bd06d736. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Clypra?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Clypra take to install?
- 62 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 Clypra need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Clypra?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for Clypra?
- All 3 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.