Summary
Running openclaw onboard and selecting Feishu during channel setup can end with:
feishu missing register/activate export
feishu plugin not available
After that, onboarding finishes without writing any channels.feishu config, even though Feishu is shown as installed.
Reproduction
- Start from a fresh local config directory.
- Run
openclaw onboard.
- Select
Feishu/Lark (飞书) in QuickStart / channel setup.
- Continue through setup.
Actual behavior
The setup UI reports:
Feishu: installed
Feishu: not configured
feishu missing register/activate export
feishu plugin not available
~/.openclaw/openclaw.json ends up with only:
plugins.entries.openclawcode.config.defaultNotificationLocale
and no channels.feishu block is written.
Expected behavior
Feishu should load through its setup entry, prompt for the required Feishu configuration, and write the resulting channels.feishu config during onboarding.
Root cause
The Feishu bundled setup entry is emitted in the new bundled channel setup contract shape:
kind: "bundled-channel-setup-entry"
loadSetupPlugin()
Example built artifact:
dist/extensions/feishu/setup-entry.js
However, the setup-time loader path in src/plugins/loader.ts still resolves setup exports using the legacy shape:
function resolveSetupChannelRegistration(moduleExport: unknown): {
plugin?: ChannelPlugin;
} {
const resolved = unwrapDefaultModuleExport(moduleExport);
if (!resolved || typeof resolved !== "object") {
return {};
}
const setup = resolved as {
plugin?: unknown;
};
if (!setup.plugin || typeof setup.plugin !== "object") {
return {};
}
return {
plugin: setup.plugin as ChannelPlugin,
};
}
So when manifestRecord.setupSource is present, the loader does not recognize the bundled setup entry contract, fails to register the setup plugin, and then falls through to the generic plugin export path, which expects register/activate. That produces the misleading error:
missing register/activate export
Relevant locations:
src/plugins/loader.ts (resolveSetupChannelRegistration, setup-only/setup-runtime branch)
dist/extensions/feishu/setup-entry.js
dist/channel-entry-contract-*.js (defineBundledChannelSetupEntry returns kind: "bundled-channel-setup-entry" + loadSetupPlugin)
src/flows/channel-setup.ts (surfaces plugin not available)
Notes
This likely affects other bundled channel plugins that use defineBundledChannelSetupEntry(...), not just Feishu.
Summary
Running
openclaw onboardand selecting Feishu during channel setup can end with:feishu missing register/activate exportfeishu plugin not availableAfter that, onboarding finishes without writing any
channels.feishuconfig, even though Feishu is shown as installed.Reproduction
openclaw onboard.Feishu/Lark (飞书)in QuickStart / channel setup.Actual behavior
The setup UI reports:
Feishu: installedFeishu: not configuredfeishu missing register/activate exportfeishu plugin not available~/.openclaw/openclaw.jsonends up with only:plugins.entries.openclawcode.config.defaultNotificationLocaleand no
channels.feishublock is written.Expected behavior
Feishu should load through its setup entry, prompt for the required Feishu configuration, and write the resulting
channels.feishuconfig during onboarding.Root cause
The Feishu bundled setup entry is emitted in the new bundled channel setup contract shape:
kind: "bundled-channel-setup-entry"loadSetupPlugin()Example built artifact:
dist/extensions/feishu/setup-entry.jsHowever, the setup-time loader path in
src/plugins/loader.tsstill resolves setup exports using the legacy shape:So when
manifestRecord.setupSourceis present, the loader does not recognize the bundled setup entry contract, fails to register the setup plugin, and then falls through to the generic plugin export path, which expectsregister/activate. That produces the misleading error:missing register/activate exportRelevant locations:
src/plugins/loader.ts(resolveSetupChannelRegistration, setup-only/setup-runtime branch)dist/extensions/feishu/setup-entry.jsdist/channel-entry-contract-*.js(defineBundledChannelSetupEntryreturnskind: "bundled-channel-setup-entry"+loadSetupPlugin)src/flows/channel-setup.ts(surfacesplugin not available)Notes
This likely affects other bundled channel plugins that use
defineBundledChannelSetupEntry(...), not just Feishu.