Skip to content

fix(telegram): backtick code spans silently dropped from message content #285

Description

@ptone

Bug Description

When a scion message is sent to a user via Telegram and the content contains backtick-delimited strings (markdown code spans), the text inside the backticks is silently dropped from the rendered message.

Steps to Reproduce

scion message user:ptone@google.com --channel telegram --thread-id 1282 "Started capture-auth-ui-dev to implement \`my-agent-name\`"

Expected Behavior

Telegram should display the full message including the backtick-wrapped text:

Started capture-auth-ui-dev to implement my-agent-name

Actual Behavior

Telegram receives a truncated message with the backtick-wrapped content stripped entirely:

Started capture-auth-ui-dev to implement

Impact

Agent names, command names, and other inline code spans in coordinator/agent status messages are silently stripped. This makes automated status messages ambiguous or misleading — recipients cannot tell which agent or command is being referenced.

Notes

This likely relates to how the Telegram message formatting pipeline handles markdown. Telegram uses its own flavor of markdown (MarkdownV2) which requires special escaping of certain characters including backticks. The issue may be in how the message content is serialized before being sent to the Telegram API.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions