Skip to content

feat(telegram): push notifications for answers + dedupe tool log#42

Merged
arniesaha merged 1 commit intomainfrom
feat/telegram-answer-notification
Apr 24, 2026
Merged

feat(telegram): push notifications for answers + dedupe tool log#42
arniesaha merged 1 commit intomainfrom
feat/telegram-answer-notification

Conversation

@arniesaha
Copy link
Copy Markdown
Owner

Summary

  • Split status bubble (edit-only) from answer bubble (new message → push fires)
  • Collapse consecutive duplicate tool entries as `✅ (×N)`
  • Finalize status bubble to just the tool log at end of turn (or `✅ Done`)

Behavior change

Before: bot edits the "⏳ Thinking..." message in place with the final answer — if the user left the app, no push notification.
After: "⏳ Thinking..." stays as a live status/tool-log bubble; the actual answer is sent as a new message when the model starts producing text, which triggers a Telegram push notification.

Test plan

  • `npx tsc --noEmit` clean
  • Send a message, leave app, confirm push notification arrives for answer
  • Run a browser_control loop, confirm tool log shows `✅ Controlling browser (×N)` not N lines
  • Tool-only turn (no text response) still sends answer as new message
  • Error path still works

🤖 Generated with Claude Code

Split the status bubble (edit-only, holds collapsed tool log) from the
answer bubble (sent as a new message on first text delta, so Telegram
fires a push notification even when the user has left the app). Collapse
consecutive duplicate tool entries to "<label> (×N)".

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@arniesaha arniesaha merged commit 3cca0c8 into main Apr 24, 2026
1 check passed
@arniesaha arniesaha deleted the feat/telegram-answer-notification branch April 24, 2026 02:39
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