clawverse/apress
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(onboard): ship telegram disabled so a tokenless channel can't spam probes

Browse Source 
A tokenless [channels.telegram.default] with enabled=true starts the Telegram
channel anyway; its getUpdates startup probe fails every 5s ("Startup probe:
API error : ; retrying in 5s") and that WARN leaks into the Module 2 chat via
the node activity feed. Ship enabled=false; the setup wizard flips it on with a
real bot_token when a team opts in (api/src/nodes.ts configureTelegram).

Co-Authored-By: Claude Opus 4.8 <[email protected]>
This commit is contained in:
Omar Sobh
2026-07-22 18:25:23 -07:00
co-authored by Claude Opus 4.8
parent 4622f8c409
commit 107e5b0955
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/uno-q/onboard-app/config.toml
+5 -1
View File
@@ -383,7 +383,11 @@ transcription_provider = ""
tts_provider = ""
[channels.telegram.default]
enabled = true
# Ships DISABLED: a tokenless channel would fail its getUpdates startup probe
# every 5s ("Startup probe: API error"), and that noise leaks into the module
# chat. The Telegram setup wizard flips this to enabled + a real bot_token when
# a team opts in (see api/src/nodes.ts configureTelegram).
enabled = false
bot_token = ""
api_base_url = "https://api.telegram.org"
approval_timeout_secs = 120