Skip to content

fix(telegram): add explicit config switch for voice summaries#1458

Open
anikin-xyz wants to merge 1 commit into
danielmiessler:mainfrom
anikin-xyz:fix/telegram-voice-summary-switch
Open

fix(telegram): add explicit config switch for voice summaries#1458
anikin-xyz wants to merge 1 commit into
danielmiessler:mainfrom
anikin-xyz:fix/telegram-voice-summary-switch

Conversation

@anikin-xyz

Copy link
Copy Markdown

sendVoiceSummary was gated only by the presence of ELEVENLABS_API_KEY. Because the Telegram module and the CLI /notify VoiceServer share that one env var, an install that wants ElevenLabs for the CLI channel but not spoken Telegram notes had no way to turn the latter off short of unsetting the key (which kills both).

This adds a [telegram] voice_summaries flag, threaded through the existing loadPulseConfig → startTelegram → activeConfig path — no new plumbing (loadPulseConfig already passes the whole [telegram] table through). Defaults to enabled (undefined ⇒ on) so existing installs are unchanged; set voice_summaries = false to keep text replies but suppress the voice note. telegramHealth() reflects the switch.

Design note: a dedicated [telegram] flag was chosen over reusing the top-level [voice] enabled because [voice] gates the separate CLI VoiceServer//notify channel — conflating the two surfaces would be wrong.

sendVoiceSummary was gated only by ELEVENLABS_API_KEY presence, so any install
with the key set could not suppress Telegram voice notes without unsetting the
key (which also disables the CLI /notify voice channel that shares it).

Add a [telegram] voice_summaries flag, threaded through the existing
loadPulseConfig → startTelegram → activeConfig path (no new plumbing). Defaults
to enabled (undefined ⇒ on) so existing installs are unchanged; set
voice_summaries = false to keep text replies but suppress voice notes. Health
output reflects the switch.
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.

1 participant