[BUG] Stop hooks not executing after responses despite proper configuration
Resolved 💬 3 comments Opened Sep 1, 2025 by PeterJBurke Closed Sep 5, 2025
Environment
- Platform (select one):
- [ ] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [x ] Other: <!-- specify --> Claude Code
- Claude CLI version: <!-- output of
claude --version--> - Operating System: <!-- e.g. macOS 14.3, Windows 11, Ubuntu 22.04 -->
- Terminal: <!-- e.g. iTerm2, Terminal App -->
Linux Mint 22 Bash
Title: Stop hooks not executing after responses despite proper configuration
Description:
- Expected: Stop hook should run after every Claude response per .claude/claude.json configuration
- Actual: Hook only runs sporadically/not at all during conversation
- Configuration: Stop hook properly configured with --notify flag in claude.json
- Evidence: Debug file shows hook ran at 12:34 but no entries for subsequent responses
- Impact: TTS notifications and logging features are broken
Steps to reproduce:
- Configure Stop hook in .claude/claude.json with --notify flag
- Have conversation with Claude
- Check if hook runs after each response (it doesn't)
This appears to be a core hook execution issue affecting the fundamental hook system functionality.
Additional Context
<!-- Add any other context about the problem here, such as screenshots, logs, etc. -->
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