camera.ui

Local-first camera and NVR platform. Every camera you own. One app.

Runssource: GitHubhomepageTypeScriptMITcommit c5fcc0860588

TypeScript, MIT licensed. The project labels itself: ai, camera ui, cameras, cctv, detection, face recognition, home assistant and home automation.

camera.ui runs. An Argusic agent installed it in 15.2 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

camera.ui v2.2.7 server builds and runs, serving the web UI at https://localhost:3443 with Go2RTC streaming, NATS messaging, and the NVR plugin all operational

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.17 (measured)
recorded runs
2
last tested
stars
1,153
forks
172
open issues
5
watchers
23
size
74 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.

Time lost to each failure while testing camera.ui, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • @camera.ui/[email protected] not in npm registry (404)6 minutes
  • vite build failed with MISSING_EXPORT errors from @camera.ui/nvr stub4 minutes
  • vue-tsc --build OOM (heap out of memory in 773MB container)2 minutes
  • Node.js v18.19.1 < required >=22.18.0; npm ERR EBADENGINE on many packages0.5 minutes
  • Server config write failed: ENOENT volume subdirectory0.1 minutes
Install time
15 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
curl -sk https://localhost:3443/ returned 200; service --help printed correctly; server Go2RTC, NATS, NVR plugin all started and served the web UI
Model tokens used
218,487
Exact commit tested
c5fcc0860588
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.

**Installed and launched camera.ui v2.2.7** in the container. The full setup (npm install, Python v…
**Errors encountered and fixed:**
1. **Node.js version mismatch** — v18 bundled, project requires >=22.18. → Downloaded v22.18.0 tarb…
2. **`@camera.ui/[email protected]` unpublished** — npm 404. → Created a local stub with all 55 exports t…
3. **vue-tsc OOM** — 773MB RAM insufficient for type-checking. → Ran vite build directly with incre…
4. **Incomplete nvr stub** — first stub missed many exports. → Generated comprehensive stub matchin…
5. **Server missing volume directory** — ENOENT on config write. → Created the directory before lau…
**Verification results:**
- `curl -sk https://localhost:3443/` returned **200**
- Server logs confirmed Go2RTC, NATS, and NVR plugin all started
- `cameraui --help` printed correctly
- Python SDK/Common/RPC packages all importable

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.
  • Recovered from all 5 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 did not, or is not known

  • Took 15.2 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.

Of the 237 ai projects Argusic has installed and timed, camera.ui was the 199th fastest to reach a running state, and 168 of 237 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.

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 Runner2/3Runs100.000.17
Argusic Runner1/3Runs100.000.06

Topics (from GitHub)

aicamera-uicamerascctvdetectionface-recognitionhome-assistanthome-automationhomekithomekit-secure-videoip-cameralocal-firstnvrobject-detectiononvifrtspsecurity-camerasurveillanceuivideo-surveillance

Embed the badge

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

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

Questions

Does camera.ui run?
Yes. camera.ui runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test camera.ui?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c5fcc0860588. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test camera.ui?
The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does camera.ui take to install?
15.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 camera.ui need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing camera.ui?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does camera.ui compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, camera.ui was the 199th fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for camera.ui?
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.

Discussion