Clay CLI/plugin launcher does not support native Windows (only macOS/Linux binaries published)

[DM-Gentwo]

The bundled bin/clay launcher (installed via the Claude Code plugin, version 2.1.13)
only recognizes Darwin and Linux from uname -s:

case "$os" in
  Darwin) os="darwin" ;;
  Linux) os="linux" ;;
  *) die "validation_error" "clay: unsupported OS: $os" 2 ;;
esac

On native Windows (Git Bash reports MINGW64_NT-10.0-26200), this immediately fails:

{"error":{"code":"validation_error","message":"clay: unsupported OS: MINGW64_NT-10.0-26200"}}

Checkingbin/checksums.txt confirms there's no Windows asset published at all —
only clay-darwin-arm64, clay-darwin-x64, clay-linux-arm64, clay-linux-x64 exist
on the clay-cli-v GitHub release. So this isn't just a detection gap in
the launcher script; there's no Windows binary to fall back to.

This affects any Windows user running Claude Code, Codex, or Cursor natively
(not under WSL) — clay whoami, clay login, and clay mcp (the MCP server)
all fail at the same bootstrap step, so the plugin is entirely unusable outside
WSL/macOS/Linux.

Requesting either a native Windows binary + launcher support, or at minimum a
clear error message pointing Windows users at WSL as the supported path.

Environment: Windows 11 Pro, Claude Code, plugin version 2.1.13, Git Bash (MINGW64).

[GirishVerm]

@DM-Gentwo
Thanks for the thorough writeup, and confirmed on both counts: the clay-cli-v0.1.14 release only publishes clay-darwin-arm64, clay-darwin-x64, clay-linux-arm64, and clay-linux-x64 — no Windows asset exists to fall back to.

Building and publishing native Windows binaries is a change to the clay CLI's own build/release pipeline (a different repo/process than this plugin), so it's out of scope here and we can't ship that from agent-plugins directly.

What we can do from this repo — and have opened #12 for — is the fallback you suggested: bin/clay now recognizes Git Bash/MSYS/Cygwin's uname -s output (MINGW64_NT-*, MSYS_NT-*, CYGWIN_NT-*) and fails with a clear, actionable message instead of the generic "unsupported OS" error, pointing you at WSL as the supported path in the meantime:

clay: native Windows is not supported yet (no Windows CLI binary is published) — run Claude Code, Codex, or Cursor inside WSL instead

We'll leave this issue open to track native Windows binary support as the larger ask.