v0.3.8

Wind v0.3.8 — Pick your coding agent and keep the bracket: wind up now launches Claude Code, Codex, or Antigravity — with the full connect → trace → retrospective loop operational on Codex — and every SessionEnd trace carries metadata.provenance v1: what produced this work and what it took.

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

Pick your coding agent — wind agent, wind up --agent

The wind bracket used to mean Claude Code, full stop. Now you choose the agent and the bracket follows:

wind agent codex          # persist your default
wind up v0.4.0 dark-mode  # opens the seat in Codex
wind up feature spike --agent claude   # one-off override, any wind up form

claude, codex, and antigravity are the three choices. Nothing to migrate: with no preference set, wind launches Claude Code exactly as before.

One edge to know: the agent is resolved before anything is created, so a bad preference or a missing credential refuses up front — you'll never find a fresh worktree stranded behind a launcher that couldn't start.

Codex runs the whole loop

Selecting Codex isn't just a launcher swap — the full Wind Stream bracket works: wind setup configures Codex's native MCP and lifecycle hooks and installs the $windstream-connect skill, sessions open connected, and when Codex exits your session trace is uploaded by the waiting wind up process, so the return path fits inside Codex's strict hook time budget.

Your Wind Stream token never lands in a Codex config file or a command line — Codex reads it from the child process environment, and wind auth login knows which agent's configuration to reconcile.

Two edges to know: Codex asks you to trust the installed hooks once (run /hooks inside Codex — setup installs them but can't trust them for you), and on the Wind Stream side a Codex trace currently displays under the Claude Code integration label until the server presents agents neutrally. Antigravity launches too, but as a launcher only — its return path is a later train.

Your trace says what produced it — and what it took

Every session trace now carries provenance: which harness and model did the work, the billing context it ran under (billing mode, whether an API key was present — never the key itself, and whether fast mode was on), and the git context it came from. Wind ships the raw signal; the platform turns it into pricing and reporting.

The full list of what a trace contains — everything, up front — is documented in docs/trace.md.

Frame an Outcome across several eval families at once

wind eval outcome frame char-empathy char-rigor char-wit \
  --statement "Opus 5 character holds across families" \
  --exit-condition "all six families green two eras running"

Every listed family binds to the one Outcome at birth, in order. And when an era closes, next inherits: run it with no list and the successor re-links everything the prior linked — the same lines, one era richer. Pass an explicit list only when you mean to restate the full set — the list you pass is the successor's set, so a family you omit is dropped on purpose.

If a bind fails partway, wind tells you exactly where things stand — linked so far, failed, not attempted — instead of leaving you to guess.

wind up inside a worktree no longer buries the new one

Running wind up from inside an existing worktree used to nest the new one at worktrees/worktrees/… under a mangled name. Now wind notices and offers the fix:

this is a worktree of ~/Developer/GitHub/wind — new worktrees would nest under ~/Developer/GitHub/worktrees/worktrees
anchor to the main checkout (~/Developer/GitHub/wind)? [Y/n]

Enter (or Y) puts the new worktree where it belongs, as a sibling under worktrees/ with the real repo name. n keeps the old behavior on purpose. Scripts and agents get the anchor automatically — announced, never silent.

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.8, commit e9d32c1b419ce10047eb06b0efacafccfcfef7c1. 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.