Skip to content

fix: respect notifications.voice.enabled setting (#83)#85

Merged
virtualian merged 1 commit intomainfrom
83-voice-plays-despite-disabled
Mar 10, 2026
Merged

fix: respect notifications.voice.enabled setting (#83)#85
virtualian merged 1 commit intomainfrom
83-voice-plays-despite-disabled

Conversation

@virtualian
Copy link
Copy Markdown
Owner

Summary

  • Voice server now reads notifications.voice.enabled from settings.json at startup and gates all TTS globally — single point of control for ~200 inline curl callers
  • VoiceCompletion hook checks the same setting via existing getSettings() for early exit before HTTP round-trip (belt-and-suspenders)
  • Defaults to enabled when setting is absent (preserves existing behavior)
  • Desktop notifications remain independent of voice toggle

Closes #83

Test plan

  • Voice server /health reports voice_globally_enabled: false when setting is false
  • curl with voice_enabled: true produces no audio when globally disabled
  • Desktop notifications still fire when voice is disabled
  • Verify voice plays normally when notifications.voice.enabled: true

🤖 Generated with Claude Code

…hook (#83)

Voice played despite settings.json having voice.enabled: false because
neither voice source checked the setting. Voice server now reads the
flag at startup and gates TTS globally. VoiceCompletion hook also checks
via existing getSettings() for early exit before HTTP round-trip.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Voice plays despite settings.json voice.enabled: false

1 participant