wind connects Wind Stream workflows to the AI coding tools you work in — Claude Code and Codex today. It brackets a piece of work: wind up stands up a connected session, wind down closes the loop with a retrospective, and the trace returns to Wind Stream automatically. It's built for developer productivity — wind absorbs the setup so you don't have to think about it.
wind up <release> my-feature
→ worktree at ../worktrees/<repo>-<release>-my-feature, branched off release/<release>
→ Claude or Codex connects the worktree to a Wind Stream session
→ …do the work…
→ on session end, the hook returns a trace to Wind Stream
| Guide | What's in it |
|---|---|
| Install (macOS / Linux) | Binary install, wind setup, verification |
| Install (Windows) | PowerShell-first install, Windows gotchas |
| Getting started | The session lifecycle: up → work → down |
| Command reference | Every verb: synopsis, flags, behavior |
| wind proxy | Shadow one service behind another, score the parity window |
| wind factory | The software factory: a Wind Stream brief becomes a gated, evidenced pull request handed to a reviewer |
| What a trace contains | Everything the SessionEnd trace ships, listed up front |
| Troubleshooting | Symptom-first fixes |
Issues and support: success@windstream.ai