vit
Git for video editing.
Runssource: GitHubhomepagePythonMITcommit 472b94039b5c
Python, MIT licensed. The project labels itself: version control, video and video editing.
vit runs. An Argusic agent installed it in 1.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
100/100 tests pass; vit CLI fully works with real git backend; AI merge degrades gracefully without GEMINI_API_KEY; Resolve panel scripts import cleanly (tkinter panel excluded due to missing tkinter in headless container)
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.
- pip install failed: externally-managed-environment0.2 minutes
- git commit failed: Author identity unknown0.1 minutes
- git checkout main failed: pathspec 'main' did not match0.1 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- python -m pytest tests/ -v: 100 passed; vit CLI commands exercised end to end (init, add, commit, branch, checkout, merge, log, diff, status, validate, --version)
- Model tokens used
- 48,377
- Exact commit tested
- 472b94039b5c
- 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.
48,377 All done. Here's the summary: **Install** — Created a venv and installed the package with all dependencies. 3 issues encountered … - System pip blocked → used venv - Missing git identity → set `user.email`/`user.name` - Default git branch is `master`, tests expect `main` → set `init.defaultBranch` **Verification** — All **100 tests pass**. The CLI was exercised end-to-end: - `vit init`, `vit add`, `vit commit`, `vit branch`, `vit checkout`, `vit merge`, `vit log`, `vit d… - Merge with `--no-ai` correctly reports conflicts on same-file edits - AI features gracefully degrade without `GEMINI_API_KEY` - Resolve panel backend scripts import cleanly (the Tkinter panel UI can't load without `tkinter`, … The result line has been printed above.
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 1.5 minutes.
- Recovered from all 3 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 2 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.
- A quick evaluation: it was running 1.5 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vit)Questions
- Does vit run?
- Yes. vit runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test vit?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 472b94039b5c. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test vit?
- 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 vit take to install?
- 1.5 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 vit need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vit?
- 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.
- Where is the evidence for vit?
- 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.