News

OpenClaw v2026.5.5: LINE, operator field notes

May 6, 20265 min readUpdated September 11, 2026By OpenClawBlog Team

The source record for v2026.5.5 names a release-level runtime or packaging change. This is an operator's reading of that record, with the exact source facts kept next to a bounded experiment rather than a generic feature list.

This is a stable release line; read the exact record for migrations and fixes before applying it to a live Gateway. The release body cannot certify every local combination of provider, channel, platform, and account; use the bounded test below for the path you actually run.

Channel
Stable

Primary signals
Feishu; LINE; source trail

Publication date
2026-05-06

A small field test

01 / Feishu

Source signal. hydrate missing native topic starter thread IDs before session routing so first turns and follow-ups stay in the same topic session. Fixes #78262.

Use Feishu as a routing test: capture the destination before the send, interrupt the transport, and verify that retry logic did not duplicate or redirect the response.

02 / LINE

Source signal. reject dmPolicy: "open" configs without wildcard allowFrom so webhook DMs fail validation instead of being acknowledged and silently blocked before inbound processing. Fixes #78316.

Use LINE for a small reproducible task: save the input, visible result, useful failure, and version context another operator would need.

The details that affect a runbook

Read the narrow change in context

v2026.5.5 is a stable checkpoint with a deliberately small surface. The source names Feishu: hydrate missing native topic starter thread IDs before session routing so first turns and follow-ups stay in the same topic session. Fixes #78262. 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 operator's maintenance notes. 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 LINE: reject dmPolicy: "open" configs without wildcard allowFrom so webhook DMs fail validation instead of being acknowledged and silently blocked before inbound processing. Fixes #78316. 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.

A bounded check for this version

  1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Feishu.
  2. Check the release's migration notes and make a restorable backup before changing persistent state.
  3. Use one deterministic input to exercise the change and keep the command, output, and source note together.
  4. Compare the result with the previous version and write down the one behavior that changed and the one that did not.
  5. If the result differs from the release body, stop the rollout and attach the log, screenshot, or transcript to the version record.
openclaw --version
openclaw gateway status
openclaw doctor

Close the loop with evidence

A useful maintenance record names the changed behavior, the behavior that stayed stable, the identity that approved the test, and the step that would undo it. Preserve that record beside the release tag.

Edge cases in this tag

Feishu. hydrate missing native topic starter thread IDs before session routing so first turns and follow-ups stay in the same topic session. Fixes #78262. Record the failure that this correction addresses before declaring the upgrade complete.

LINE. reject dmPolicy: "open" configs without wildcard allowFrom so webhook DMs fail validation instead of being acknowledged and silently blocked before inbound processing. Fixes #78316. This is the edge case to include in a regression check, especially when the release is pre-release.

The authoritative record is the v2026.5.5 GitHub release. The release index gives the surrounding sequence, while the getting-started guide supplies the operational background.

Reference Trail

Sources and further reading

  1. v2026.5.5 GitHub releasegithub.com
  2. release indexgithub.com
  3. getting-started guidedocs.openclaw.ai
Back to ArchiveMore: NewsNext: OpenClaw iMessage node setup: verify the first message safely