bark-notify-setup

Bark Notify Setup

Configure the current Claude Code environment (macOS, Linux, or Windows) to send a Bark notification when Claude finishes a turn.

Goals

After setup, the local machine should contain:

• macOS/Linux: ~/.claude/claude-stop-bark.sh
• Windows: %USERPROFILE%\.claude\claude-stop-bark.ps1
• hooks in ~/.claude/settings.json for Stop, StopFailure, SessionEnd, and Notification that all run that script asynchronously

Required behavior

1. Detect the current OS first.

   • Run uname -s 2>/dev/null (bash) or check if the working directory path starts with a drive letter.
   • If $env:OS is Windows_NT or the path looks like C:\... or D:\..., treat as Windows.
   • Otherwise treat as macOS/Linux.
   • Read ../bark-notify/references/config-patterns.md to get the platform-specific hook command and script template.

2. Confirm Bark prerequisites.

   • Read ../bark-notify/references/bark-prereqs.md.
   • Make sure the user has a Bark push URL.
   • Ask whether they want plain mode or encrypted mode.
   • If encrypted mode, require a 16-character key and remind them to match Bark app settings on iPhone.

3. Inspect current Claude config before writing.

   • Read ~/.claude/settings.json if it exists.
   • Never overwrite unrelated settings.
   • Merge in the Stop, StopFailure, SessionEnd, and Notification hooks safely.

4. Write the sender script using the platform template from ../bark-notify/references/config-patterns.md.

   macOS / Linux

   • Write ~/.claude/claude-stop-bark.sh.
   • Parse hook_event_name, reason, and cwd from stdin JSON using python3 -c "..." (do NOT use a python heredoc — it collides with the piped stdin payload). Do NOT read $HOOK_EVENT — Claude Code does not set that env var.
   • Hook command in settings.json: /bin/bash ~/.claude/claude-stop-bark.sh

   Windows

   • Resolve the absolute home path first (run $env:USERPROFILE in PowerShell) and embed it as a literal path.
   • Use the PowerShell plain/encrypted template exactly as shown in config-patterns.md.
   • 🛑 DO NOT use the Write tool to create claude-stop-bark.ps1. The Write tool writes UTF-8 without BOM. Windows PowerShell 5.1 then decodes the file using the system ANSI code page (GBK on Chinese Windows), which mangles the Chinese characters in string literals (已完成 etc.) and produces Unexpected token parse errors at hook execution time. You MUST write the file via PowerShell with an explicit UTF-8-with-BOM encoder:

     $content = @'
     <PASTE THE FULL .PS1 SCRIPT HERE>
     '@
     $utf8Bom = New-Object System.Text.UTF8Encoding($true)
     [System.IO.File]::WriteAllText("$env:USERPROFILE\.claude\claude-stop-bark.ps1", $content, $utf8Bom)
     

     Use a single-quoted here-string (@'...'@) so PowerShell does not interpolate $variables inside the script body. The closing '@ must be at column 0.
   • After writing, verify the BOM is present (first 3 bytes = EF BB BF). If missing, abort and re-write — the hook will silently fail at runtime otherwise.
   • Hook command in settings.json: powershell.exe -ExecutionPolicy Bypass -NoProfile -NonInteractive -File "C:\Users\<username>\.claude\claude-stop-bark.ps1" — use the resolved absolute path, not %USERPROFILE%.
   • Do NOT run chmod on Windows — PS1 files do not need executable bits.