Skip to content

fix(telegram): bound reply context size#226

Closed
Gezi-lzq wants to merge 1 commit into
bubbuild:mainfrom
Gezi-lzq:gezi/telegram-reply-context-truncation
Closed

fix(telegram): bound reply context size#226
Gezi-lzq wants to merge 1 commit into
bubbuild:mainfrom
Gezi-lzq:gezi/telegram-reply-context-truncation

Conversation

@Gezi-lzq

@Gezi-lzq Gezi-lzq commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • truncate quoted Telegram reply text before inserting it into agent context
  • drop replied-message media metadata so large media payloads are not duplicated in reply context
  • add regression coverage for truncation and media stripping

Verification

  • python -m pytest -q tests/test_telegram_reply_context.py

@frostming

Copy link
Copy Markdown
Collaborator
  • drop replied-message media metadata so large media payloads are not duplicated in reply context

Will it be stored elsewhere?

@Gezi-lzq Gezi-lzq closed this Jun 9, 2026
@Gezi-lzq Gezi-lzq deleted the gezi/telegram-reply-context-truncation branch June 9, 2026 01:27
@Gezi-lzq

Gezi-lzq commented Jun 9, 2026

Copy link
Copy Markdown
Contributor Author

Sorry, I encountered a similar issue before going to bed yesterday and complained to bub about it. I didn't expect it to directly submit a PR for me. I shouldn't have given it this permission.

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.

2 participants