版本升级作战卡：按 2026.2.17 发布点逐项回归（1M context / subagent / Telegram 按钮）
问题/场景：升级后功能很多，容易只看版本号却漏掉关键回归。前置条件：可维护窗口、可重启 gateway。实施步骤：先升级再按发布清单做最小回归（subagent、消息流式、按钮样式）→记录通过/失败矩阵。关键命令：openclaw gateway status、openclaw gateway restart。验证：三类核心能力都可复现。风险：不同渠道功能开关不一致，需逐渠道验证。
XDiscovered 2026-02-19Author @openclaw
Prerequisites
- Runtime has been upgraded to v2026.2.17 (or newer) and release notes are accessible.
- At least one chat channel (e.g., Telegram/Slack) is connected for end-to-end verification.
Steps
- Restart gateway after upgrade and capture baseline with openclaw gateway status.
- Run one spawn-subagent scenario from chat and verify result announcement returns to parent conversation.
- Test streaming reply path on your primary channel; ensure long outputs arrive progressively instead of one-shot flush.
- For Telegram, send message with inline buttons and verify rendered style plus callback round-trip.
- Record pass/fail matrix and keep rollback command path ready before widening rollout.
Commands
openclaw gateway statusopenclaw gateway restartopenclaw helpVerify
Post-upgrade checks pass for subagent spawn, channel streaming, and Telegram inline-button interaction in one maintenance window.
Caveats
- The X post is a feature announcement; exact config toggles per deployment should be cross-checked in official docs/release page（需验证）.
- Do not skip rollback rehearsals when enabling multiple new capabilities simultaneously.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