openclaw - 💡(How to fix) Fix [Bug] Feishu plugin 2026.5.22: gateway connection timeout + QR code display broken

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Two regressions introduced by Feishu plugin v2026.5.22:

  1. Gateway startup connection timeout: After upgrading the openclaw and Feishu plugin to 2026.5.22, the Gateway takes an extremely long time to connect to Feishu on startup, with timeout errors appearing in logs before the connection eventually succeeds.

  2. QR code display broken during configure: When running openclaw configure and selecting QR Code for Feishu setup, the QR code is rendered at an abnormal size — it fills the entire terminal window, making it impossible to scan without manually resizing the terminal to a very large window.

Root Cause

Additional context

  • Both issues appeared after upgrading the openclaw and Feishu plugin to 2026.5.22
  • Previous Feishu plugin version (5.18) worked without these issues
  • I have rolled back to openclaw 5.18 and issues 1 is resolved, but issue 2 still exsist because the Feishu plugin can not roll back, after run the openclaw configure, Feishu plugin will Automatically update to the latest version.
  • The QR code issue may be related to terminal rendering changes in the new plugin version
  • The connection timeout may be related to the lazy-loading changes in 5.22 Gateway performance optimizations
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Two regressions introduced by Feishu plugin v2026.5.22:

  1. Gateway startup connection timeout: After upgrading the openclaw and Feishu plugin to 2026.5.22, the Gateway takes an extremely long time to connect to Feishu on startup, with timeout errors appearing in logs before the connection eventually succeeds.

  2. QR code display broken during configure: When running openclaw configure and selecting QR Code for Feishu setup, the QR code is rendered at an abnormal size — it fills the entire terminal window, making it impossible to scan without manually resizing the terminal to a very large window.

Steps to reproduce

Issue 1: Gateway connection timeout

  1. Upgrade openclaw and Feishu plugin to 2026.5.22
  2. Start the Gateway with openclaw gateway start
  3. Observe long delay and timeout errors in logs before Feishu connects

Issue 2: QR code display

  1. Run openclaw configure
  2. Select Feishu channel setup
  3. Choose QR Code option
  4. The QR code renders oversized, filling the entire terminal window

Expected behavior

Issue 1

Feishu plugin should connect promptly on Gateway startup, as it did in previous versions.

Issue 2

QR code should render at a standard, scannable size within the terminal window.

Actual behavior

Issue 1

Connection takes significantly longer with timeout errors in gateway logs.

Issue 2

QR code is scaled to fill the entire terminal, requiring manual window resizing to view the complete code.

Environment

  • openclaw version (when issues occurred): 2026.5.22
  • openclaw version (after rollback): 2026.5.18 (working normally)
  • Feishu plugin version: @openclaw/feishu 2026.5.22
  • OS: Windows 11 Professional (10.0.26100, x64)
  • Node.js: v24.15.0
  • Install method: npm global
  • Feishu domain: feishu (CN)
  • Connection mode: websocket

Additional context

  • Both issues appeared after upgrading the openclaw and Feishu plugin to 2026.5.22
  • Previous Feishu plugin version (5.18) worked without these issues
  • I have rolled back to openclaw 5.18 and issues 1 is resolved, but issue 2 still exsist because the Feishu plugin can not roll back, after run the openclaw configure, Feishu plugin will Automatically update to the latest version.
  • The QR code issue may be related to terminal rendering changes in the new plugin version
  • The connection timeout may be related to the lazy-loading changes in 5.22 Gateway performance optimizations

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING