feat(telegram): send rich message text by obviyus · Pull Request #92679 · openclaw/openclaw

obviyus · 2026-06-13T13:08:45Z

Summary

Send Telegram text replies and edits with Bot API rich messages, keeping Markdown raw by default.
Replace native draft preview endpoints with real rich send/edit previews.
Add rich-message chunking and sanitizing for Telegram limits, wide tables, surrogate pairs, and text-only media safety.
Migrate retired native draft preview config through Telegram doctor.

Verification

PASS: Telegram focused Vitest suite: send, outbound adapter, draft stream, bot delivery/dispatch/message, config schema, doctor.
PASS: auto-reply chunk regression test.
PASS: tsgo for extensions and core.
PASS: oxfmt, oxlint, bundled channel config metadata check, git diff --check.
Live Bot API proof: sendMessageTelegram sent and deleted messages 31167-31173 for rich chunking, table, and edit cases.
Autoreview: earlier actionable findings were fixed; final rerun was stopped after stalling.

Known gap

Bot-to-bot /status@foremanclawbot probe sent message 31166 but saw no SUT reply in 45s; no local SUT poller was found.

clawsweeper · 2026-06-13T13:10:07Z

Codex review: found issues before merge. Reviewed June 13, 2026, 12:09 PM ET / 16:09 UTC.

Summary
The PR changes Telegram delivery to send and edit text through rich Bot API messages, removes native draft preview support, updates prompt guidance, and adjusts related config migration, docs, tests, and tooling.

PR surface: Source +287, Tests +178, Docs -18, Generated 0, Other -10. Total +437 across 43 files.

Reproducibility: yes. for the merge risks from source inspection: current main uses sendMessage/editMessageText fallbacks and accepts native draft config, while the PR routes sends/previews through rich raw methods and removes those keys. I did not run a live custom apiRoot fallback repro in this read-only review.

Review metrics: 2 noteworthy metrics.

Retired Telegram preview keys: 2 removed. nativeToolProgress and nativeToolProgressAllowFrom are shipped user config keys, so removal needs maintainer-visible upgrade approval.
Telegram text transport families: 3 moved to rich raw calls. Durable sends, text edits, and draft previews now depend on Bot API rich-message support rather than the current send/edit paths.

Stored data model
Persistent data-model change detected: migration/backfill/repair: extensions/telegram/src/doctor-contract.ts, migration/backfill/repair: extensions/telegram/src/doctor.test.ts, serialized state: extensions/telegram/src/draft-stream.ts, unknown-data-model-change: extensions/telegram/src/doctor-contract.ts, unknown-data-model-change: src/config/bundled-channel-config-metadata.generated.ts, vector/embedding metadata: docs/channels/groups.md. Confirm migration or upgrade compatibility proof before merge.

Merge readiness
Overall: 🧂 unranked krab
Proof: 🦞 diamond lobster ✨ media proof bonus
Patch quality: 🧂 unranked krab
Result: blocked by patch quality or review findings.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

Preserve or explicitly document fallback behavior for unsupported rich Bot API roots and custom apiRoot setups.
Resolve the native draft-preview retirement as a maintainer-approved upgrade path or keep a compatibility/deprecation path.

Risk before merge

[P2] Existing custom apiRoot, proxy, or self-hosted Telegram Bot API deployments that support sendMessage/editMessageText but not rich-message endpoints may lose ordinary visible text delivery because the PR does not preserve the current send/edit fallback.
[P1] Existing users who intentionally enabled nativeToolProgress or nativeToolProgressAllowFrom will have those keys removed by doctor and lose native DM draft previews unless maintainers explicitly approve that retirement.
[P1] The PR changes Telegram agent prompt policy toward richer tables and rich Markdown by default, which is a product choice even with positive visual proof.

Maintainer options:

Preserve compatible fallback (recommended)
Keep rich rendering as the preferred path but retry the current sendMessage/editMessageText path when rich raw methods are unavailable on custom or lagging Bot API roots.
Approve the new Telegram API floor
Maintainers can intentionally require Bot API 10.1 rich-message support if the PR documents custom apiRoot and upgrade impact before merge.
Split native draft retirement
Pause or split the native draft-preview config removal if maintainers want rich text delivery reviewed independently from retiring shipped operator config.

Next step before merge

[P2] The protected maintainer label and remaining blockers require choosing an API compatibility floor and native draft-preview upgrade behavior, not a narrow safe automated repair.

Security
Cleared: No concrete security or supply-chain regression was found; the diff does not change dependencies, workflows, permissions, secrets handling, package resolution, or downloaded executable code.

