autoclip

AutoClip|一个链接,一键出片。开源 AI 视频剪辑桌面工具,将播客、访谈、课程等长视频自动剪成短视频,生成字幕、封面和发布文案,适配抖音、小红书、TikTok、Reels 与 YouTube Shorts。Open-source AI video clipping & content repurposing.

Runssource: GitHubhomepagePythonMITcommit 17100c05252b

Python, MIT licensed. The project labels itself: ai agent, ai video editor, content repurposing, desktop app, douyin, instagram reels, mcp and open source.

autoclip 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.

103 backend tests pass, FastAPI server starts and responds 200 on /health and /api/v1/video-categories, and the frontend Vite build completes successfully.

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

At a glance

verdict
Runs
Argusic Score
90.7 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
3
last tested
stars
10,090
forks
1,795
open issues
33
watchers
37
size
107 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.

Install time
2 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
pytest backend/tests/ returned '103 passed, 18 warnings in 3.04s'; curl http://localhost:8000/health returned HTTP 200 with body {"status":"ok","mode":"web","version":"1.0.0"}; curl http://localhost:8000/api/v1/video-categories returned HTTP 200 with valid category JSON; npm run build succeeded producing dist/
Model tokens used
35,226
Exact commit tested
17100c05252b
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.

print(repr(get_api_key()))
" 2>&1' in /work/repo
 succeeded in 53ms:
'your_dashscope_api_key_here'
exec
/bin/sh -lc 'cd /work/repo && echo "=== BACKEND TEST COUNTS ===" && . venv/bin/activate && python -…
 succeeded in 751ms:
103 tests collected in 0.46s
All systems work out of the box. Here's the final report:
tokens used
35,226
All systems work out of the box. Here's 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 2 minutes, faster than the median of the 231 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.
  • Measured 3 times, so the result is not a one-off.

Of the 232 ai projects Argusic has installed and timed, autoclip was the 41st fastest to reach a running state, and 153 of 232 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner3/3Runs80.000.03
Argusic Runner2/3Runs100.000.04
Argusic Runner1/3Runs with mocks92.000.05

Topics (from GitHub)

ai-agentai-video-editorcontent-repurposingdesktop-appdouyininstagram-reelsmcpopen-sourcepodcastsubtitlestiktokvideo-clippingvideo-editing-softwarexiaohongshuyoutube-shorts

Embed the badge

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

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

Questions

Does autoclip run?
Yes. autoclip 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 autoclip?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 17100c05252b. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test autoclip?
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 autoclip 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 autoclip need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing autoclip?
Nothing did, in the recorded run: zero errors between clone and running.
How does autoclip compare with the alternatives?
Of the 232 ai projects Argusic has installed and timed, autoclip was the 41st fastest to reach a running state, and 153 of 232 reached one at all.
Where is the evidence for autoclip?
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.

Discussion