Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix Telegram formatter drops spacing before numbered section after bullet block [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#76998•Fetched 2026-05-04 04:59:36
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Author
evgyurevgyur
Participants
clawsweeper[bot]clawsweeper[bot]evgyurevgyur
Timeline (top)
cross-referenced ×2commented ×1

Telegram replies can lose the blank line between a manually-indented bullet block and the next numbered section. This makes long planning/status messages hard to scan in Telegram.

Root Cause

This looks related to list/paragraph preservation work in #74474, but that fix does not cover this Telegram boundary case. It is also adjacent to #10944 because Telegram HTML output is sensitive to newline preservation around list-like text.

Fix Action

Fixed

PR fix notes

PR #76999: fix(telegram): preserve spacing before numbered sections

Description (problem / solution / changelog)

Summary

  • Preserve a blank line when Telegram markdown-ish output transitions from a bullet block to a following numbered section or heading.
  • Apply the normalization before Telegram markdown IR rendering, including chunked rendering.
  • Add regression coverage for the observed numbered-section boundary and for fenced code blocks.

Fixes #76998.

Test

  • pnpm exec vitest run extensions/telegram/src/format.test.ts

Changed files

  • extensions/telegram/src/format.test.ts (modified, +27/-0)
  • extensions/telegram/src/format.ts (modified, +41/-2)

Code Example

2. Main invariants:

  • Raw Log is source of truth.
  • Autonomy starts only with report/draft.
3. Cognee is a candidate:

  • bake-off first;
  • decide keep/adopt/hybrid later.
4. Project Flow slices:

---

• Autonomy starts only with report/draft.
3. Cognee is a candidate:

---

• Autonomy starts only with report/draft.

3. Cognee is a candidate:
RAW_BUFFERClick to expand / collapse

Summary

Telegram replies can lose the blank line between a manually-indented bullet block and the next numbered section. This makes long planning/status messages hard to scan in Telegram.

Repro

Observed in a live Telegram message from @chipsclawbot on OpenClaw 2026.5.3-beta.2.

Input shape:

2. Main invariants:

  • Raw Log is source of truth.
  • Autonomy starts only with report/draft.
3. Cognee is a candidate:

  • bake-off first;
  • decide keep/adopt/hybrid later.
4. Project Flow slices:

Actual Telegram text stores/renders the next numbered section immediately after the last bullet:

  • Autonomy starts only with report/draft.
3. Cognee is a candidate:

Expected:

  • Autonomy starts only with report/draft.

3. Cognee is a candidate:

Notes

This looks related to list/paragraph preservation work in #74474, but that fix does not cover this Telegram boundary case. It is also adjacent to #10944 because Telegram HTML output is sensitive to newline preservation around list-like text.

extent analysis

TL;DR

The issue can be fixed by ensuring that a blank line is preserved between a manually-indented bullet block and the next numbered section in Telegram messages.

Guidance

  • Verify that the input shape has a blank line between the bullet block and the next numbered section.
  • Check if the list/paragraph preservation work in #74474 can be extended to cover this Telegram boundary case.
  • Investigate if the Telegram HTML output can be modified to preserve newlines around list-like text, as mentioned in #10944.
  • Test the rendering of the message in Telegram with different input shapes to identify the exact cause of the issue.

Example

No code snippet is provided as the issue is related to text rendering in Telegram and not a specific code implementation.

Notes

The fix may require modifications to the Telegram message rendering logic or the preservation of newlines in the input text. The issue is specific to the Telegram platform and may not be applicable to other messaging platforms.

Recommendation

Apply workaround: Modify the input shape to include a blank line between the bullet block and the next numbered section to ensure proper rendering in Telegram. This is a temporary solution until a more permanent fix can be implemented.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#dependency conflict#environment setup#docker error#permission error#memory optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix Telegram formatter drops spacing before numbered section after bullet block [1 pull requests, 1 comments, 2 participants]