chat-demo

Chat Demo

Runssource: GitHubhomepageTypeScriptMITcommit 5d5dd754ebc1

TypeScript, MIT licensed.

chat-demo runs. An Argusic agent installed it in 7 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The project builds via pnpm build producing a dist/ folder with index.html, JS, CSS, and assets, the dev server starts and serves the app on port 8090 returning HTTP 200, and TypeScript type checks pass with zero errors.

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

At a glance

verdict
Runs
Argusic Score
90 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
4,988
forks
1,123
open issues
1
watchers
18
size
0 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 chat-demo, 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.

  • Node.js v18.19.1 bundled in container, but Rspack requires Node.js 20.19+ or 22.12+2 minutes
  • pnpm not pre-installed; npm install -g pnpm failed due to EACCES on /usr/local1 minute
Install time
7 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
pnpm build exited 0 (Rspack compiled successfully in 2.08s), pnpm type exited 0, pnpm dev served HTTP 200 at localhost:8090 with compiled JS/CSS assets
Model tokens used
12,136
Exact commit tested
5d5dd754ebc1
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.

/bin/sh -lc 'kill %1 2>/dev/null; true' in /work/repo
 succeeded in 0ms:
Now let me record the final JSON result. All steps completed successfully.
exec
/bin/sh -lc 'echo "Time check"; date +%s' in /work/repo
 succeeded in 0ms:
Time check
1794986293
Let me calculate the elapsed time and produce the final JSON. The session started ~7 minutes ago.
tokens used
12,136
Let me calculate the elapsed time and produce the final JSON. The session started ~7 minutes ago.

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 2 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 7 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.

Of the 37 TypeScript projects Argusic has installed and timed, chat-demo was the 28th fastest to reach a running state, and 31 of 37 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 7 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Unverified80.000.04
Argusic Runner1/3Runs100.000.02

Embed the badge

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

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

Questions

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