Review findings

[P1] Preserve Telegram sends on non-rich Bot API roots — extensions/telegram/src/send.ts:637-641
[P1] Keep explicit native draft-preview upgrade handling — src/config/zod-schema.providers-core.ts:123-125

Review details

Best possible solution:

Land rich Telegram text only after maintainers either preserve a safe fallback for unsupported rich transports or explicitly approve and document the Bot API 10.1 floor, with native draft-preview retirement accepted as an upgrade decision.

Do we have a high-confidence way to reproduce the issue?

Yes for the merge risks from source inspection: current main uses sendMessage/editMessageText fallbacks and accepts native draft config, while the PR routes sends/previews through rich raw methods and removes those keys. I did not run a live custom apiRoot fallback repro in this read-only review.

Is this the best way to solve the issue?

No as-is. Rich-message support is a strong direction, but the best mergeable solution needs compatible fallback or explicit maintainer approval for the Bot API 10.1 floor and native draft-preview retirement.

Full review comments:

[P1] Preserve Telegram sends on non-rich Bot API roots — extensions/telegram/src/send.ts:637-641
This sends visible text chunks only through raw.sendRichMessage, while current main still supports sendMessage with HTML/plain fallback and documents custom/self-hosted apiRoot values. A root that lacks rich methods can lose normal text replies instead of falling back to the existing transport.
Confidence: 0.9
[P1] Keep explicit native draft-preview upgrade handling — src/config/zod-schema.providers-core.ts:123-125
Replacing the Telegram-specific preview schema with the shared preview schema removes nativeToolProgress and nativeToolProgressAllowFrom while doctor deletes those keys. Existing users who opted into native DM tool-progress drafts need explicit maintainer-approved retirement documentation or a compatibility/deprecation path.
Confidence: 0.86

Overall correctness: patch is incorrect
Overall confidence: 0.88

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against bb71f4625136.

Label changes

Label justifications:

P2: The PR is a bounded Telegram feature with compatibility and delivery risks, not an emergency or urgent live regression.
merge-risk: 🚨 compatibility: The PR removes shipped Telegram native draft-preview config and changes the Bot API capability floor for custom or self-hosted roots.
merge-risk: 🚨 message-delivery: The PR routes visible Telegram text replies and previews through rich raw methods, so unsupported transports could prevent ordinary message delivery.
rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🦞 diamond lobster and patch quality is 🧂 unranked krab.
status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Sufficient (recording): The PR body reports live Bot API send/delete proof, and inspected Mantis video proof visibly shows after-fix Telegram rich rendering, table layout, and text-only media-link behavior.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body reports live Bot API send/delete proof, and inspected Mantis video proof visibly shows after-fix Telegram rich rendering, table layout, and text-only media-link behavior.
proof: 🎥 video: Contributor real behavior proof includes video or recording evidence. The PR body reports live Bot API send/delete proof, and inspected Mantis video proof visibly shows after-fix Telegram rich rendering, table layout, and text-only media-link behavior.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram chat formatting and tables, so Telegram Desktop proof is appropriate and already present.

Evidence reviewed

PR surface:

Source +287, Tests +178, Docs -18, Generated 0, Other -10. Total +437 across 43 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	23	847	560	+287
Tests	16	1072	894	+178
Docs	2	10	28	-18
Config	0	0	0	0
Generated	1	5	5	0
Other	1	49	59	-10
Total	43	1983	1546	+437

What I checked:

Latest PR rich send path: At latest PR head, sendMessageTelegram sends text chunks through api.raw.sendRichMessage and records the operation as sendRichMessage, with no fallback to the current sendMessage path in this code path. (extensions/telegram/src/send.ts:630, ed2c94abe443)
Current main send fallback: Current main sends Telegram text through sendMessage with HTML parse fallback to plain text, so the PR changes existing text-delivery fallback behavior. (extensions/telegram/src/send.ts:650, bb71f4625136)
Latest PR draft preview path: At latest PR head, draft previews send and edit through raw rich methods, extending the rich-method dependency to streaming previews. (extensions/telegram/src/draft-stream.ts:154, ed2c94abe443)
Latest PR config retirement: At latest PR head, Telegram preview config uses the shared preview schema, while doctor removes nativeToolProgress and nativeToolProgressAllowFrom. (src/config/zod-schema.providers-core.ts:123, ed2c94abe443)
Current main native draft config: Current main accepts nativeToolProgress and nativeToolProgressAllowFrom in the Telegram preview schema, confirming the PR removes a shipped config surface. (src/config/zod-schema.providers-core.ts:92, bb71f4625136)
Telegram maintainer note: Maintainer notes require real Telegram proof for transport and streaming changes and identify draft streaming behavior as an intentional review surface. (.agents/maintainer-notes/telegram.md:1)

