A standalone CLI tool to send desktop notifications from the terminal via OSC escape sequences or native tools.

• OSC-first: Works over SSH, inside tmux/screen
• Smart fallbacks: Uses native tools when OSC unavailable
• Cross-platform: macOS, Linux, Windows
• Zero dependencies: Single binary, no runtime requirements

brew install soloterm/tap/tnotify

go install github.com/soloterm/tnotify@latest

Download from GitHub Releases.

# Simple notification
tnotify 'Build complete!'

# With title
tnotify -t 'My App' 'Task finished'

# With urgency (low, normal, critical)
tnotify -u critical 'Server down!'

# Notification ID for updates (Kitty only)
tnotify -i progress 'Building... 50%'
tnotify -i progress 'Building... 100%'
tnotify --close progress

# Pipe input
echo 'Done' | tnotify -t 'Results'

# Force specific method
tnotify --osc 'Uses escape sequences only'
tnotify --native 'Uses osascript/notify-send only'
tnotify --bell  # Just beep

# Show capabilities
tnotify --capabilities

# Diagnose notification issues
tnotify --diagnose

# Exit code integration (auto-sets urgency)
make build; tnotify -e $? 'Build finished'      # critical if failed
make test; tnotify -e $? --if-failed 'Tests failed!'

# Progress bar in terminal tab/taskbar (Windows Terminal, Ghostty)
tnotify -p 50                        # 50% progress
tnotify -p 100 --progress-state error  # Red/error state at 100%
tnotify --progress-clear             # Clear progress bar

# Request attention (iTerm2 - bounces dock icon)
tnotify --attention
tnotify --fireworks  # With fireworks animation

# Check version and for updates
tnotify --version

Ghostty (OSC 777)	iTerm2 (OSC 9)	macOS Native Fallback

iTerm2	Ghostty

Use -e / --exit-code to pass the previous command's exit code:

# Notify with auto-urgency (critical if non-zero)
long-running-task; tnotify -e $? 'Task complete'

# Only notify on failure
make test; tnotify -e $? --if-failed 'Tests failed!'

# Combine with title
./deploy.sh; tnotify -e $? -t 'Deploy' 'Finished'

The --if-failed flag skips the notification entirely if the exit code is 0.

Show progress in terminal tabs or taskbar. Supported by Windows Terminal, Ghostty (1.2+), and iTerm2 (3.6.6+). On unsupported terminals, -p prints plain text instead.

# Normal progress (green)
tnotify -p 50

# Error state (red)
tnotify -p 100 --progress-state error

# Paused state (yellow)
tnotify -p 75 --progress-state paused

# Indeterminate/pulsing
tnotify -p 0 --progress-state indeterminate

# Clear progress bar
tnotify --progress-clear

The progress bar appears at the top of the terminal window (Ghostty) or in the taskbar (Windows Terminal). Use tnotify --capabilities to check if your terminal supports progress bars.

Bounce the dock icon or flash the taskbar (iTerm2):

tnotify --attention          # Standard attention request
tnotify --fireworks          # With fireworks animation

I have no idea why you'd use this, but here we are.

When OSC notifications aren't supported, tnotify falls back to:

• macOS: osascript (AppleScript)
• Linux: notify-send (libnotify)
• Windows: PowerShell toast notifications

Notification doesn't appear?

Run the diagnostic command to test all notification methods:

tnotify --diagnose

This will show your detected terminal, test each method, and report what works.

Common issues:

1. macOS Focus Mode — If you're using Focus/Do Not Disturb, your terminal app must be added to the allowed apps list. Go to System Settings → Focus → [Your Focus Mode] → Allowed Apps and add Ghostty, iTerm2, or your terminal.

2. Terminal is focused — Many terminals suppress notifications when the terminal window is focused. This is intentional. Test by switching to another window:

   sleep 3 && tnotify 'Hello!'  # Switch windows during the sleep

3. Notification permissions — Check System Settings → Notifications and ensure your terminal app has notifications enabled with "Banners" or "Alerts" style.

4. Native fallback on macOS — Native notifications use osascript, which sends notifications as "Script Editor". Enable notifications for Script Editor in System Settings → Notifications.

5. Linux: notify-send not installed — The native fallback requires libnotify. Install it with:

   # Debian/Ubuntu
   sudo apt install libnotify-bin
   # Fedora
   sudo dnf install libnotify
   # Arch
   sudo pacman -S libnotify

6. Windows: Focus Assist — Windows Focus Assist (Do Not Disturb) blocks notifications. Check Settings → System → Focus Assist, or click the notification icon in the system tray.

7. VTE-based terminals (GNOME Terminal, Tilix) — OSC 777 support requires Fedora's VTE patches or manual configuration. On Ubuntu/Arch, add to your ~/.bashrc or ~/.zshrc:

   if [ "$VTE_VERSION" ]; then
       source /etc/profile.d/vte.sh 2>/dev/null
   fi

8. tmux passthrough — OSC sequences require tmux 3.2+ with passthrough enabled:

   # Add to ~/.tmux.conf
   set -g allow-passthrough on

   Run tnotify --diagnose inside tmux to check if passthrough is configured.

• Solo - All-in-one Laravel command for local development
• Screen - Pure PHP terminal renderer
• Dumps - Laravel command to intercept dumps
• Grapheme - Unicode grapheme width calculator
• Notify - PHP package for desktop notifications via OSC escape sequences
• Notify Laravel - Laravel integration for soloterm/notify
• VTail - Vendor-aware tail for Laravel logs

MIT