Guide

OpenClaw v2026.5.10-beta.2: QA/Mantis, upgrade notes

May 10, 20264 min readUpdated September 11, 2026By OpenClawBlog Team

v2026.5.10-beta.2 arrived on 2026-05-10 with a change that matters during maintenance: qa/mantis. The page is a researched reading note from the official release record, with a test path for a real Gateway.

The tag is pre-release: keep it isolated from a production Gateway and compare it with the stable line before making it a default. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.

Channel
Pre-Release

Primary signals
QA/Mantis; Discord/voice; Telegram

Publication date
2026-05-10

Before the package changes

QA/Mantis

Evidence from the release. add Telegram live PR evidence automation with Convex-leased credentials, Crabbox transcript capture, motion GIF previews, and inline PR comments.

Operator reading. The useful evidence for QA/Mantis is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

QA/Mantis

Evidence from the release. add a Telegram desktop scenario builder that leases Crabbox, installs native Telegram Desktop, configures an OpenClaw Telegram gateway with leased bot credentials, and records VNC screenshot/video artifacts.

Operator reading. The useful evidence for QA/Mantis is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

Discord/voice

Evidence from the release. add realtime voice diagnostics for speaker turns, playback resets, barge-in detection, and audio cutoff analysis.

Operator reading. The operator question around Discord/voice is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

Telegram

Evidence from the release. pass agent-scoped media roots through gateway message actions so workspace-local media from the active agent is not rejected as cross-agent access.

Operator reading. For Telegram, 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.

Details behind the headline

CLI/gateway

keep gateway status --deep plugin-aware so configured plugin manifest warnings, including missing channel config metadata, stay visible during install and update smoke checks.

CLI/gateway lives at the handoff between the Gateway and a conversation. Send one harmless message, reconnect once, and compare the account, thread, sender, and final transcript.

Test this release without widening the boundary

  1. Note the current version, host, provider, and workspace before exercising QA/Mantis.
  2. Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
  3. Send one harmless message through the named account and save the account, thread, and sender identifiers.
  4. Compare the transcript before and after reconnect, including delivery state and any visible error.
  5. Stop if the observed behavior falls outside the official note, and link the log or screenshot to the version record.
openclaw --version
openclaw gateway status
openclaw doctor

Record what the release actually changed

Keep the version, source URL, test identity, and rollback decision together. If this tag is pre-release, leave it isolated; if it is stable, record the migration and rollback result before reconnecting every channel.

Corrections worth replaying

Telegram. pass agent-scoped media roots through gateway message actions so workspace-local media from the active agent is not rejected as cross-agent access. Keep the reproduction and the post-fix result together in the acceptance record.

CLI/gateway. keep gateway status --deep plugin-aware so configured plugin manifest warnings, including missing channel config metadata, stay visible during install and update smoke checks. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.5.10-beta.2 release notes for the exact change list, then cross-check the official release index and the model provider reference before acting.

Reference Trail

Sources and further reading

  1. complete OpenClaw v2026.5.10-beta.2 release notesgithub.com
  2. official release indexgithub.com
  3. model provider referencedocs.openclaw.ai
Back to ArchiveMore: GuidesNext: OpenClaw v2026.5.10-beta.1: QA/Mantis, provider notes