Skip to main content
Glama
nkyy

Claude Code Notification Hooks

by nkyy
README.md
# šŸ”” Claude Code Notification Hooks

> **āš ļø DEPRECATED**: This project has been superseded by [cat-ccnotify-hook](https://github.com/nkygit/cat-ccnotify-hook). Please use the new standalone package for better performance and easier installation.

Enhanced Claude Code experience with automatic desktop notifications and contextual sounds for all events. No manual notification calls needed - works automatically with all Claude Code operations!

## ✨ Features

- šŸ”” **Automatic Notifications**: Intercepts ALL Claude Code notifications and enhances them
- šŸŽµ **Contextual Sounds**: Different sounds for success, error, warning, and other event types
- šŸš€ **Zero Configuration**: Automatic detection and enhancement of notification types
- šŸ“‹ **Smart Sound Mapping**: Intelligent analysis of notification content for appropriate sounds
- šŸ–±ļø **Native System Integration**: Uses macOS/Windows/Linux native notification systems

## šŸš€ Quick Start

### Method 1: One-Command Setup (Recommended)

Run this in Claude Code:

```bash
cd /path/to/ccnotify && npm run setup-hooks
```

### Method 2: Manual Setup

1. **Clone and build:**
```bash
git clone <this-repository>
cd ccnotify
npm install && npm run build
```

2. **Run setup:**
```bash
npm run setup-hooks
```

3. **Restart Claude Code** if it's currently running

### 3. That's It!

All Claude Code notifications will now automatically have enhanced sounds and styling. No additional configuration needed!

## šŸ“± How It Works

The notification hook automatically detects and enhances all Claude Code notifications:

### Automatic Sound Assignment
- āœ… **Success/Completion** → Glass sound (macOS)
- 🚨 **Errors/Failures** → Basso sound (macOS)  
- āš ļø **Warnings/Attention** → Sosumi sound (macOS)
- šŸ’” **Info/Updates** → Blow sound (macOS)
- ā³ **Progress/Ongoing** → Tink sound (macOS)

### Examples in Action
```bash
# Building a project
npm run build
# → Automatic success notification with Glass sound when complete
# → Automatic error notification with Basso sound if failed

# Running tests  
npm test
# → Automatic progress notification with Tink sound while running
# → Automatic completion notification when finished

# Git operations
git push origin main
# → Automatic notifications for each step with appropriate sounds
```

## šŸŽµ Available Sounds

| Sound | Use Case | macOS Sound |
|-------|----------|-------------|
| `success` | Task completion, success | Glass |
| `error` | Errors, failures | Basso |
| `warning` | Warnings, attention needed | Sosumi |
| `info` | Information, status updates | Blow |
| `progress` | Progress updates, ongoing work | Tink |
| `reminder` | Reminders, prompts | Ping |
| `default` | System default notification sound | - |
| `silent` | No sound | - |

## šŸ› ļø Advanced Configuration

### Customizing Sound Mappings

Edit the hook script at `hooks/notification-hook.js` to customize sound mappings:

```javascript
// Example: Add custom sound rules
const customSoundRules = [
  { pattern: /deployment/i, sound: 'Ping' },
  { pattern: /security/i, sound: 'Funk' },
  { pattern: /backup/i, sound: 'Purr' }
];
```

### Troubleshooting

**Hook not working?**
```bash
# Check if hook is properly installed
cat ~/.config/claude-code/settings.json | grep -A 10 "hooks"

# Verify hook script is executable
ls -la hooks/notification-hook.js

# Re-run setup if needed
npm run setup-hooks
```

**Sounds not playing?**
```bash
# Test system sound (macOS)
afplay /System/Library/Sounds/Glass.aiff

# Check notification permissions in System Preferences
```

## šŸŒ Real-World Examples

### Automatic Enhancement Examples

**Claude Code Operations** → **Enhanced Notifications**

```bash
# File operations
"Create a new React component"
→ āœ… "Component created successfully" + Glass sound

# Build processes  
"Run the build process"
→ ā³ "Build in progress..." + Tink sound
→ āœ… "Build completed successfully" + Glass sound

# Error scenarios
"Fix the TypeScript errors"
→ 🚨 "3 type errors found" + Basso sound

# Git operations
"Commit these changes"
→ āœ… "Changes committed successfully" + Glass sound
```

## šŸ”§ Development

### Development Commands
```bash
npm run dev    # Development mode with auto-reload
npm run build  # Production build
npm start      # Start production server
```

### Platform Support
- **macOS**: Full native support with `osascript` and system sounds
- **Windows/Linux**: Cross-platform support via `node-notifier` package

### Architecture
- Type-safe TypeScript implementation
- MCP (Model Context Protocol) compliant
- Automatic platform-specific implementation switching
- Extensible notification type system

## šŸ“‹ Technical Details

### Hook Architecture

The notification hook intercepts Claude Code's notification system and enhances it:

1. **Interception**: Hook receives all notification calls from Claude Code
2. **Analysis**: Analyzes notification content using pattern matching
3. **Enhancement**: Adds appropriate sounds and styling based on content
4. **Native Integration**: Uses platform-specific notification APIs

### Installation Structure

```
~/.config/claude-code/settings.json  # Claude Code configuration
hooks/notification-hook.js            # Main hook script  
dist/index.js                        # Built MCP server (optional)
scripts/setup-hooks.js               # Automated setup script
```

### Platform Support
- **macOS**: Full native support with `osascript` and system sounds
- **Windows/Linux**: Cross-platform support via `node-notifier` package

### Legacy MCP Server (Optional)

For advanced users who want manual notification control, the MCP server is still available:

```json
{
  "mcpServers": {
    "ccnotify": {
      "command": "node",
      "args": ["/absolute/path/to/ccnotify/dist/index.js"]
    }
  }
}
```

## šŸ¤ Contributing

Bug reports and feature requests are welcome! Please open an [issue](../../issues).

## šŸ“„ License

MIT License

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation3/5

The tools have overlapping purposes despite different names, as all are notification tools with specific triggers. The descriptions help differentiate contexts (errors, task completion, user actions, general auto-notification), but the boundaries are somewhat fuzzy, especially between auto_notify_if_appropriate and the more specific tools. An agent might struggle to choose between them in ambiguous situations.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern (e.g., send_error_notification, send_task_complete_notification), with all tools using snake_case. The only deviation is auto_notify_if_appropriate, which uses a slightly different verb style ('auto_notify' vs. 'send'), but overall, the naming is predictable and readable.

Tool Count5/5

With 4 tools, the count is well-scoped for a notification server. Each tool serves a distinct notification type (errors, task completion, user actions, general auto-notification), and there are no unnecessary redundancies. This number allows for focused coverage without being overwhelming or too sparse.

Completeness5/5

The tool set comprehensively covers the notification domain for code-related contexts. It includes notifications for errors, task completions, user actions, and general auto-notification, ensuring no gaps in common scenarios like failures, successes, or required interactions. This provides a complete lifecycle of notification needs without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues