Claude Code ring bell on any kind of stop without explicitly enabling alarms

Open
#56 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
shell, typescript
Domain
cli

Research direction

The issue names no files or tests. Start by locating the existing alarm and notification handling in the TypeScript code, then compare it with the Notification and Stop hook workaround in issue #36850. Done means terminal bells occur for every Claude Code stop without users explicitly enabling alarms.

Written by the indexing model from the issue text.

Description

documentation enhancement

Right now there are two paths to get a notification when Claude Code has stopped for some reason:

  "hooks": {
    "Notification": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "printf '\\a' > /dev/tty 2>/dev/null || true"
          }
        ]
      }
    ],
    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "printf '\\a' > /dev/tty 2>/dev/null || true"
          }
        ]
      }
    ]
  }

Ideally we should work out of the box, and the user shouldn't have to turn anything on at all...

Dominant language
TypeScript
Stars
5
Forks
1
Avg merge
18h 26m
Merged PRs (30d)
229

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from diffplug/dormouse

All issues in diffplug/dormouse

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.