Baixar Vayu 0.44.0 per a Windows

0.44.0 - 2026-10-17
Nothing to read before updating. This release makes load-test results easier to
trust and compare, adds Insomnia v5 import and Postman environment export, and
makes the first ten minutes smoother: a clearer welcome screen, curl paste, and
a fallback port when 9876 is taken.
Added
- Insomnia v5 import. Collections and environments exported as Insomnia v5
YAML import alongside the existing formats.
- Compare any two runs. A run in History can be compared with any other run
of the same request, with a warning when the two are not like for like, and a
p95, throughput and error-rate trend across a request's runs.
- A verdict on every load run. A finished run says whether it passed, on the
run itself and on its History row, and says so when the run was stopped.
Budgets carried over from a request are visible in the load-test dialogs and
tagged in the verdict.
- One report for a finished run. The dashboard shows History's report,
including the HDR plot, per-sample and slow-request views. The Samples tab
sorts by time, filters by status class, and error rows in the Overview link to
an example.
- Share a finished run. The new Export menu on a run, and the command
palette, save or copy it as Markdown (to paste into a PR or a chat), save
it as one self-contained HTML report with charts (to send to someone who
does not have Vayu), or save it as JSON. MCP agents get an export_run_report
tool that returns the report as Markdown or JSON. The same reports are available from
POST /export/run-report.
- Export an environment as a Postman environment from the environment row
menu.
- Vayu's own time per request. The response bar shows how much of a request's
time was Vayu's, not the server's.
- Import anywhere. Drop a file anywhere on the window to open the Import
dialog. Paste a curl command into the Import dialog or the URL bar to open it
as a request. The preview says which variables, auth and scripts came along,
and the import notes stay reachable inside the imported collection.
- A clearer first run. The welcome screen says what Vayu is for and offers
to connect a coding agent, and its New request tile works. If port 9876 is
taken, Vayu starts on another port and tells you which one to free.
- Load-test dialog. It names the target host and advises when it is not on
your network, shows a two-pane layout, and offers a collection load test the
same profiles as a request. "Virtual users" is the one name for the user
count. Fixed Iterations is now Fixed request count.
- MCP. The server runs on SDK v2 for both protocol eras.
- install.sh offers to open Vayu after a fresh install and refuses macOS
older than 13.3.
Changed
- The live error rate counts HTTP error responses, the same way every report and
MCP tool does.
- Runs are named Send, Collection run and Load test across History, the palette
and the welcome screen.
- The request and response tab strips fit the pane and move the rest into a
menu.
- An imported Postman environment is activated when none was.
Fixed
- Requests cancelled by Stop are counted apart from errors.
- A finished run no longer reports a lost live metrics stream.
- Scenario steps count HTTP error responses in their Errors tally, and replay
every enabled post-request script, never a disabled one.
- Sub-millisecond latencies print as such instead of "0 ms"; latency percentiles
and idle virtual users are no longer painted as failures; chart axes start at
zero and carry a unit.
- Counts and rates are grouped the same way on every run screen.
- A request rate below 10 req/s keeps a decimal instead of showing 0.
- The import loss report stays after a successful import.
- A root folder's badge counts its descendant requests.
- A file the OS hands Vayu opens in the Import dialog even when it is already
open.
- Internal: a vcpkg baseline bump (curl 8.23.0), documentation and comparison
pages brought back in line with the code, and test and refactoring work.
Every asset carries a build-provenance attestation: gh attestation verify <asset> --repo athrvk/vayu.
Which file do I download?
- macOS (Apple Silicon and Intel): run bash -c "$(curl --proto '=https' --tlsv1.2 -fsSL https://athrvk.github.io/vayu/install.sh)". The .dmg and .zip are the same universal build, unsigned.
- Windows (x64): winget install athrvk.Vayu, or Vayu-x64.exe.
- Linux (x86_64 only, there is no arm64 build): the .AppImage, or sudo apt install ./Vayu-amd64.deb.
- The .yml, .blockmap and .sha256 files are for the auto-updater and for checking a download. You do not need them.
If your OS warns you
Vayu is not code-signed, so the OS can stop a downloaded file on first launch. Nothing is wrong with the file.
macOS says an app downloaded from this page (.dmg or .zip) is "damaged", because Vayu is not notarized. This command installs it without the warning:
bash -c "$(curl --proto '=https' --tlsv1.2 -fsSL https://athrvk.github.io/vayu/install.sh)"
Windows shows "Windows protected your PC". Choose More info, then Run anyway. winget install athrvk.Vayu skips it.