Claude Code ring bell on any kind of stop without explicitly enabling alarms
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 0
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 216
Description
Right now there are two paths to get a notification when Claude Code has stopped for some reason:
- explicitly turn on the alarm which is looking for visual changes
- follow the workaround in https://github.com/anthropics/claude-code/issues/36850 to send terminal bells on stop
```json
"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...
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
- Tech stack
- shell, typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100