Argusic could not verify that nWave runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.

How did Argusic test nWave?

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

What did it cost to test nWave?

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

How long does nWave take to install?

8 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 nWave need a GPU?

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

What goes wrong when installing nWave?

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.

Where is the evidence for nWave?

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.

nWave

AI agents that guide you from idea to working code, with you in control at every step.

Could not verifysource: GitHub homepagePythonMITcommit da401a8384dc

Python, MIT licensed. The project labels itself: agentic ai, agentic coding, agentic framework, agentic workflow, ai, atdd, bdd and claude code.

Argusic could not get nWave running. An Argusic agent installed it in 8 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

nwave-ai v3.22.2 installed in a venv, deploys to ~/.claude/ for Codex CLI, all 10 doctor checks pass, 34 agents and 151 skills install successfully, and all key Python modules (nwave_ai.cli, des.domain, nwave_ai.sync, nwave_ai.outcomes) import without 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 80 of 100 (the mean of this project's run scores).

At a glance

verdict: Could not verify
Argusic Score: 80 / 100
cost of the verifying run: $0.04 (measured)
recorded runs: 2
last tested: 2026-09-21
stars: 617
forks: 63
open issues: 32
watchers: 8
size: 8 MB
created: 2026-02-13
last push: 2026-09-16

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 nWave, 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.

pip install -e failed: pyproject.toml references lib/python/des which does not exist — DES code is at src/des/2 minutes
pip install failed: externally-managed-environment (PEP 668) blocks system-wide install1 minute

Install time: 8 minutes
Cold machine to finish: 7 minutes
Errors hit and fixed: 2 hit, 2 fixed with no human help
How the result was proved: nwave-ai version returned 'nwave-ai 3.22.2'; nwave-ai doctor --json returned 10/10 checks passed; python -c 'import nwave_ai.cli, nwave_ai.sync, nwave_ai.outcomes, des.domain' succeeded; nwave-ai install --platform codex deployed 34 agents, 151 skills, all hooks, and exited 0
Model tokens used: 147,133
Exact commit tested: da401a8384dc
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
Whether it works at all: this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

      "message": "Package and framework in sync (v3.22.2)",
      "remediation": null
    }
  ],
  "summary": {
    "total": 10,
    "passed": 10,
    "failed": 0
  }
}
tokens used
147,133

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 8 minutes, faster than the median of the 7 comparable projects Argusic has measured.
Recovered from all 2 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

An agent with no time limit did not get it running.

Of the 8 agentic-ai projects Argusic has installed and timed, nWave was the 4th fastest to reach a running state, and 5 of 8 reached one at all.

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	2/3	Unverified	80.00	0.04	2026-09-21 07:37 UTC
Argusic Runner	1/3	Unverified	80.00	0.11	2026-09-21 07:30 UTC

Topics (from GitHub)

agentic-ai agentic-coding agentic-framework agentic-workflow ai atdd bdd claude-code claude-code-cli claude-code-commands claude-code-hooks claude-code-skills claude-code-subagents devops lean-ux opencode software-architecture software-craftmanship tdd

Embed the badge

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

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

Questions

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