mirror of
https://github.com/openclaw/openclaw.git
synced 2026-05-06 07:40:44 +00:00
4013c65853
* fix(qqbot): enable qqbot plugin by default so runtime deps install before QR-code setup The qqbot plugin manifest was missing the enabledByDefault: true flag. Without it, ensureBundledPluginRuntimeDeps treats qqbot as bundled-but- disabled-by-default (isBundledPluginConfiguredForRuntimeDeps returns false when no qqbot channel/account is configured yet), so @tencent-connect/qqbot-connector is never installed into dist/extensions/qqbot/node_modules on first launch. This creates a chicken-and-egg failure for the QR-code binding flow: finalize.ts dynamically imports @tencent-connect/qqbot-connector to run qrConnect(), but the package isn't present yet because no account is configured — binding is exactly the step that configures the first account. Users hit: QQ Bot 绑定失败: Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@tencent-connect/qqbot-connector' imported from .../dist/extensions/qqbot/channel-*.js Adding enabledByDefault: true makes the host install qqbot's runtime deps eagerly on first launch, mirroring the pattern already used by mistral / groq / deepgram / amazon-bedrock-mantle and other bundled plugins whose providers must be available before any channel config exists. No code changes required; the existing runtime-deps install pipeline handles everything once the gate is opened. * fix(qqbot): changelog for enable-by-default fix (#71051) (thanks @cxyhhhhh) --------- Co-authored-by: sliverp <870080352@qq.com>