Telegram: response formatting concatenates URLs with following text #974

Closed
opened 2026-10-27 13:38:31 +00:00 by sam · 0 comments
Owner

Problem

Telegram responses can concatenate a bare URL with the sentence that follows it, which breaks the clickable/direct link and makes the message look malformed.

This has occurred at least twice. Example:

https://github.com/samcharles93/archie-core/issues/513It includes model-independent safeguards...

The expected output is:

https://github.com/samcharles93/archie-core/issues/513

It includes model-independent safeguards...

Desired behavior

  • Preserve paragraph/newline boundaries between links and subsequent text.
  • Ensure a bare URL remains independently clickable in Telegram.
  • Do not concatenate separately streamed/rendered response segments.
  • Apply the fix consistently whether the response is sent once, edited while streaming, or split into multiple Telegram messages.

Acceptance criteria

  • A URL followed by prose is rendered with at least one newline separating them.
  • Bare GitHub issue URLs remain clickable and contain no trailing prose.
  • Regression coverage includes the exact example above.
  • Coverage exercises the relevant Telegram streaming/editing and message-splitting paths.

Close reason

Fixed Telegram URL/prose boundary normalization across one-shot, live, and split delivery paths; added Markdown/code safety, newline preservation, and regression coverage.


Imported from beads archie-core-1786748942566-19-aa1c4552 · GitHub #514 · type bug · priority P2 · created 2026-08-14 · closed 2026-08-15

## Problem Telegram responses can concatenate a bare URL with the sentence that follows it, which breaks the clickable/direct link and makes the message look malformed. This has occurred at least twice. Example: ```text https://github.com/samcharles93/archie-core/issues/513It includes model-independent safeguards... ``` The expected output is: ```text https://github.com/samcharles93/archie-core/issues/513 It includes model-independent safeguards... ``` ## Desired behavior - Preserve paragraph/newline boundaries between links and subsequent text. - Ensure a bare URL remains independently clickable in Telegram. - Do not concatenate separately streamed/rendered response segments. - Apply the fix consistently whether the response is sent once, edited while streaming, or split into multiple Telegram messages. ## Acceptance criteria - A URL followed by prose is rendered with at least one newline separating them. - Bare GitHub issue URLs remain clickable and contain no trailing prose. - Regression coverage includes the exact example above. - Coverage exercises the relevant Telegram streaming/editing and message-splitting paths. ### Close reason Fixed Telegram URL/prose boundary normalization across one-shot, live, and split delivery paths; added Markdown/code safety, newline preservation, and regression coverage. --- _Imported from beads `archie-core-1786748942566-19-aa1c4552` · GitHub #514 · type bug · priority P2 · created 2026-08-14 · closed 2026-08-15_
sam added the mediumbug labels 2026-10-27 13:38:31 +00:00
sam self-assigned this 2026-10-27 13:38:31 +00:00
sam closed this issue 2026-10-27 13:38:31 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#974