fix(plugins): auto-enable non-bundled installed plugins when allowlist is empty

mmyzwl · mmyzwl · commit 0ce2f986684c · 2026-06-20T01:42:31.000+08:00
When plugins.allow is empty (no restrictive allowlist), non-bundled installed plugins like npm-installed Slack should be enabled by default. Previously only bundled plugins whose channel was configured received auto-enablement; non-bundled plugins fell through to implicit disabled, requiring users to manually add them to plugins.allow even when no allowlist restriction was in place. Fixes #91873
diff --git a/src/plugins/config-activation-shared.ts b/src/plugins/config-activation-shared.ts
@@ -260,6 +260,25 @@ export function resolvePluginActivationDecisionShared<TRootConfig>(params: {
       cause: "enabled-by-effective-config",
     };
   }
+  // FIX #91873: When plugins.allow is empty (no restrictive allowlist),
+  // non-bundled installed plugins (e.g. npm-installed Slack) should be
+  // enabled by default — matching the auto-load behavior before 2026.6.5.
+  // Without this, non-bundled plugins with no explicit entry in config fall
+  // through to implicit disabled, requiring users to manually add them to
+  // plugins.allow even though no allowlist restriction is in place.
+  if (
+    params.origin !== "bundled" &&
+    params.origin !== "workspace" &&
+    params.config.allow.length === 0
+  ) {
+    return {
+      enabled: true,
+      activated: true,
+      explicitlyEnabled: false,
+      source: "default",
+      cause: "non-bundled-auto-enable",
+    };
+  }
   if (
     params.origin === "bundled" &&
     params.isBundledChannelEnabledByChannelConfig(params.rootConfig, params.id)