Likely related people:

obviyus: Authored prior merged Telegram sendMessageDraft private-chat streaming work and appears in the history for the draft-stream behavior this PR retires, beyond simply opening this PR. (role: recent Telegram streaming contributor; confidence: high; commits: 6edb512efaeb, 7cc4258dd592; files: extensions/telegram/src/draft-stream.ts, extensions/telegram/src/bot-message-dispatch.ts)
Cypherm: Commit 6b4c24c added Telegram custom apiRoot support across send/fetch behavior, which is the compatibility surface exposed by rich-method-only delivery. (role: introduced custom apiRoot behavior; confidence: high; commits: 6b4c24c2e55b; files: extensions/telegram/src/send.ts, extensions/telegram/src/fetch.ts)
Alexander Krimm: Commit 7cc4258 added the native DM draft tool-progress behavior and adjacent docs/tests that this PR removes or rewrites. (role: introduced native tool-progress drafts; confidence: medium; commits: 7cc4258dd592; files: extensions/telegram/src/native-tool-progress-draft.ts, extensions/telegram/src/bot-message-dispatch.ts, docs/channels/telegram.md)
OpenCils: Commit 3fe4c19 fixed duplicate messages in DM draft streaming mode, making this history relevant to draft finalization behavior affected by removing native draft previews. (role: adjacent draft-stream contributor; confidence: medium; commits: 3fe4c1930588; files: extensions/telegram/src/draft-stream.ts, extensions/telegram/src/lane-delivery.ts)
steipete: Commit 7fc691a added current-main table-mode propagation coverage, which is adjacent to this PR's rich Telegram table-rendering goal. (role: recent Telegram table-path contributor; confidence: medium; commits: 7fc691a426cb; files: extensions/telegram/src/telegram-outbound.test.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

openclaw-mantis · 2026-06-13T13:45:56Z

Mantis Telegram Desktop Proof

Summary: Mantis captured native Telegram Desktop before/after GIF evidence for rich Telegram message rendering.

Scenario: telegram-desktop-proof
Trigger: pull_request_target
Run: https://github.com/openclaw/openclaw/actions/runs/27467939612
Artifact: https://github.com/openclaw/openclaw/actions/runs/27467939612/artifacts/7611286900
Baseline: pass at 78c66742ab976ba1c1e1676615b792605cbb99fb, expected baseline visual proof captured
Candidate: pass at 5fe5f0e1670dd8e851b0f6f72358031f6db4dcf3, expected candidate visual proof captured
Overall: true

Main screenshot	This PR screenshot

Main	This PR

Motion-trimmed clips:

Raw QA files: https://artifacts.openclaw.ai/mantis/telegram-desktop/pr-92679/run-27467939612-1/index.json

obviyus · 2026-06-13T16:13:42Z

New rich text formatting demo:

rich-text-demo-compressed-15MiB.mp4

obviyus · 2026-06-13T16:15:45Z

Landed via rebase onto main.

Scoped tests: /Users/obviyus/Developer/openclaw/node_modules/.bin/oxfmt --check ..., node scripts/run-vitest.mjs src/agents/cli-runner/helpers.system-prompt.test.ts src/agents/cli-runner/prepare.test.ts src/agents/system-prompt.test.ts, /Users/obviyus/Developer/openclaw/node_modules/.bin/tsgo -p test/tsconfig/tsconfig.test.src.json --incremental --tsBuildInfoFile .artifacts/tsgo-cache/telegram-cli-rich-prompt.tsbuildinfo --declaration false --singleThreaded --checkers 1, git diff --check
CI: PR checks green before merge, including Real behavior proof and agent/channel runtime boundaries
Live proof: HamVerBot on Ted was confirmed to be using the Claude CLI backend; user retested the latest PR behavior before merge
Changelog: not updated; normal PR release notes cover this feature
Land commit before rebase: ed2c94a
Merge commit: 45e36a2

