OpenClaw v2026.4.14-beta.1: Telegram/forum topics, for maintainers

For maintainers reading v2026.4.14-beta.1, the source is a map of contracts. It describes a channel, client, interface, or browser change, then lists implementation changes and fixes that can affect plugins, providers, or downstream tooling.

This candidate is still pre-release. Treat provider, channel, and migration behavior as unconfirmed until your own bounded test passes. Treat the version as one input to the decision. Local credentials, enabled plugins, channels, and host support still need their own evidence.

Compatibility for maintainers

01 / Telegram/forum topics

Source signal. surface human topic names in agent context, prompt metadata, and plugin hook metadata by learning names from Telegram forum service messages.

The operator question around Telegram/forum topics is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

02 / UI/chat

Source signal. replace marked.js with markdown-it so maliciously crafted markdown can no longer freeze the Control UI via ReDoS.

Test UI/chat at the edges of the interface: clean start, reload, reconnect, and a refused or unavailable action. Keep the final screen and error message with the release note.

03 / Auto-reply/send policy

Source signal. keep sendPolicy: "deny" from blocking inbound message processing, so the agent still runs its turn while all outbound delivery is suppressed for observer-style setups.

For Auto-reply/send policy, delivery is only proven when identity survives an interruption. Keep a disposable channel, send one request, and check for a single reply in the intended thread.

API, package, and test clues

Read the narrow change in context

v2026.4.14-beta.1 is a pre-release checkpoint with a deliberately small surface. The source names Telegram/forum topics: surface human topic names in agent context, prompt metadata, and plugin hook metadata by learning names from Telegram forum service messages. A narrow patch still has a clear job: it should remove one failure or preserve one compatibility promise without changing unrelated configuration.

Keep this patch beside the package and test record. Compare the installed tag, package version, and service owner before applying it. If this entry is a correction release, record the broken behavior that led you here, then repeat that exact scenario after the update. That evidence is more useful than a general claim that the package installed successfully.

The adjacent source detail is UI/chat: replace marked.js with markdown-it so maliciously crafted markdown can no longer freeze the Control UI via ReDoS. Read both signals together, because a hotfix can alter the boundary around a plugin, channel, session, or installer even when the version number looks like a minor suffix.

A small worksheet for this version

• Write the old version, the new version, and the package or tag that actually changed.
• Capture one reproduction before the update and the same reproduction after it.
• Record the first useful log line, the final user-visible result, and any rollback command that was tested.
• Leave unrelated channels, skills, and provider defaults untouched until the correction is understood.

Run the smallest useful rehearsal

1. Write down the baseline for Telegram/forum topics, including the installed version, host, provider, and workspace.
2. Confirm what can be restored, then take a verified backup before applying the candidate package.
3. Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
4. Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
5. Keep the experiment bounded; an unexpected result belongs in the release record before any wider rollout.

openclaw --version
openclaw gateway status
openclaw doctor

Leave a usable maintenance note

Save the command, output, source link, and environment used for this check. Future operators should be able to tell whether a difference belongs to the release or to local provider, channel, or platform state.

Fix details to carry forward

UI/chat. replace marked.js with markdown-it so maliciously crafted markdown can no longer freeze the Control UI via ReDoS. This is the edge case to include in a regression check, especially when the release is pre-release.

Auto-reply/send policy. keep sendPolicy: "deny" from blocking inbound message processing, so the agent still runs its turn while all outbound delivery is suppressed for observer-style setups. Treat the fix as a boundary condition and retain the source wording beside your local result.

Keep the full v2026.4.14-beta.1 notes with your test result. Read the official release index for neighboring versions and the channel routing guide for configuration limits.