HN 표시: Voxlert – SHODAN과 StarCraft 부관이 내 에이전트 세션을 설명합니다.

LLM-generated voice notifications for Claude Code, Cursor, OpenAI Codex, pi, and OpenClaw, spoken by game characters like the StarCraft Adjutant, Kerrigan, C&C EVA, SHODAN, and more. Existing notification chimes (like peon-ping) do a great job of telling you when something happened, but not what happened or which agent needs your attention. If you have several agent sessions running at once, you end up alt-tabbing through windows just to find the one waiting on you. Voxlert makes each session speak in a distinct character voice with its own tone and vocabulary. You hear "Query efficiency restored to nominal" from the HEV Suit in one window and "Pathetic test suite for code validation processed" from SHODAN in another, and you know immediately what changed. Because phrases are generated by an LLM instead of picked from a tiny fixed set, they stay varied instead of becoming wallpaper. Voxlert is for users who: - Run two or more AI coding agent sessions concurrently (Claude Code, Cursor, Codex, pi, OpenClaw) - Get interrupted by notification chimes but can't tell which window needs attention - Want ambient audio feedback that doesn't require looking at a screen - Are comfortable installing local tooling (Node.js, optionally Python for TTS) If you run a single agent session and it's always in focus, Voxlert adds personality but not much utility. If you run several at once and context-switch between them, it's meaningfully useful. Minimum: Node.js 18+ and afplay (macOS built-in) or FFmpeg (Windows/Linux). That's enough to get started; TTS and SoX are optional. | Aspect | macOS | Windows | Linux | |---|---|---|---| | Node.js 18+ | nodejs.org or brew install node | nodejs.org or winget install OpenJS.NodeJS | nodejs.org or distro package (for example sudo apt install nodejs ) | | Audio playback | Built-in (afplay ) | FFmpeg so ffplay is on PATH | FFmpeg so ffplay is on PATH | | Audio effects | SoX (optional) | SoX (optional) | SoX (optional) | See Installing FFmpeg and Installing SoX for platform-specific commands. You will also want: - An LLM API key from OpenRouter (recommended), OpenAI, Google Gemini, or Anthropic. You can skip this and use fallback phrases only. - At least one TTS backend if you want spoken output instead of notifications only. | Backend | Best for | Requirements | |---|---|---| | Qwen3-TTS (recommended) | Apple Silicon or NVIDIA GPU | Python 3.13+, 16 GB RAM, ~8 GB disk | | Chatterbox | Any platform with GPU | Python 3.10+, CUDA or MPS | The setup wizard auto-detects running TTS backends. If none are running yet, setup still completes, but you will only get text notifications and fallback phrases until you start one and rerun setup. Can't run local TTS? Both backends require a GPU or Apple Silicon. Voxlert still works without TTS — you'll get text notifications and fallback phrases. Need help? Post in Setup help & troubleshooting. npx voxlert --onboard The setup wizard configures: - LLM provider and API key - Voice pack downloads - Active voice pack - TTS backend - Platform hooks for Claude Code, Cursor, Codex, and pi For OpenClaw, install the separate OpenClaw plugin. Start Qwen3-TTS or Chatterbox, then run: voxlert setup This lets the wizard detect the backend and store it in config. voxlert test "Hello" You should hear a phrase and see a notification. If you do not hear speech, check that: - A TTS server is running voxlert config shows the expectedtts_backend Visual notifications: Voxlert shows a popup with each phrase without extra install. On macOS you can use the custom overlay or system Notification Center. On Windows and Linux you get system toasts. Change it anytime with: voxlert notification Run npm install inside cli/ , then use node src/cli.js or link it globally if you prefer. Config and cache live in ~/.voxlert (Windows: %USERPROFILE%\.voxlert ). Run tests locally with: npm test The sc1-adjutant preview below uses the animated in-game portrait GIF from assets/sc1-adjutant.gif . More coming soon: Request a voice voxlert voice Installed through voxlert setup . Claude Code hook events are processed by: voxlert hook Installed through voxlert setup , or add hooks manually in ~/.cursor/hooks.json : { "version": 1, "hooks": { "sessionStart": [{ "command": "voxlert cursor-hook", "timeout": 10 }], "sessionEnd": [{ "command": "voxlert cursor-hook", "timeout": 10 }], "stop": [{ "command": "voxlert cursor-hook", "timeout": 10 }], "postToolUseFailure": [{ "command": "voxlert cursor-hook", "timeout": 10 }], "preCompact": [{ "command": "voxlert cursor-hook", "timeout": 10 }] } } | Cursor Hook Event | Voxlert Event | Category | |---|---|---| sessionStart | SessionStart | session.start | sessionEnd | SessionEnd | session.end | stop | Stop | task.complete | postToolUseFailure | PostToolUseFailure | task.error | preCompact | PreCompact | resource.limit | Restart Cursor after installing or changing hooks. See Cursor integration for details. Voxlert uses Codex's notify config so that completed agent