777genius/claude-notifications-go

Windows: no windows-amd64 binary shipped (Windows notifier code exists but never built/attached)

Open

#108 opened on Jul 10, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (100 forks)auto 404
buggood first issuewindows

Repository metrics

Stars
 (759 stars)
PR merge metrics
 (PR metrics pending)

Description

Problem

No Windows binary ships, so the plugin can't run on Windows even though the Windows notification code exists.

Detail

  • The repo has full Windows support in source: internal/notifier/bell_windows.go, focus_windows.go, terminal_windows.go (go-toast + beeep).
  • bin/hook-wrapper.sh has detect_windows_binary() looking for bin/claude-notifications-windows-<arch>.exe.
  • But bin/ only contains the darwin symlink (claude-notifications -> claude-notifications-darwin-arm64); no claude-notifications-windows-amd64.exe is committed or attached to any release.
  • Result: on Windows the wrapper finds no binary and the hooks no-op.

Building locally works: CGO_ENABLED=1 CC=<mingw-gcc> GOOS=windows GOARCH=amd64 go build -o bin/claude-notifications-windows-amd64.exe ./cmd/claude-notifications produces a working exe (malgo/CGO needs a mingw toolchain, not MSVC clang).

Suggestion

Attach claude-notifications-windows-amd64.exe to releases (the release.yml matrix already builds it with CGO_ENABLED: '1' on windows-latest) — or document the local build step for Windows users.

Env

Windows 11, Go 1.26.5, plugin v1.40.0

Thanks for the great work on claude-notifications-go!

Contributor guide

Research direction
Examine the release.yml CI workflow to understand how binaries are built and attached. The Windows binary (claude notifications windows amd64.exe) is already built in the CI matrix but missing from release assets. Either add it to the release assets or document the local build steps for Windows users.
Tech stack
go
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75