Does infinitunes run?

infinitunes runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.

How did Argusic test infinitunes?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 83d0b88a1db7. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test infinitunes?

The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does infinitunes take to install?

3 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 infinitunes need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing infinitunes?

4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for infinitunes?

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.

infinitunes

🎵 A Simple Music Player Web App built using ▲ Next.js, shadcn/ui, TailwindCSS, DrizzleORM and more...

Runs with mockssource: GitHub homepageTypeScriptMITcommit 83d0b88a1db7

TypeScript, MIT licensed. The project labels itself: app router, authjs, drizzle, drizzle kit, drizzle orm, jiosaavn api, jotai and music streaming.

infinitunes runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Infinitunes builds and serves its login page (HTTP 200) and static assets; dynamic pages fail because the external JioSaavn API is defunct and the inline mock data has partial type mismatches in the Modules response
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 87.7 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 87.7 / 100
cost of the verifying run: $0.14 (measured)
recorded runs: 2
last tested: 2026-09-19
stars: 361
forks: 78
open issues: 20
watchers: 1
size: 9 MB
created: 2022-11-22
last push: 2026-09-21

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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 infinitunes, 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.

Default JioSaavn API URL (jiosaavn-api-ts.vercel.app) returns DEPLOYMENT_NOT_FOUND30 minutes
experimental.ppr: true requires canary Next.js, but npm resolved to stable 15.5.252 minutes
package.json overrides field contains npm-incompatible alias syntax (npm:types-react@...)1 minute
npm peer dependency conflict due to React 19 RC version1 minute

Install time: 3 minutes
Cold machine to finish: 32 minutes
Errors hit and fixed: 4 hit, 4 fixed with no human help
How the result was proved: npm install completed (696 packages); next build compiled all 38 routes; next start served on port 3017; curl /login returned HTTP 200 with valid Next.js HTML; tsc --noEmit exited 0
Model tokens used: 361,422
Exact commit tested: 83d0b88a1db7
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 2026-09-09, 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.

 succeeded in 0ms:
Report ready
exec
/bin/sh -lc "ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_minutes…
 exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:{install_succeeded:true,launch_succeeded:true,install_minutes:3.0,errors…
The shell can't handle the long JSON as a command. Let me output it as a separate echo:
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_m…
 succeeded in 0ms:
tokens used
361,422

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 3 minutes.
Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
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

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs with mocks	83.43	0.14	2026-09-19 22:56 UTC
Argusic Runner	1/3	Runs with mocks	92.00	0.14	2026-09-09 20:26 UTC

Topics (from GitHub)

app-router authjs drizzle drizzle-kit drizzle-orm jiosaavn-api jotai music-streaming next-auth nextauth nextauthjs nextjs nextjs13 nextjs14 react shadcn-ui taiwindcss typescript unofficial-api

Embed the badge

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

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

Questions

Does infinitunes run?: infinitunes runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test infinitunes?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 83d0b88a1db7. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test infinitunes?: The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does infinitunes take to install?: 3 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 infinitunes need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing infinitunes?: 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for infinitunes?: 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.