open-genjutsu
Local-first AI video recasting with draft review, explicit HD approval, and source-audio restoration.
Runs with mockssource: GitHubJavaScriptMITcommit f2045a2a90bd
JavaScript, MIT licensed. The project labels itself: ai media, ai video, character replacement, character swap, creative tools, fastapi, ffmpeg and generative ai.
open-genjutsu runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.1 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Open Genjutsu FastAPI app installs, starts, and serves all 7 API endpoints plus static frontend files. With the mock API in place, the upload-source -> upload-reference -> recast -> prediction -> export -> download -> clear flow completes successfully and the exported MP4 passes ffmpeg validation.
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. 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.
- Self-signed SSL certificate CN mismatch with 127.0.0.1 when connecting to mock API2 minutes
- Install time
- under a minute
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- Python script started mock API on port 8769 (HTTPS) and app on port 8770, then called health (200), upload source (200), upload reference (200), recast (200), prediction (200), export (200), download (200, 32225 bytes), and clear (200). Exported MP4 validated with 'ffmpeg -v error -i FILE -f null -' (PASS). Root and static files also serve 200.
- Model tokens used
- 298,873
- Exact commit tested
- f2045a2a90bd
- 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
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 1, 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.
/bin/sh -lc 'ls /work/repo/mock_api.py 2>/dev/null && echo "exists" || echo "not found"' in /work/r… succeeded in 0ms: /work/repo/mock_api.py exists exec /bin/sh -lc 'cd /work/repo && ls runtime/assets/ 2>/dev/null; ls runtime/exports/ 2>/dev/null; ls m… succeeded in 0ms: mock_api.py All tests pass. Here is the final report: tokens used 298,873 All tests pass. Here is 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
- Installed in 0.1 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, 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.11 |
Topics (from GitHub)
ai-mediaai-videocharacter-replacementcharacter-swapcreative-toolsfastapiffmpeggenerative-ailocal-firstmedia-processingomni-referenceopen-genjutsupythonseedanceself-hostedvideo-editingvideo-generationvideo-to-videovideo-transformationvideo-workflow
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/open-genjutsu)Questions
- Does open-genjutsu run?
- open-genjutsu runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test open-genjutsu?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f2045a2a90bd. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test open-genjutsu?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does open-genjutsu take to install?
- 0.1 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 open-genjutsu need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing open-genjutsu?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for open-genjutsu?
- 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.