…26.6.8) (#1144) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.6` → `2026.6.8` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.8`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202668) [Compare Source](openclaw/openclaw@v2026.6.6...v2026.6.8) ##### Highlights - Telegram and WhatsApp channel delivery are richer and less brittle: Telegram can send structured rich text with tables, lists, expandable blockquotes, prompt-preserving CLI backend delivery, retired native draft migration, and safer rich-media boundaries, while WhatsApp now honors configured ACP bindings. ([#92679](openclaw/openclaw#92679), [#84082](openclaw/openclaw#84082), [#89421](openclaw/openclaw#89421), [#92513](openclaw/openclaw#92513)) Thanks [@obviyus](https://github.com/obviyus), [@jzakirov](https://github.com/jzakirov), [@spacegeologist](https://github.com/spacegeologist), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Agent and Gateway recovery is sharper across account-scoped DM sends, generated media completions, restart shutdown aborts, yielded subagent pauses, yielded cron media, heartbeat dedupe, session identity prompts, and unknown OpenAI agent selector rejection. ([#92788](openclaw/openclaw#92788), [#91246](openclaw/openclaw#91246), [#91357](openclaw/openclaw#91357), [#92631](openclaw/openclaw#92631), [#92146](openclaw/openclaw#92146), [#91287](openclaw/openclaw#91287), [#92468](openclaw/openclaw#92468), [#92510](openclaw/openclaw#92510)) Thanks [@yetval](https://github.com/yetval), [@TurboTheTurtle](https://github.com/TurboTheTurtle), [@ooiuuii](https://github.com/ooiuuii), [@openperf](https://github.com/openperf), [@IWhatsskill](https://github.com/IWhatsskill), [@ZengWen-DT](https://github.com/ZengWen-DT), and [@zhangguiping-xydt](https://github.com/zhangguiping-xydt). - Provider/model handling expands and tightens with GLM-5.2, Claude Haiku 4.5 catalog rows, OpenRouter and Google Vertex provider-prefix normalization, managed SecretRef auth, bounded model browse discovery, storeless OpenAI Responses replay gating, and Claude 4.5 Copilot tool-streaming safety. ([#92796](openclaw/openclaw#92796), [#90116](openclaw/openclaw#90116), [#92627](openclaw/openclaw#92627), [#91218](openclaw/openclaw#91218), [#90686](openclaw/openclaw#90686), [#92247](openclaw/openclaw#92247), [#90706](openclaw/openclaw#90706), [#75393](openclaw/openclaw#75393)) Thanks [@arkyu2077](https://github.com/arkyu2077), [@liuhao1024](https://github.com/liuhao1024), [@bymle](https://github.com/bymle), [@rohitjavvadi](https://github.com/rohitjavvadi), [@samson910022](https://github.com/samson910022), [@snowzlm](https://github.com/snowzlm), and [@Kailigithub](https://github.com/Kailigithub). - `/usage` and reply payload hooks now have a native full footer renderer, default template, fixed-decimal formatting, credential-aware limits, better partial-count handling, and warnings for broken templates instead of silent bad output. ([#92657](openclaw/openclaw#92657), [#89835](openclaw/openclaw#89835), [#89629](openclaw/openclaw#89629)) Thanks [@Marvinthebored](https://github.com/Marvinthebored). - UI and mobile flows are steadier: workspace files can collapse and start collapsed, WebChat backscroll survives streaming, the sidebar session picker remains interactive above the desktop workbench, reset soft args survive UI dispatch, stale dashboard session parent lineage is preserved, and iOS reconnects stale foreground gateways. ([#92779](openclaw/openclaw#92779), [#92622](openclaw/openclaw#92622), [#92705](openclaw/openclaw#92705), [#91353](openclaw/openclaw#91353), [#90658](openclaw/openclaw#90658), [#92552](openclaw/openclaw#92552)) Thanks [@shakkernerd](https://github.com/shakkernerd), [@TurboTheTurtle](https://github.com/TurboTheTurtle), [@NianJiuZst](https://github.com/NianJiuZst), [@zhouhe-xydt](https://github.com/zhouhe-xydt), [@luoyanglang](https://github.com/luoyanglang), and [@Solvely-Colin](https://github.com/Solvely-Colin). - Memory, state, and diagnostics recover cleaner: oversized OpenAI embedding batches split before 431s, QMD memory search stays available in transient mode, SQLite avoids WAL on NFS state volumes, stuck-session recovery scheduling no longer resets warning backoff, and Infinity chunk limits stay genuinely unbounded. ([#92650](openclaw/openclaw#92650), [#92618](openclaw/openclaw#92618), [#92639](openclaw/openclaw#92639), [#91247](openclaw/openclaw#91247), [#92752](openclaw/openclaw#92752), [#92735](openclaw/openclaw#92735)) Thanks [@mushuiyu886](https://github.com/mushuiyu886), [@TurboTheTurtle](https://github.com/TurboTheTurtle), [@849261680](https://github.com/849261680), [@gnanam1990](https://github.com/gnanam1990), and [@yhterrance](https://github.com/yhterrance). ##### Changes - Providers/models: add GLM-5.2 support and Claude Haiku 4.5 catalog entries while keeping provider-qualified model IDs normalized across OpenRouter and Google Vertex paths. ([#92796](openclaw/openclaw#92796), [#90116](openclaw/openclaw#90116), [#92627](openclaw/openclaw#92627), [#91218](openclaw/openclaw#91218)) Thanks [@arkyu2077](https://github.com/arkyu2077), [@liuhao1024](https://github.com/liuhao1024), and [@bymle](https://github.com/bymle). - Channel plugins: ship Telegram rich-message delivery and WhatsApp ACP binding support, including rich prompt handoff to CLI backends and transport fixtures for richer drafts. ([#92679](openclaw/openclaw#92679), [#92513](openclaw/openclaw#92513)) Thanks [@obviyus](https://github.com/obviyus) and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Agent commands: support `/btw` in CLI-backed sessions and keep CLI usage-error exits classified as usage failures instead of successful runs. ([#92669](openclaw/openclaw#92669), [#92162](openclaw/openclaw#92162)) Thanks [@joshavant](https://github.com/joshavant) and [@Pandah97](https://github.com/Pandah97). - Usage hooks: add built-in full footer rendering, default footer templates, per-turn usage state, credential-aware limits, and fixed-decimal formatting for usage-bar templates. ([#92657](openclaw/openclaw#92657), [#89835](openclaw/openclaw#89835), [#89629](openclaw/openclaw#89629)) Thanks [@Marvinthebored](https://github.com/Marvinthebored). - Docs and operator guidance: document node config examples, clarify before-install hook scope, correct agent default concurrency comments, refresh ZAI provider docs, and update channel/group docs for current Telegram and WhatsApp behavior. ([#92677](openclaw/openclaw#92677), [#92766](openclaw/openclaw#92766), [#92695](openclaw/openclaw#92695)) Thanks [@liuhao1024](https://github.com/liuhao1024), [@sallyom](https://github.com/sallyom), and [@ArielSmoliar](https://github.com/ArielSmoliar). ##### Fixes - Onboarding/skills: show the Homebrew install recommendation only on macOS and Linux, so FreeBSD and other unsupported platforms no longer get a misleading brew prompt. Fixes [#68893](openclaw/openclaw#68893); carries forward [#68894](openclaw/openclaw#68894), [#68910](openclaw/openclaw#68910), [#68941](openclaw/openclaw#68941), [#68943](openclaw/openclaw#68943), [#69002](openclaw/openclaw#69002), and [#69545](openclaw/openclaw#69545). Thanks [@yurivict](https://github.com/yurivict), [@Sanjays2402](https://github.com/Sanjays2402), [@Eruditi](https://github.com/Eruditi), [@JustInCache](https://github.com/JustInCache), [@nnish16](https://github.com/nnish16), and [@Mlightsnow](https://github.com/Mlightsnow). - Channels and delivery: preserve account-scoped DM channel send policy, rich Telegram final replies, rich Telegram tables and lists, Telegram thread-create CLI remapping, Slack outbound `message_sent` hooks, contributed message-tool schema optionality, same-channel generated media completions, and channel chunking around surrogate pairs and Infinity limits. ([#92788](openclaw/openclaw#92788), [#92679](openclaw/openclaw#92679), [#89421](openclaw/openclaw#89421), [#89943](openclaw/openclaw#89943), [#91137](openclaw/openclaw#91137), [#91246](openclaw/openclaw#91246), [#92735](openclaw/openclaw#92735)) Thanks [@yetval](https://github.com/yetval), [@obviyus](https://github.com/obviyus), [@spacegeologist](https://github.com/spacegeologist), [@rishitamrakar](https://github.com/rishitamrakar), [@lundog](https://github.com/lundog), [@TurboTheTurtle](https://github.com/TurboTheTurtle), and [@yhterrance](https://github.com/yhterrance). - Auto-reply/groups: keep ordinary group text replies on automatic final-reply delivery while allowing `message(action=send)` for files, images, and other attachments to the same group or topic. Carries forward [#43276](openclaw/openclaw#43276); refs [#48004](openclaw/openclaw#48004). Thanks [@NayukiChiba](https://github.com/NayukiChiba) and [@ShakaRover](https://github.com/ShakaRover). - Auto-reply/skills: preserve multiline payloads for `/skill` and direct skill slash commands while keeping command-head normalization for aliases, colon syntax, and bot mentions. Fixes [#79155](openclaw/openclaw#79155); carries forward [#81305](openclaw/openclaw#81305). Thanks [@web3blind](https://github.com/web3blind). - iMessage: normalize leading NUL sent-message echo prefixes while preserving interior NUL bytes and the leading attributedBody marker handling from [#73942](openclaw/openclaw#73942). Carries forward [#63581](openclaw/openclaw#63581). Thanks [@drvoss](https://github.com/drvoss). - Discord: give generated auto-thread titles a 60-second timeout and 4,096-token reasoning-model output budget, clamped to the selected model output cap. ([#64734](openclaw/openclaw#64734)) Thanks [@hanamizuki](https://github.com/hanamizuki). - Agent, cron, and Gateway runtime: mark active main sessions before restart shutdown aborts, pause yielded subagent runs whose terminal also signals abort, preserve yielded media completions, de-duplicate main-session heartbeat events, expose session identity in runtime prompts, reject unknown OpenAI agent selectors, keep generated media completions and slash-command block replies in WebChat, preserve fresh post-compaction usage while clearing stale usage snapshots, and require admin privileges for HTTP session/model override surfaces. ([#91357](openclaw/openclaw#91357), [#92631](openclaw/openclaw#92631), [#92146](openclaw/openclaw#92146), [#91287](openclaw/openclaw#91287), [#92468](openclaw/openclaw#92468), [#92510](openclaw/openclaw#92510), [#91246](openclaw/openclaw#91246), [#50795](openclaw/openclaw#50795), [#50845](openclaw/openclaw#50845), [#82874](openclaw/openclaw#82874), [#92651](openclaw/openclaw#92651), [#92646](openclaw/openclaw#92646)) Thanks [@ooiuuii](https://github.com/ooiuuii), [@openperf](https://github.com/openperf), [@IWhatsskill](https://github.com/IWhatsskill), [@ZengWen-DT](https://github.com/ZengWen-DT), [@zhangguiping-xydt](https://github.com/zhangguiping-xydt), [@Hollychou924](https://github.com/Hollychou924), [@leno23](https://github.com/leno23), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Agents/exec: default empty-success background completion notices on only for real chat channels, preserving explicit opt-outs and keeping generic providers silent while carrying forward the narrow UX intent from [#39726](openclaw/openclaw#39726) and [#46926](openclaw/openclaw#46926). Thanks [@Sapientropic](https://github.com/Sapientropic) and [@wenkang-xie](https://github.com/wenkang-xie). - Providers and model replay: preserve storeless OpenAI Responses replay compatibility, avoid eager tool streaming for Claude 4.5 in Copilot, honor profile auth for SecretRef model entries, bound model browsing, strip provider prefixes where runtimes need bare IDs, and surface nested embedding fetch failures. ([#90706](openclaw/openclaw#90706), [#75393](openclaw/openclaw#75393), [#90686](openclaw/openclaw#90686), [#92247](openclaw/openclaw#92247), [#92627](openclaw/openclaw#92627), [#91218](openclaw/openclaw#91218), [#92628](openclaw/openclaw#92628)) Thanks [@snowzlm](https://github.com/snowzlm), [@Kailigithub](https://github.com/Kailigithub), [@rohitjavvadi](https://github.com/rohitjavvadi), [@samson910022](https://github.com/samson910022), [@liuhao1024](https://github.com/liuhao1024), [@bymle](https://github.com/bymle), and [@mushuiyu886](https://github.com/mushuiyu886). - Memory, state, diagnostics, and config: split header-too-large embedding batches, keep QMD memory search enabled in transient mode, avoid SQLite WAL on NFS volumes, preserve recovery scheduling outside stuck-session warning backoff, and keep shell environment fallbacks contained in config write tests. ([#92650](openclaw/openclaw#92650), [#92618](openclaw/openclaw#92618), [#92639](openclaw/openclaw#92639), [#91247](openclaw/openclaw#91247), [#92752](openclaw/openclaw#92752)) Thanks [@mushuiyu886](https://github.com/mushuiyu886), [@TurboTheTurtle](https://github.com/TurboTheTurtle), [@849261680](https://github.com/849261680), and [@gnanam1990](https://github.com/gnanam1990). - Workspace setup state: store setup completion outside the workspace dot directory using an OpenClaw-named root file, migrate valid legacy state forward, and avoid clobbering generic root `workspace-state.json` files for TigerFS-style dot-path compatibility. This Clownfish replacement carries forward the focused [#53326](openclaw/openclaw#53326) fix idea because the original branch was closed and uneditable. ([#53326](openclaw/openclaw#53326), [#44783](openclaw/openclaw#44783), [#39446](openclaw/openclaw#39446)) Thanks [@1qh](https://github.com/1qh). - UI/mobile/TUI: preserve dashboard session parent lineage, WebChat backscroll, reset soft command args, sidebar session picker interactivity, collapsed workspace files, resolved `/model` confirmation refs, and stale foreground iOS Gateway reconnects. ([#90658](openclaw/openclaw#90658), [#92622](openclaw/openclaw#92622), [#91353](openclaw/openclaw#91353), [#92705](openclaw/openclaw#92705), [#92779](openclaw/openclaw#92779), [#92773](openclaw/openclaw#92773), [#92552](openclaw/openclaw#92552)) Thanks [@luoyanglang](https://github.com/luoyanglang), [@TurboTheTurtle](https://github.com/TurboTheTurtle), [@zhouhe-xydt](https://github.com/zhouhe-xydt), [@NianJiuZst](https://github.com/NianJiuZst), [@shakkernerd](https://github.com/shakkernerd), [@NarahariRaghava](https://github.com/NarahariRaghava), and [@Solvely-Colin](https://github.com/Solvely-Colin). - TUI: reload the active session after external `/new` or `/reset` session-change events so stale transcript and stream state clear promptly. Fixes [#38966](openclaw/openclaw#38966); carries forward [#40472](openclaw/openclaw#40472). Thanks [@yizhanzjz](https://github.com/yizhanzjz) and [@wsyjh8](https://github.com/wsyjh8). - Control UI: preserve Gateway Access tokens during same-normalized WebSocket URL edits and reload gateway-scoped tokens when switching endpoints. Fixes [#41545](openclaw/openclaw#41545); repairs [#42001](openclaw/openclaw#42001) with additional source PRs [#41546](openclaw/openclaw#41546), [#41552](openclaw/openclaw#41552), and [#41718](openclaw/openclaw#41718). Thanks [@wsyjh8](https://github.com/wsyjh8), [@llagy0020](https://github.com/llagy0020), [@llagy007](https://github.com/llagy007), [@pingfanfan](https://github.com/pingfanfan), and [@zheliu2](https://github.com/zheliu2). - Gateway CLI: tolerate a single transient clean WebSocket close before `hello-ok` so one-shot RPC calls reconnect instead of failing noisily, while repeated clean pre-hello closes still surface. Carries forward source PRs [#54475](openclaw/openclaw#54475) and [#54774](openclaw/openclaw#54774); [#85253](openclaw/openclaw#85253) covered adjacent connect assembly diagnostics. Thanks [@ruanrrn](https://github.com/ruanrrn). - Gateway/Linux: keep root-owned systemd user service lifecycle commands on root's user manager when a stale `SUDO_USER` remains in a root shell with root's user bus environment. Fixes [#81410](openclaw/openclaw#81410). Thanks [@Ericksza](https://github.com/Ericksza) and [@ChuckClose-tech](https://github.com/ChuckClose-tech). - Release and test reliability: extend slow Gateway/full-suite watchdogs, split local full-suite shards when throttled, stabilize plugin auth marker fixtures, avoid brittle provider-ref error text, and keep QA Lab bootstrap selection assertions aligned with flow-only scenarios. ([#92652](openclaw/openclaw#92652)) - macOS Peekaboo bridge: update the embedded Peekaboo package to 3.5.2 and route bundled-skill CLI commands through the OpenClaw app bridge so they inherit its Screen Recording and Accessibility grants. - Agent routing: route subagent RPC callbacks addressed to an agent-shaped `--to` target to the correct session key instead of falling back to the main session, so WeChat (and other channel) session-key callbacks reach the intended subagent session. ([#90231](openclaw/openclaw#90231)) Thanks [@zhangguiping-xydt](https://github.com/zhangguiping-xydt). - Cron: preserve model, fallback, thinking, timeout, light-context, unsafe-content, and tool allow-list overrides on implicit text payloads by promoting them to agent turns, while explicit system events still prune those fields. Fixes [#28905](openclaw/openclaw#28905); carries forward [#64060](openclaw/openclaw#64060) and [#73946](openclaw/openclaw#73946). Thanks [@liaoandi](https://github.com/liaoandi). - QQBot delivery: keep markdown table chunks self-contained across message boundaries by preserving table state across block deliveries, flushing unfinished table-row fragments as plain text, and detecting short pipe-terminated rows by column count so split rows are not sent as malformed markdown. ([#92428](openclaw/openclaw#92428)) Thanks [@sliverp](https://github.com/sliverp). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1144

openclaw-barnacle Bot added docs Improvements or additions to documentation channel: discord Channel integration: discord channel: telegram Channel integration: telegram scripts Repository scripts size: XL maintainer Maintainer-authored PR labels Jun 13, 2026

clawsweeper Bot temporarily deployed to qa-live-shared June 13, 2026 13:22 Inactive

openclaw-barnacle Bot added the agents Agent runtime and tooling label Jun 13, 2026

obviyus force-pushed the codex/telegram-rich-messages branch from 921cd02 to 5522476 Compare June 13, 2026 14:40

obviyus added 9 commits June 13, 2026 20:26

feat(telegram): send text as rich messages

8aeb972

refactor(telegram): remove native draft previews

9c8101c

fix(chunking): preserve surrogate pairs

e0500ba

test(telegram): cover rich list and table limits

b871667

fix(telegram): migrate retired native draft config

1d382c8

fix(telegram): keep rich text media-free

69d50e6

feat(telegram): nudge agents toward rich text

e7591fd

fix(telegram): clean rich message CI gates

42c55ad

test(telegram): align message flow fixture with rich drafts

12abd37

fix(telegram): allow rich tables in group prompts

187e95d

obviyus force-pushed the codex/telegram-rich-messages branch from 5522476 to 187e95d Compare June 13, 2026 14:57

obviyus added 2 commits June 13, 2026 21:07

fix(telegram): show rich text prompt for final replies

25014c6

fix(telegram): pass rich text prompts to cli backends

ed2c94a

obviyus merged commit 45e36a2 into main Jun 13, 2026
161 checks passed

obviyus deleted the codex/telegram-rich-messages branch June 13, 2026 16:15

Glucksberg mentioned this pull request Jun 14, 2026

feat(telegram): add rich message API helpers #92309

Closed

This was referenced Jun 14, 2026

fix(telegram): preserve delivery without rich API #92946

Closed

fix(telegram): respect configured text chunk limit #64717

Closed

[codex] Fix Telegram rich parse fallback text loss #93059

Draft

SweetSophia mentioned this pull request Jun 15, 2026

[Bug]: Telegram clients show "not supported" for every reply on 2026.6.8-beta.1 #93263

Closed

This was referenced Jun 15, 2026

fix(telegram): restore readable default text sends #93279

Merged

fix(telegram): default replies to legacy sendMessage #93372

Closed

steipete mentioned this pull request Jun 16, 2026

feat: Telegram Bot API 10.1 — Rich Messages support (sendRichMessage, sendRichMessageDraft, RichBlockThinking) #92258

Closed

This was referenced Jun 17, 2026

Telegram message text appears larger after upgrading to v2026.6.8 and custom font size is ignored #94098

Closed

Telegram iOS font size setting ignored in v2026.6.8 — bot messages render at fixed larger size #94131

Closed

agentecausante-gif mentioned this pull request Jun 17, 2026

Feature Request: Add parseMode config for Telegram channels #10944

Open

ZOOWH mentioned this pull request Jun 19, 2026

fix(telegram): skip parse_mode=HTML for plain-text chunks to preserve iOS font-size #94873

Closed

clawsweeper Bot mentioned this pull request Jun 22, 2026

fix(telegram): fall back to sendMessage when sendRichMessage unsupported by client #95626

Closed

steipete mentioned this pull request Jul 12, 2026

Clarify group chat style guidance #79141

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

feat(telegram): send rich message text#92679

feat(telegram): send rich message text#92679
obviyus merged 12 commits into
mainfrom
codex/telegram-rich-messages

obviyus commented Jun 13, 2026

Uh oh!

clawsweeper Bot commented Jun 13, 2026 •

edited

Loading

Uh oh!

openclaw-mantis Bot commented Jun 13, 2026

Uh oh!

obviyus commented Jun 13, 2026

Uh oh!

Uh oh!

obviyus commented Jun 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

obviyus commented Jun 13, 2026

Uh oh!

clawsweeper Bot commented Jun 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openclaw-mantis Bot commented Jun 13, 2026

Mantis Telegram Desktop Proof

Uh oh!

obviyus commented Jun 13, 2026

Uh oh!

Uh oh!

obviyus commented Jun 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

clawsweeper Bot commented Jun 13, 2026 •

edited

Loading