fix(markdown): require paired || delimiters for spoiler detection by Sid-Qin · Pull Request #26105 · openclaw/openclaw

Sid-Qin · 2026-02-25T04:28:31Z

Summary

Problem: Telegram renders single | pipe characters (e.g., emoticons like (￣_￣|)) and unpaired || as spoiler/hidden text, hiding subsequent message content
Why it matters: Users see garbled messages with unexpectedly hidden text in Telegram
What changed: Added a pre-scan in injectSpoilersIntoInline (src/markdown/ir.ts) that counts all || delimiters across an inline token group; if the count is odd or < 2, spoiler injection is skipped entirely. Handles cross-token || pairs correctly (e.g., ||**bold**||)
What did NOT change: Properly paired ||spoiler|| syntax continues to work as expected

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Closes [Bug]: Telegram channel incorrectly treats "|" pipe character as spoiler/hidden text #26068

User-visible / Behavior Changes

Single | and unpaired || in messages are now rendered as plain text in Telegram instead of being incorrectly treated as spoiler markers.

Security Impact (required)

New permissions/capabilities? No
Secrets/tokens handling changed? No
New/changed network calls? No
Command/tool execution surface changed? No
Data access scope changed? No

Repro + Verification

Environment

Integration/channel: Telegram

Steps

Send a message containing (￣_￣|) face or before || after to the bot
View the message in Telegram client

Expected

| and unpaired || display as plain text

Actual (before fix)

Text after | appears as spoiler (gray hidden block)

Evidence

Failing test/log before + passing after
New test: single pipe (￣_￣|) not treated as spoiler
New test: unpaired before || after not treated as spoiler
Existing tests: paired ||spoiler|| and ||**bold**|| still render correctly
All 69 markdown/telegram format tests pass

Human Verification (required)

Verified scenarios: single pipe, unpaired ||, paired ||, nested formatting inside spoilers
Edge cases checked: odd delimiter count, cross-token delimiter pairs, empty inline groups
What you did not verify: live Telegram bot end-to-end (unit tests only)

Compatibility / Migration

Backward compatible? Yes
Config/env changes? No
Migration needed? No

Failure Recovery (if this breaks)

How to disable/revert this change quickly: Revert the single commit afc7168
Files/config to restore: src/markdown/ir.ts
Known bad symptoms reviewers should watch for: Legitimate ||spoiler|| syntax no longer rendering as spoilers

Risks and Mitigations

Risk: Edge case where || delimiters are split across inline groups in unusual markdown structures
- Mitigation: Pre-scan counts across all text tokens within the same inline group; tested with nested formatting

An unpaired || (odd count across all inline tokens) would open a spoiler that never closes, causing closeRemainingStyles to extend it to the end of the text. This made all content after an unpaired || appear as hidden/spoiler in Telegram. Pre-count || delimiters across the entire inline token group and skip spoiler injection entirely when the count is less than 2 or odd. This prevents single | characters and unpaired || from triggering spoiler formatting. Closes openclaw#26068 Co-authored-by: Cursor <cursoragent@cursor.com>

@Sid-Qin

…penclaw#26105) (thanks @Sid-Qin)

steipete · 2026-02-25T04:54:57Z

Landed via temp rebase onto main.

Gate: pnpm test src/telegram/format.test.ts && pnpm check
Land commit: 2c84a2a
Merge commit: 2e84017

Thanks @Sid-Qin!

@Sid-Qin

…enclaw#26105) * fix(markdown): require paired || delimiters for spoiler detection An unpaired || (odd count across all inline tokens) would open a spoiler that never closes, causing closeRemainingStyles to extend it to the end of the text. This made all content after an unpaired || appear as hidden/spoiler in Telegram. Pre-count || delimiters across the entire inline token group and skip spoiler injection entirely when the count is less than 2 or odd. This prevents single | characters and unpaired || from triggering spoiler formatting. Closes openclaw#26068 Co-authored-by: Cursor <cursoragent@cursor.com> * fix: preserve valid spoiler pairs with trailing unmatched delimiters (openclaw#26105) (thanks @Sid-Qin) --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Peter Steinberger <steipete@gmail.com>

@Sid-Qin

…enclaw#26105) * fix(markdown): require paired || delimiters for spoiler detection An unpaired || (odd count across all inline tokens) would open a spoiler that never closes, causing closeRemainingStyles to extend it to the end of the text. This made all content after an unpaired || appear as hidden/spoiler in Telegram. Pre-count || delimiters across the entire inline token group and skip spoiler injection entirely when the count is less than 2 or odd. This prevents single | characters and unpaired || from triggering spoiler formatting. Closes openclaw#26068 Co-authored-by: Cursor <cursoragent@cursor.com> * fix: preserve valid spoiler pairs with trailing unmatched delimiters (openclaw#26105) (thanks @Sid-Qin) --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Peter Steinberger <steipete@gmail.com>

@Sid-Qin

