One command. No config required. novastorm figures out the rest.
npm install -g novastorm
Then create a nova.toml in your project root (optional):
Then run: nova — that's it.
A new paradigm. No prompts. No code. Just use your app.
novastorm never asks you to write code. It watches how you interact and generates patches from observed behavior.
Forget chat windows and prompt engineering. Your actions are the prompt. Click, scroll, hesitate — novastorm reads intent.
Run novastorm alongside your dev server. Use your app normally. Problems get detected and fixed in real time.
[ novastorm turns your frustration into features ]
Complete all 4 experiments to unlock your training rank.
try refreshing the weather data. [hint: the button is... somewhere]
select an area. speak your command. [click and drag]
something feels wrong here. [click two elements to swap]
[no instructions. just use the dashboard. novastorm is watching.]
novastorm operates on 4 processing lanes. Faster lane = simpler fix.
How novastorm compares to other development approaches.
| VIBE CODING | VISUAL-FIRST | SPEC-DRIVEN | AMBIENT | |
|---|---|---|---|---|
| Input method | Chat / prompt | GUI builder | Spec documents | None (observation) |
| Context awareness | ~ | ✘ | ~ | ✔ |
| Real user behavior | ✘ | ✘ | ✘ | ✔ |
| Zero-prompt fixes | ✘ | ✘ | ✘ | ✔ |
| Frustration detection | ✘ | ✘ | ✘ | ✔ |
| Continuous learning | ✘ | ✘ | ~ | ✔ |
| Setup complexity | Medium | High | High | 1 command |
Source-available. BSL 1.1. Free for small teams. Open MIT on March 20, 2029.
Not headcount. Unique git commit authors in a sliding 90-day window.
The manifesto. 10 parts. Why code was never the real bottleneck.
What ambient means. Five principles. How it works in practice.