[FEATURE] Configurable notification preferences for neurodivergent users and accessibility

[FEATURE] Configurable notification preferences for neurodivergent users and accessibility

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code currently uses system beeps/terminal bell notifications to get user attention. While well-intentioned, this creates significant accessibility barriers for neurodivergent users, particularly those with:

• Auditory sensitivities (common in autism, ADHD, sensory processing disorders)
• Misophonia (specific sound sensitivities)
• Anxiety disorders where unexpected sounds trigger stress responses
• Audio processing differences where sound notifications are distracting or overwhelming

The current implementation:

1. Uses audible beeps that cannot be customized or disabled within Claude Code
2. Provides no alternative notification methods for users who need them
3. Forces users to choose between:

• Tolerating potentially distressing auditory notifications
• Disabling ALL terminal notifications system-wide (affecting other tools)
• Not using Claude Code at all

This is an inclusion and accessibility issue, not just a preference. For many neurodivergent users, unexpected or repetitive sounds can:

• Break focus and concentration
• Cause physical discomfort or pain
• Trigger anxiety or stress responses
• Make the tool unusable for extended periods

Proposed Solution

Add configurable notification preferences that respect diverse user needs:

Configuration Options

{
  "notifications": {
    "enabled": true,  // Master toggle
    "types": {
      "user_input_needed": {
        "enabled": true,
        "method": "visual"  // "audio", "visual", "both", "none"
      },
      "task_complete": {
        "enabled": true,
        "method": "visual"
      },
      "error": {
        "enabled": true,
        "method": "both"
      }
    },
    "audio": {
      "bell_character": false,  // Disable terminal bell \x07
      "custom_sound": null,     // Path to custom sound file (gentler options)
      "volume": 50              // If audio is used
    },
    "visual": {
      "status_line_indicator": true,   // Show in status line
      "color_change": true,             // Change prompt/status color
      "text_notification": true         // Print text message
    }
  }
}

Alternative Notification Methods

1. Visual indicators:

• Status line changes (color, icon, text)
• Terminal title updates
• Prompt modifications

1. Configurable audio:

• Option to disable bell entirely
• Custom sound file support (users can choose gentle/preferred sounds)
• Volume control

1. Per-event customization:

• Different notification methods for different events
• Priority levels (critical vs. informational)

Alternative Solutions

If full configuration is too complex initially, even basic options would help:

1. Minimal: Simple --no-bell flag or notifications.bell: false setting
2. Basic: Choose between "audio", "visual", or "both"
3. Ideal: Full configuration as described above

Priority

High - Affects accessibility and inclusion

Feature Category

• Accessibility
• CLI commands and flags
• Settings and configuration

Use Case Example

Scenario 1: Autistic user with auditory sensitivity

# In settings.json
{
  "notifications": {
    "audio": { "bell_character": false },
    "visual": { "status_line_indicator": true }
  }
}

User receives clear visual notifications without distressing sounds.

Scenario 2: ADHD user who needs certain sounds but not others

{
  "notifications": {
    "types": {
      "user_input_needed": { "method": "both" },  // Important: keep audio
      "task_complete": { "method": "visual" }      // Less critical: visual only
    }
  }
}

User gets audio alerts for critical interactions but avoids notification fatigue.

Scenario 3: User with misophonia

{
  "notifications": {
    "audio": {
      "bell_character": false,
      "custom_sound": "~/gentle-chime.wav"  // User-selected tolerable sound
    }
  }
}

User replaces harsh bell with a sound they've identified as comfortable.

Additional Context

Related Issues

• #12046 (Option to disable notifications)
• #7121 (Excessive terminal BEL)
• #12438 (Bell notification issues)

Accessibility Standards

This aligns with:

• WCAG 2.1 (Web Content Accessibility Guidelines) principle of perceivable information
• Universal Design principles of flexibility in use
• Neurodiversity inclusion best practices

Impact

Making this change would:

• Enable neurodivergent developers to use Claude Code comfortably
• Demonstrate Anthropic's commitment to inclusion and accessibility
• Set a positive example for AI tooling accessibility
• Potentially help other users who work in shared spaces or have different preferences

Community Need

The existing issues show this affects multiple users, and the neurodivergent developer community is substantial. Making AI tools accessible isn't just good practice—it's essential for ensuring equitable access to these powerful technologies.

---

Thank you for considering this feature request. Accessible, inclusive tools benefit everyone.