…enclaw#26105) * fix(markdown): require paired || delimiters for spoiler detection An unpaired || (odd count across all inline tokens) would open a spoiler that never closes, causing closeRemainingStyles to extend it to the end of the text. This made all content after an unpaired || appear as hidden/spoiler in Telegram. Pre-count || delimiters across the entire inline token group and skip spoiler injection entirely when the count is less than 2 or odd. This prevents single | characters and unpaired || from triggering spoiler formatting. Closes openclaw#26068 Co-authored-by: Cursor <cursoragent@cursor.com> * fix: preserve valid spoiler pairs with trailing unmatched delimiters (openclaw#26105) (thanks @Sid-Qin) --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Peter Steinberger <steipete@gmail.com>

@Sid-Qin

…enclaw#26105) * fix(markdown): require paired || delimiters for spoiler detection An unpaired || (odd count across all inline tokens) would open a spoiler that never closes, causing closeRemainingStyles to extend it to the end of the text. This made all content after an unpaired || appear as hidden/spoiler in Telegram. Pre-count || delimiters across the entire inline token group and skip spoiler injection entirely when the count is less than 2 or odd. This prevents single | characters and unpaired || from triggering spoiler formatting. Closes openclaw#26068 Co-authored-by: Cursor <cursoragent@cursor.com> * fix: preserve valid spoiler pairs with trailing unmatched delimiters (openclaw#26105) (thanks @Sid-Qin) --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Peter Steinberger <steipete@gmail.com>

@Sid-Qin

…enclaw#26105) * fix(markdown): require paired || delimiters for spoiler detection An unpaired || (odd count across all inline tokens) would open a spoiler that never closes, causing closeRemainingStyles to extend it to the end of the text. This made all content after an unpaired || appear as hidden/spoiler in Telegram. Pre-count || delimiters across the entire inline token group and skip spoiler injection entirely when the count is less than 2 or odd. This prevents single | characters and unpaired || from triggering spoiler formatting. Closes openclaw#26068 Co-authored-by: Cursor <cursoragent@cursor.com> * fix: preserve valid spoiler pairs with trailing unmatched delimiters (openclaw#26105) (thanks @Sid-Qin) --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Peter Steinberger <steipete@gmail.com>

@Sid-Qin

…enclaw#26105) * fix(markdown): require paired || delimiters for spoiler detection An unpaired || (odd count across all inline tokens) would open a spoiler that never closes, causing closeRemainingStyles to extend it to the end of the text. This made all content after an unpaired || appear as hidden/spoiler in Telegram. Pre-count || delimiters across the entire inline token group and skip spoiler injection entirely when the count is less than 2 or odd. This prevents single | characters and unpaired || from triggering spoiler formatting. Closes openclaw#26068 Co-authored-by: Cursor <cursoragent@cursor.com> * fix: preserve valid spoiler pairs with trailing unmatched delimiters (openclaw#26105) (thanks @Sid-Qin) --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Peter Steinberger <steipete@gmail.com>

@Sid-Qin

…enclaw#26105) * fix(markdown): require paired || delimiters for spoiler detection An unpaired || (odd count across all inline tokens) would open a spoiler that never closes, causing closeRemainingStyles to extend it to the end of the text. This made all content after an unpaired || appear as hidden/spoiler in Telegram. Pre-count || delimiters across the entire inline token group and skip spoiler injection entirely when the count is less than 2 or odd. This prevents single | characters and unpaired || from triggering spoiler formatting. Closes openclaw#26068 Co-authored-by: Cursor <cursoragent@cursor.com> * fix: preserve valid spoiler pairs with trailing unmatched delimiters (openclaw#26105) (thanks @Sid-Qin) --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Peter Steinberger <steipete@gmail.com>

openclaw-barnacle bot added channel: telegram Channel integration: telegram size: XS experienced-contributor labels Feb 25, 2026

SidQin-cyber and others added 2 commits February 25, 2026 04:53

fix: preserve valid spoiler pairs with trailing unmatched delimiters (o…

2c84a2a

…penclaw#26105) (thanks @Sid-Qin)

steipete force-pushed the fix/telegram-spoiler-pipe-26068 branch from afc7168 to 2c84a2a Compare February 25, 2026 04:54

steipete merged commit 2e84017 into openclaw:main Feb 25, 2026
9 checks passed

github-actions bot mentioned this pull request Feb 25, 2026

📡 Upstream Digest — 2026-02-25 06:54 UTC curtismercier/openclaw-mods#122

Open

arjunaskykok mentioned this pull request Feb 26, 2026

fix/test a2ui bundle preflight #27345

Open

2 tasks

Takhoffman mentioned this pull request Mar 7, 2026

telegram: treat unmatched || as plain text in markdown formatter #26090

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(markdown): require paired || delimiters for spoiler detection#26105

fix(markdown): require paired || delimiters for spoiler detection#26105
steipete merged 2 commits intoopenclaw:mainfrom
Sid-Qin:fix/telegram-spoiler-pipe-26068

Sid-Qin commented Feb 25, 2026 •

edited

Loading

Uh oh!

Uh oh!

steipete commented Feb 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

Sid-Qin commented Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

User-visible / Behavior Changes

Security Impact (required)

Repro + Verification

Environment

Steps

Expected

Actual (before fix)

Evidence

Human Verification (required)

Compatibility / Migration

Failure Recovery (if this breaks)

Risks and Mitigations

Uh oh!

Uh oh!

steipete commented Feb 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Sid-Qin commented Feb 25, 2026 •

edited

Loading