VideoCoF
[CVPR 2026 Highlight] VideoCoF: Unified Video Editing with Temporal Reasoner
Runs with mockssource: GitHubhomepagePythonApache-2.0commit 153e6bb31c59
Python, Apache-2.0 licensed. The project labels itself: diffusion models, long video editing, long video generation, video diffusion transformers, video editing, video generation and video to video.
VideoCoF runs, with stand-ins for the services it depends on. An Argusic agent installed it in 5 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Gradio demo app with 74 UI components serves HTTP 200 on port 7860, all core Python modules import successfully, video-to-video CoT pipeline construction verified, grounding instruction extraction works for all 4 task types
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 92 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.
- diffusers 0.42.1 requires torch.accelerator (PyTorch >=2.6) but torch 2.5.1 installed2 minutes
- Gradio 3.48 unable to launch with share=False due to container localhost unavailability; starlette/jinja2 version conflict caused TemplateResponse TypeError2 minutes
- scipy 1.18.1 requires numpy >=2.0 but numpy 1.26.4 was installed; numpy.long attribute missing1 minute
- transformers 5.x removed FLAX_WEIGHTS_NAME import used by diffusers 0.311 minute
- Gradio 4.x incompatible with app (gradio_client error, argparser mismatch); needed gradio 3.x1 minute
- Missing asset/1.png gallery placeholder images referenced in videox_fun/ui/ui.py line 260-2670.5 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- curl -s http://127.0.0.1:7860/config returned 200 with version 3.48.0, mode=blocks, 74 components; curl -s -o /dev/null -w %{http_code} http://127.0.0.1:7860/ returned 200
- Model tokens used
- 136,155
- Exact commit tested
- 153e6bb31c59
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
verified_how: curl -s http://127.0.0.1:7860/config returned 200 with 74 components
final_state: Gradio demo app with 74 UI components serves HTTP 200 on port 7860
Here is my final assessment:
exec
/bin/sh -lc "cd /work/repo && echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"ins…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 5, "errors": [{"msg": "dif…
exec
/bin/sh -lc "printf 'ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install…
succeeded in 0ms:
tokens used
136,155Replay 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
- Installed in 5 minutes.
- Recovered from all 6 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.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 with mocks | 92.00 | 0.22 |
Topics (from GitHub)
diffusion-modelslong-video-editinglong-video-generationvideo-diffusion-transformersvideo-editingvideo-generationvideo-to-video
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/videocof)Questions
- Does VideoCoF run?
- VideoCoF runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 5 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test VideoCoF?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 153e6bb31c59. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test VideoCoF?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does VideoCoF take to install?
- 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 VideoCoF need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing VideoCoF?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for VideoCoF?
- 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.