Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Feishu messaging broken on Windows: ESM loader path error [4 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#72783•Fetched 2026-04-28 06:32:14
View on GitHub
Comments
4
Participants
2
Timeline
8
Reactions
0
Author
jackychen-pngjackychen-png
Participants
jackychen-pngjackychen-pngsteipetesteipete
Timeline (top)
commented ×4closed ×2cross-referenced ×1reopened ×1

Error Message

Feishu messaging is completely broken on Windows. Sending messages via the \message\ tool fails with the following error: 3. Error is returned

  • The error originates from Node.js ESM loader when processing a Windows absolute path (\C:...) as an import URL Message sending should work normally, or at least provide a more actionable error message. The error occurs because Node.js ESM module loader requires Windows absolute paths to be in \

Root Cause

The error occurs because Node.js ESM module loader requires Windows absolute paths to be in \ ile:///C:/...\ format, but somewhere in the code path (likely in the lazy runtime module loading for the feishu channel), a raw Windows path like \C:\Users...\ is being passed to \import().

This bug appears to be in the OpenClaw core, not in user configuration or feishu API credentials.

RAW_BUFFERClick to expand / collapse

Bug Description

Feishu messaging is completely broken on Windows. Sending messages via the \message\ tool fails with the following error:

Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

Environment

  • OS: Windows
  • OpenClaw version: 2026.4.24
  • Node.js: v24.13.1
  • Channel: Feishu (websocket mode)

Steps to Reproduce

  1. Configure Feishu channel with appId and appSecret
  2. Attempt to send a message using the \message\ tool with \channel=feishu\
  3. Error is returned

Observed Behavior

  • Feishu API scopes are correctly detected (156 permissions granted)
  • Feishu document read/write works fine (feishu_doc tools work)
  • Only message sending is broken
  • The error originates from Node.js ESM loader when processing a Windows absolute path (\C:...) as an import URL

Expected Behavior

Message sending should work normally, or at least provide a more actionable error message.

Analysis

The error occurs because Node.js ESM module loader requires Windows absolute paths to be in \ ile:///C:/...\ format, but somewhere in the code path (likely in the lazy runtime module loading for the feishu channel), a raw Windows path like \C:\Users...\ is being passed to \import().

This bug appears to be in the OpenClaw core, not in user configuration or feishu API credentials.

Additional Context

  • \openclaw doctor\ output shows: \Feishu: failed (unknown)\
  • The issue affects both WebSocket (connectionMode: websocket) configured channel
  • Feishu docs functionality works perfectly, indicating API credentials are correct

extent analysis

TL;DR

The issue can be fixed by modifying the code to convert Windows absolute paths to valid file:// URLs before passing them to the Node.js ESM loader.

Guidance

  • Verify that the error occurs when sending messages via the message tool with the Feishu channel configured.
  • Check the OpenClaw core code for the lazy runtime module loading of the Feishu channel to identify where the raw Windows path is being passed to import().
  • Consider using the URL class or a similar approach to convert Windows absolute paths to valid file:// URLs, such as file:///C:/....
  • Test the fix by sending a message via the message tool with the modified code.

Example

const filePath = 'C:\\\\\\Users\\\\\\...';
const fileUrl = `file:///C:/${filePath.replace(/\\/g, '/')}`;
// Use fileUrl instead of filePath when calling import()

Notes

The fix may require modifications to the OpenClaw core code, which could have implications for future updates or compatibility. It's essential to test the fix thoroughly to ensure it resolves the issue without introducing new problems.

Recommendation

Apply a workaround by modifying the OpenClaw core code to convert Windows absolute paths to valid file:// URLs, as this is the most direct way to address the issue.

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…
#api#ssr#installation#tensor shape#autograd error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Feishu messaging broken on Windows: ESM loader path error [4 comments, 2 participants]