capcut-cli
Independent, unofficial CLI to edit CapCut and JianYing (剪映) projects, subtitles, timing, speed, volume, templates, cut long-form to shorts. No API needed, reads draft_content.json and draft_info.json (剪映草稿) directly. Not affiliated with ByteDance.
Runssource: GitHubhomepageJavaScriptMITcommit ca5046924698
JavaScript, MIT licensed. The project labels itself: agent skills, ai agent, automation, capcut, capcut api, capcut automation, capcut editor and capcut subtitles.
capcut-cli runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
capcut-cli v0.25.0 builds from source, all 981 tests pass, CLI commands create and inspect valid CapCut draft projects with zero errors on linux
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.
- Install time
- 2 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npm test passed 981/981, capcut doctor returned ok, capcut quickstart created a valid draft with video from /tmp/test_clip.mp4, capcut info read it back with correct duration/tracks/resolution
- Model tokens used
- 119,739
- Exact commit tested
- ca5046924698
- 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.
**Errors encountered:** None. Everything worked on the first attempt. tokens used 119,739 Here's the summary: **Install & build:** `npm install` added 16 packages, `npm run build` compiled TypeScript successfu… **Test suite:** All 981 tests pass (307 suites, 0 fail, 0 skipped). **CLI verification:** - `capcut --version` → `0.25.0` - `capcut doctor` → `ok` on linux; ffprobe, ffmpeg available; whisper/TTS/ANTHROPIC_API_KEY noted a… - `capcut quickstart /tmp/capcut-test/my-draft --video /tmp/test_clip.mp4` → created a real editabl… - `capcut info /tmp/capcut-test/my-draft -H` → reads the draft correctly: 3.00s, 1920x1080, 1 track… **Errors encountered:** None. Everything worked on the first attempt.
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 2 minutes, faster than the median of the 115 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 116 agent-skills projects Argusic has installed and timed, capcut-cli was the 40th fastest to reach a running state, and 86 of 116 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 2 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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)
agent-skillsai-agentautomationcapcutcapcut-apicapcut-automationcapcut-editorcapcut-subtitlescapcut-templateclaude-code-pluginclidraft-content-jsonjianyingpythonsrt-exportsubtitle-editorvideo-editingvideo-productionvideo-to-shorts
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/capcut-cli)Questions
- Does capcut-cli run?
- Yes. capcut-cli runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test capcut-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ca5046924698. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test capcut-cli?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does capcut-cli take to install?
- 2 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 capcut-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing capcut-cli?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does capcut-cli compare with the alternatives?
- Of the 116 agent-skills projects Argusic has installed and timed, capcut-cli was the 40th fastest to reach a running state, and 86 of 116 reached one at all.
- Where is the evidence for capcut-cli?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.