The Clay plugin's bundled CLI launcher (bin/clay) only recognizes Darwin and Linux from uname -s, and the release ships only clay-darwin-arm64/x64 and clay-linux-arm64/x64 (glibc-linked). On native-Windows Claude Code, the Bash tool is Git Bash, which reports MINGW64_NT-10.0-26200, so every invocation fails at the launcher's OS gate:
$ clay whoami
{"error":{"code":"validation_error","message":"clay: unsupported OS: MINGW64_NT-10.0-26200"}}
This blocks the entire plugin (CLI, clay login, clay mcp, and even clay feedback, since the OS check runs before any subcommand dispatches).
Notes on the Windows situation:
- Git Bash / MSYS can't execute Linux ELF binaries, so pointing the launcher at the Linux build wouldn't help.
- WSL is present but only the
docker-desktop utility distro exists (musl-based), so the glibc-linked Linux binary would also fail there.
Requests:
- A native Windows build (
clay-win-x64) with launcher support for MINGW*/MSYS*/CYGWIN*, or
- Documented guidance that Windows users must run Claude Code + Clay inside a glibc WSL distro (e.g. Ubuntu), plus a clearer error message pointing there instead of a bare "unsupported OS."
Environment: Windows 11 (build 26200), Claude Code native-Windows, plugin clay 2.1.14.
The Clay plugin's bundled CLI launcher (
bin/clay) only recognizesDarwinandLinuxfromuname -s, and the release ships onlyclay-darwin-arm64/x64andclay-linux-arm64/x64(glibc-linked). On native-Windows Claude Code, the Bash tool is Git Bash, which reportsMINGW64_NT-10.0-26200, so every invocation fails at the launcher's OS gate:This blocks the entire plugin (CLI,
clay login,clay mcp, and evenclay feedback, since the OS check runs before any subcommand dispatches).Notes on the Windows situation:
docker-desktoputility distro exists (musl-based), so the glibc-linked Linux binary would also fail there.Requests:
clay-win-x64) with launcher support forMINGW*/MSYS*/CYGWIN*, orEnvironment: Windows 11 (build 26200), Claude Code native-Windows, plugin clay 2.1.14.