v0.3.9

Wind v0.3.9 — wind now guards the boundary between your repo and everything it touches — and meets an imperfect command with a suggestion instead of a shrug.

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.9 --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

Attach the file you actually have — text, Markdown, logs

wind attach stopped being images-only. The plan, the notes, the service log — they upload as themselves, filenames and bytes preserved, and come back as readable references:

wind attach plan.md notes.txt service.log

One edge to know: text needs the Wind Stream server to speak it too, which arrives with the platform's next deploy. Against an older server, wind refuses that one file with a plain reason and keeps going with the rest — your images still land.

The upload queue explains itself

When a trace or retrospective can't deliver — too big, offline, token expired — it no longer vanishes into a spool you can't see. It waits with a reason, and you have a hand on it:

wind sync            # deliver everything that can deliver now, one receipt per entry
wind sync status     # what's waiting, why, and what to do — no network
wind sync drop abc1  # discard one entry, loudly, on purpose

wind status shows one line when anything is waiting, and wind down opens with your worktree's queue state — a running session is never told "nothing pending" while its own trace is still to come.

Upgrade note: entries spooled by an older wind are stamped with the old default host and will sit parked after this upgrade. Run WIND_HOST=https://alpha.windstream.ai wind sync once and they drain — same backend, nothing lost.

A typo gets an answer

$ wind statsu
unknown command: statsu
did you mean: wind status?

And when you know what you want but not what it's called, ask in your own words — wind resolves it to a command and shows it, never runs it:

$ wind ask "wrap this session up"
wind ask · "wrap this session up"
  guess    wind down
  usage    wind down [--easy] [--inline] [--yes] [--message <text>]

ask is deliberately absent from the command index for now — matching by meaning needs a platform capability that's still on its way — but the verb works today for anyone who types it, and wind help ask says plainly what it can and can't do yet.

wind next — the one thing to do now

$ wind next
wind next · feature/dark-mode
  state    4 commits on feature/dark-mode, not pushed
  next     git push -u origin feature/dark-mode

It reads the session manifest, your git state, and the PR — then names one action and the exact command. It never runs anything, and when it couldn't look somewhere (gh signed out, no repo), it says which signal it lost instead of pretending the answer is "nothing".

Ambiguous topics ask you, not a coin flip

wind surf "dark mode work" used to silently continue the closest-matching thread — or fork a duplicate on a phrasing difference, permanently, because Wind Stream sessions are write-forward. Now several matches ask:

"dark mode work" matches more than one thread:
  1) dark mode
  2) dark mode rollout
  n) start a new thread
which thread? [1-2, n]

Typing a thread's exact title skips the prompt entirely — naming a thread is choosing it.

Open anything by id

wind open session-8WPGoDHQ    # or an outcome-…, att-…, any Wind Stream id

Works from any directory — no session manifest needed. The id resolves to the right page server-side, arriving with the platform's next deploy; until then the browser lands on the Wind Stream app shell.

The boundary got harder

This release treats everything wind touches on your behalf with suspicion on your behalf: a committed session manifest is vetted before any part of it reaches a filename, a git command, or your terminal (a tampered value refuses loudly and never echoes its bytes); URLs are validated before a browser ever sees them, and Windows no longer routes them through cmd.exe; the words you type into a retrospective are never lost to a refusal — worst case you get them back to copy.

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.9, commit c884d843617e19429f4593d63b5504429e493ff8. 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.