This source preview helps you turn a request into a result you can inspect. Use it for work where you can tolerate changes to the workflow. For a whole feature, nWave can retain decisions, a public acceptance check, review, and delivery evidence. You can also run one DES step or work directly when less needs to survive the session.
Build: d5ad2352f from atdd_pure_staging (d5ad2352f089e55bfd80eb49b23493e04e7bd11e). This channel installs from a clone of this repository; it does not publish to PyPI. Check the exact release receipt before using a wheel from another channel.
You need Python 3.10+, Git, uv, and either Claude Code or Codex CLI. On Windows, use WSL. Install your chosen coding host separately.
git clone https://github.com/nWave-ai/nWave-experimental.git nWave-experimental
cd nWave-experimental
uv syncFrom the clone, install into the host you use. Choose one command:
uv run python -m nwave_ai.cli install --platform claude-code
# Or, for Codex CLI:
uv run python -m nwave_ai.cli install --platform codexUse --dev only when you intend a development-mode installation from the checkout. For Claude Code, run uv run python -m nwave_ai.cli doctor in the clone and address any failing check. For Codex, check the installer's final Codex validation; doctor checks Claude Code assets. Quit and reopen the selected host after installation.
The clone's .venv/bin/nwave-ai is a local executable. Bind its absolute path before moving to your project; uv run does not add nwave-ai to your global PATH.
NWAVE_CLI="$(pwd -P)/.venv/bin/nwave-ai"
cd /path/to/your/project
"$NWAVE_CLI" project enable
"$NWAVE_CLI" statusCheck that status says This project is active. Open the restarted host in that project. In Claude Code, ask /nw-buddy What should I do next?. In Codex, invoke $nw-buddy and ask the same question. These are host skills, not shell commands. Then describe who uses the change, its input, and the result you expect. See Your First Feature for an end-to-end example.
| Route | Use it when | What remains |
|---|---|---|
| Spine waves | A whole feature needs decisions and checks that outlive the session. | Durable authorities, applicable independent review, and delivery evidence. |
| Individual DES steps | You need one scoped product, design, oracle, craft, verify, or integration step. | That step's closed outcome and applicable artifacts. NEXT is advice, not an automatic transition. |
| Direct work | Little needs to survive the session and a late refusal is cheap. | No nWave gate, independent review, or retained authority is attested. |
The assistant and you choose the route for each request. A DES step can report Success, Refusal, Retry, or Indeterminate; treat an uncertain result as uncertain. A completed step is not a completed feature. Check the delivered behavior through its user surface. See the route guide and CLI reference.
Select a provider and model explicitly with the nw-rigor guidance. A competence label does not select a model automatically. Documentation density and optional explanation are separate settings; neither removes the checks required by the route you select.
Your native coding host runs the installed specialists and chooses the next action. DES constructs documents/facts, measures actual RED/GREEN, records results and performs explicitly requested native/Git operations; it never launches models. Independent review and fresh source-blind EXAMINE remain required where applicable. See the role invocation contract.
For this source preview, update the clone, resync its environment, reinstall into the same host, and restart that host. Do not replace it with a public-package upgrade. Automatic release checks and installation require separate permissions and controlled startup; the installation guide explains the limits. Its supported launch wrappers cover four hosts, while install and diagnostic coverage differ by host.
Coming from v3? Read the migration guide before changing persisted work. A successful preview does not prove that an active v3 delivery can resume in v4. The archived package recovery procedure applies only to its named predecessor and a verified release receipt.
nWave keeps workflow artifacts locally and collects no telemetry. Your coding host handles its own provider traffic; explicitly authorized external calls can send permitted data. See the privacy policy. Report defects through GitHub Issues. nWave is MIT licensed.