fix(telegram): silence the progress bubble, stop echoing tool output, add a...
Open Source Local First Ai Agent
Brought to you by:
sosidudku
Originally created by: sosidudku1
Follow-up to [#28], which merged without the changes requested in review. Closes [#58]. Everything below was asked for in the review thread; nothing else changed behavior.
disable_notification: true. Every owner message no longer produces two push notifications (one for the Thinking bubble, one for the reply).step_finished no longer echoes the tool-output tail. progressLabel now builds every label from stable identifiers only (✅ Step N done), so a file path, a grep hit or a key fragment can never reach forwardable Telegram history. This was the privacy concern raised in review.retry_after window. Bubble edits can no longer earn a chat-wide flood-wait that would delay or drop the final reply.telegram.progressIndicator config flag (default true) as the production kill switch, plumbed the same way parseMode was (schema defaults, telegram-settings.ts, InboundContext, captured at handler registration). Config v33 → v34; older files transparently inherit true.TelegramProgressIndicator + progressLabel move to telegram-progress-indicator.ts per the 300-line file guideline; inbound-handler.ts drops back under it.FakeApi in inbound-handler.test.ts now records editMessageText and deleteMessage, so indicator calls stop silently no-oping under test.telegram-progress-indicator.test.ts: lifecycle happy path, silent send, the fast-turn race (remove before the initial send resolves deletes the just-posted message), throttle + identical-text dedup, 429 mute, failure isolation, and a regression test asserting summaries are not echoed.progressIndicator: false suppresses it entirely.false, and a v33 file inheriting true transparently.src/channels/telegram: 139 passed. src/config: 136 passed. tsc --noEmit clean. Full suite: same pre-existing failures as main (six of them documented in [#50]; verified by running the identical file set on a clean checkout).This PR and [#52]'s fix both bump USER_CONFIG_VERSION 33 → 34 for their own field. Whichever merges second gets a trivial rebase to 35.
Ticket changed by: Ooooze