Warcraft III Peon Voice Notifications for Claude Code

Original Article ↗ Hacker News Discussion ↗

Nostalgia and voice-pack choices

  • Many commenters loved the idea and immediately requested or built variants with other RTS voices: Warcraft II/I, StarCraft (SCVs, Battlecruiser, Protoss advisor, medic, adjutant), Age of Empires II, Red Alert II, Commandos, TF2 engineer, CS 1.6, Helldivers, Stronghold Crusader, Portal’s GLaDOS, Star Trek computer, WOPR, etc.
  • Debate over the “correct” line for task completion (Warcraft III orc peon vs. human peasant “Job’s done!” / “Work complete”) became a mini lore discussion.
  • The project triggered strong LAN-party and childhood memories; people reminisced about specific missions, difficulty, favorite RTSes, and era-specific hardware.

Copyright and legality

  • Some argue redistributing Blizzard voice clips under an MIT-tagged repo is straightforward copyright infringement and emblematic of a broader “AI ignores copyright” culture.
  • Others counter that these are very short, decades-old clips that likely qualify as fair/transformative use and don’t harm any market, calling strict objections a misplaced extension of legitimate LLM copyright concerns.
  • There’s disagreement over whether this is “as bad as” LLM training on copyrighted works; some see it as equivalent, others as clearly smaller-scale and potentially fair use.
  • Several note that the MIT license applies only to code; audio assets remain under their original copyrights.

Security and installation concerns

  • Strong pushback on the curl | bash installer and large shell script: worries about blind trust, self-updating behavior, editing shell RC files, downloading arbitrary audio from remote JSON, and lack of clean uninstall.
  • Some argue this is no worse than traditional installers; others insist on package-manager-style installs or cloning and inspecting the repo (sometimes with Claude’s help) before running anything.
  • A few recommend sandboxing or forking just the sound assets, especially since media decoders have had remote-code-execution issues.

Implementation, UX, and platform support

  • Some see the hooks + JSON manifest system as nicely flexible; others think it’s overengineered for “play a sound on an event” and would prefer a simple directory-based layout.
  • Multiple examples show alternative notification setups (terminal OSC codes, desktop daemons, say/AppleScript, SSH relays, pure local TTS).
  • Initial lack of Linux support is repeatedly criticized; several people submit or announce Linux-compatible forks and variants for other editors/agents.

Broader AI and interface reflections

  • Many praise this as the kind of playful, creative AI integration that actually increases desire to use the tool, versus generic SaaS wrappers.
  • Some see it as an early example of “video game–like” interfaces for managing fleets of coding agents—suggesting future dev tools may lean heavily on game UI metaphors and sound design.