openclaw - 💡(How to fix) Fix Bundled channel setup entries emit warnings when generated modules are missing, ignoring channel/plugin disabled config [1 pull requests]

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…

Error Message

This feeds into listBundledChannelSetupPlugins() which then calls loadGeneratedBundledChannelSetupEntry() for every bundled channel, triggering log.warn when the generated module is missing (common on Windows or incomplete builds).

Root Cause

listBundledChannelPluginIdsForRoot() in src/channels/plugins/bundled.ts (line 354) enumerates all bundled channel metadata unconditionally, without checking the user's config for disabled channels:

function listBundledChannelPluginIdsForRoot(
  rootScope: BundledChannelRootScope,
): readonly ChannelId[] {
  return listBundledChannelMetadata(rootScope)
    .map((metadata) => metadata.manifest.id)
    .toSorted((left, right) => left.localeCompare(right));
}

This feeds into listBundledChannelSetupPlugins() which then calls loadGeneratedBundledChannelSetupEntry() for every bundled channel, triggering log.warn when the generated module is missing (common on Windows or incomplete builds).

Meanwhile, shouldIncludeBundledChannelSetupFeatureForConfig() (line 362) already implements the correct filtering logic — checking plugins.entries[id].enabled and channels[id].enabled — but it is only used for listBundledChannelPluginIdsForSetupFeature(), not for the main plugin enumeration.

Fix Action

Fixed

Code Example

[channels] failed to load bundled channel irc: missing generated module for bundled channel irc
[channels] failed to load bundled channel setup entry irc: missing generated module for bundled channel irc

---

function listBundledChannelPluginIdsForRoot(
  rootScope: BundledChannelRootScope,
): readonly ChannelId[] {
  return listBundledChannelMetadata(rootScope)
    .map((metadata) => metadata.manifest.id)
    .toSorted((left, right) => left.localeCompare(right));
}

---

{
  "channels": { "imessage": { "enabled": false }, "irc": { "enabled": false } },
  "plugins": { "entries": { "imessage": { "enabled": false }, "irc": { "enabled": false } } }
}
RAW_BUFFERClick to expand / collapse

Describe the bug

openclaw doctor emits warnings for bundled channels (imessage, irc, mattermost, signal) even when they are explicitly disabled in both channels.<id>.enabled and plugins.entries.<id>.enabled config:

[channels] failed to load bundled channel irc: missing generated module for bundled channel irc
[channels] failed to load bundled channel setup entry irc: missing generated module for bundled channel irc

Root Cause

listBundledChannelPluginIdsForRoot() in src/channels/plugins/bundled.ts (line 354) enumerates all bundled channel metadata unconditionally, without checking the user's config for disabled channels:

function listBundledChannelPluginIdsForRoot(
  rootScope: BundledChannelRootScope,
): readonly ChannelId[] {
  return listBundledChannelMetadata(rootScope)
    .map((metadata) => metadata.manifest.id)
    .toSorted((left, right) => left.localeCompare(right));
}

This feeds into listBundledChannelSetupPlugins() which then calls loadGeneratedBundledChannelSetupEntry() for every bundled channel, triggering log.warn when the generated module is missing (common on Windows or incomplete builds).

Meanwhile, shouldIncludeBundledChannelSetupFeatureForConfig() (line 362) already implements the correct filtering logic — checking plugins.entries[id].enabled and channels[id].enabled — but it is only used for listBundledChannelPluginIdsForSetupFeature(), not for the main plugin enumeration.

To Reproduce

  1. Add to openclaw.json:
{
  "channels": { "imessage": { "enabled": false }, "irc": { "enabled": false } },
  "plugins": { "entries": { "imessage": { "enabled": false }, "irc": { "enabled": false } } }
}
  1. Run openclaw doctor
  2. Observe [channels] failed to load bundled channel warnings for disabled channels

Expected behavior

Channels explicitly disabled in config should be skipped entirely during bundled channel enumeration, producing no warnings.

Suggested Fix

Apply the same filtering from shouldIncludeBundledChannelSetupFeatureForConfig() to listBundledChannelPluginIdsForRoot(), or pass config context through the enumeration path so disabled channels are filtered before any module loading is attempted.

Environment

  • OpenClaw version: 2026.5.22 (a374c3a)
  • OS: Windows 10 Education 10.0.19045
  • Node.js version: (see below)

Additional context

This issue is more noticeable on Windows because generated dist modules are often missing for bundled channels that aren't part of the active build, making the warnings appear on every doctor run.

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…

FAQ

Expected behavior

Channels explicitly disabled in config should be skipped entirely during bundled channel enumeration, producing no warnings.

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 Bundled channel setup entries emit warnings when generated modules are missing, ignoring channel/plugin disabled config [1 pull requests]