openclaw - 💡(How to fix) Fix Windows: Feishu channel exits with ESM loader error 'Received protocol c:' on OpenClaw 2026.4.24 [2 comments, 3 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#72862Fetched 2026-04-28 06:31:13
View on GitHub
Comments
2
Participants
3
Timeline
3
Reactions
0
Author
Timeline (top)
commented ×2closed ×1

Code Example

[gateway/channels/feishu] [work] channel exited: 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:'
[gateway/channels/feishu] [private] channel exited: 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:'
RAW_BUFFERClick to expand / collapse

Environment

  • OS: Windows 11 / Windows_NT 10.0.26100 x64
  • Node.js: v24.14.1
  • OpenClaw: 2026.4.24 (cbcfdf6)
  • Install: global npm install

Problem

The gateway stays up, but Feishu channels fail to initialize and keep auto-restarting.

Observed log

[gateway/channels/feishu] [work] channel exited: 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:'
[gateway/channels/feishu] [private] channel exited: 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:'

Notes

  • Happens on both private and work Feishu accounts (not account-specific).
  • Main gateway process remains healthy.
  • This is separate from an earlier bonjour crash (CIAO PROBING CANCELLED).
  • Issue still happens on 2026.4.24 - upgrading did not fix it.

Possible fix direction

Check the Feishu channel / bundled plugin runtime loading path on Windows. A raw Windows absolute path (e.g. C:\...) is likely being passed to an ESM loader that expects a file:// URL. Ensure any filesystem path used in import(), loader, or JITI-based module resolution is normalized via pathToFileURL(...).href before being used as an ESM specifier.

extent analysis

TL;DR

The issue can be resolved by normalizing Windows absolute paths to file:// URLs using pathToFileURL(...).href before passing them to the ESM loader.

Guidance

  • Verify that the Feishu channel plugin is using the correct path format by checking the code for any instances of import() or loader functions that may be passing raw Windows absolute paths.
  • Ensure that any filesystem paths used in module resolution are normalized using pathToFileURL(...).href to convert them to valid file:// URLs.
  • Review the OpenClaw documentation to see if there are any specific requirements or recommendations for handling Windows paths in ESM loaders.
  • Test the fix by updating the code to use normalized paths and verifying that the Feishu channels initialize correctly.

Example

const path = require('path');
const { fileURLToPath, pathToFileURL } = require('url');

// Assuming 'filePath' is a raw Windows absolute path (e.g. 'C:\...')
const normalizedPath = pathToFileURL(filePath).href;
// Use 'normalizedPath' as the ESM specifier

Notes

The issue seems to be specific to Windows and the use of ESM loaders. The provided log messages indicate that the ESM loader is expecting a file:// URL, but is receiving a raw Windows absolute path instead.

Recommendation

Apply workaround: Normalize Windows absolute paths to file:// URLs using pathToFileURL(...).href to ensure compatibility with the ESM loader. This should resolve the issue without requiring an upgrade to a fixed version.

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

openclaw - 💡(How to fix) Fix Windows: Feishu channel exits with ESM loader error 'Received protocol c:' on OpenClaw 2026.4.24 [2 comments, 3 participants]