v0.3.10

Wind v0.3.10 — Wind can now move a verified proxy test set through Wind Stream and replay one exact version against a candidate service.

Install

This repository is private during pipeline bring-up; install via gh:

# pick your build: wind-darwin-arm64 / wind-darwin-x64 / wind-linux-x64 / wind-windows-x64.exe
gh release download v0.3.10 --repo windstreamai/wind-cli -p 'wind-darwin-arm64' -p SHA256SUMS
shasum -a 256 -c <(grep darwin-arm64 SHA256SUMS)
chmod +x wind-darwin-arm64 && sudo install wind-darwin-arm64 /usr/local/bin/wind
wind setup

What's new

Replay the exact version you tested

A recorded proxy set can now move through Wind Stream without becoming a moving target. Push the set once, pull the exact version you need, and replay that version against the service you are considering:

wind proxy push id3-set --config wind-proxy.json
wind proxy pull <set-id> --version <version-id> --out ./id3-baseline
wind proxy replay --set <set-id> --version <version-id> --against http://localhost:7002 --service id3 --window release-check

Wind verifies the manifest and payload digests before it writes a download or sends candidate requests. There is no latest selector, so a concurrent upload cannot change the set you are replaying. If a network response is lost after an upload succeeds, rerunning the same push resumes the same version rather than creating another one.

Ask Wind in plain language

wind ask now works with the live assist service. It maps an intent to a command and shows you the command; it never runs it:

$ wind ask "how do I upload a screenshot?"
  command  wind attach

The command descriptions sent for routing now fit the service limits, and an explicit question has enough time to receive an answer. Ambient suggestions remain quiet when Wind has nothing useful to add.

Your connection files stay out of the way

wind connect now adds Wind's own session files to your repository's local Git excludes. A newly connected worktree stays clean, and a routine git add -A will not stage its session metadata.

Better operational evidence, when you opt in

Wind can preserve a content-free record of what happened when it consulted assist: answered, declined, suppressed by policy, or failed. The record survives a normal CLI exit and restart, and identifies the compiled build that produced it. Collection remains off until your organization enables it; this release only makes the client ready to report the outcome it actually experienced.

Docs

• Getting started — the guided walkthrough
• Command reference — every verb, its flags, and how it exits
• Install · Windows · Troubleshooting

Provenance

Built and published by the wind publish pipeline from windstreamai/wind
tag v0.3.10, commit f1048d9481a20807c44e706179299b5cc9ec8a1d. Assets are
checksum-verified before this release is published (see SHA256SUMS).

License

Proprietary — see EULA.md, governed by the
Wind Stream Terms of Service.
Third-party notices: THIRD_PARTY_NOTICES.md.