[Bug] Tool use notifications triggered for all invocations instead of input-only

Found 1 possible duplicate issue:

1. https://github.com/anthropics/claude-code/issues/12048

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

same issue here. Version: 2.0.53

Not a duplicate, real bug. v2.0.53 spams me with alerts on every tool use. macOS / iTerm.

yep, crazy things

Same here. Claude Code 2.0.53, macOS, Kitty terminal.

Feature: Notification Filtering

Good UX improvement request. Here's how to implement it.

Problem

Noisy notifications:

• Background bash reminders (every tool call)
• MCP server connection status
• Hook execution notices
• Auto-save confirmations

Impact: Clutters output, wastes tokens

Proposed Solution

Add notification levels:

// ~/.claude/config.json
{
  "notifications": {
    "level": "important",  // "all" | "important" | "errors" | "none"
    "filters": {
      "background_bash": false,  // Hide bash reminders
      "mcp_status": false,       // Hide MCP connection msgs
      "auto_save": false,        // Hide auto-save notices
      "hooks": true              // Show hook execution
    }
  }
}

Implementation:

// src/notifications/NotificationManager.ts

enum NotificationLevel {
  DEBUG = 0,
  INFO = 1,
  IMPORTANT = 2,
  ERROR = 3
}

class NotificationManager {
  private config: NotificationConfig;
  
  shouldShow(notification: Notification): boolean {
    // Check level
    if (notification.level < this.config.level) {
      return false;
    }
    
    // Check filters
    if (this.config.filters[notification.category] === false) {
      return false;
    }
    
    return true;
  }
  
  emit(notification: Notification) {
    if (this.shouldShow(notification)) {
      this.display(notification);
    }
  }
}

Categorize existing notifications:

// Background bash reminder
notification({
  category: 'background_bash',
  level: NotificationLevel.INFO,
  message: 'Background bash has new output'
});

// Error
notification({
  category: 'error',
  level: NotificationLevel.ERROR,
  message: 'Failed to connect to API'
});

UI Controls

Interactive toggle:

> /notifications

Current level: important
Filters:
  ○ background_bash (hidden)
  ○ mcp_status (hidden)  
  ● hooks (shown)
  ● errors (shown)

Change level: /notifications set <level>
Toggle filter: /notifications toggle <category>

Slash commands:

> /notifications set errors
✓ Only showing errors

> /notifications toggle background_bash
✓ Background bash notifications enabled

> /notifications reset
✓ Reset to defaults

Smart Defaults

During active development:

{
  "level": "info",  // Show most things
  "filters": { "background_bash": true }
}

During long-running sessions:

{
  "level": "important",  // Less noise
  "filters": { "background_bash": false }
}

During debugging:

{
  "level": "debug",  // Show everything
  "filters": {}  // No filtering
}

Alternative: Collapse Repeated Notifications

Instead of:

Background Bash 46410c has new output
Background Bash 46410c has new output
Background Bash 46410c has new output

Show:

Background Bash 46410c has new output (×3)
[Click to expand]

---

Verdict: Medium priority UX improvement.
Recommend: Implement notification levels first, filters later.

Please fix this, it's driving me insane

I had to disable alerts in iTerm settings (Profile -> Terminal -> Notification Center Alerts).

Same issue here. Version 2.0.53 on macOS with iTerm2 - getting bombarded with notifications after every single tool use. This is extremely annoying and makes the notification system useless since I can't distinguish between actual user input requests and normal command completions.

The alert fatigue is real - I've had to disable all notifications just to get work done. Would be great to have this fixed ASAP.

Agree with @LuisHansen - please prioritize this!

Disabling notifications of course fixes the constant beeping, but we also lose the whole 'the agent is done and needs your input' flow.

That's better than alert storm. I run two or three agents in different tabs in parallel. What a mess!

We're actively investigating right now

I think I have the same issue as this. Although the notifications are strange they look like "4;0;0" or "4;3;0".

I'm using 2.0.53 with Kitty terminal on linux.

We've just pushed a new build v2.0.54 with a fix for this! Sorry for the inconvenience

I'm using 2.0.54, but still too many notifications are issued from Claude Code.

@gfx can u add details about your terminal and maybe a screenshot?

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.