Repository navigation
Description
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
Version: 2026.4.26 → 2026.6.5Platform: Linux (Bluehost VPS), Slack channel via Socket Mode
What happened:
After updating to 2026.6.5 and restarting the gateway, the Slack channel silently stopped loading. Gateway reported "ready" with no errors. No Slack socket connection was established. The channel had been working fine on 2026.4.26.
Root cause (found manually):
The Slack plugin is installed at ~/.openclaw/npm/projects/openclaw-slack-*/. On 2026.4.26 it auto-loaded on startup. On 2026.6.5 it no longer auto-discovers from that path — only plugins in the extensions/ directory are picked up. Fix was to manually add plugins.allow: ["slack"] to config.
Two asks:
- Either restore backward-compat auto-discovery for npm-installed plugins, or document this as a breaking change with a migration step.
- If a configured channel (one with tokens/credentials in config) fails to load on startup, surface a loud warning — not a silent omission. Users have no way to know their channel is down until they try to use it.
Steps to reproduce
Repro path:
- Slack channel configured and working on 2026.4.26; plugins.allow not set in config
- npm install -g openclaw@latest → upgrades to 2026.6.5
- openclaw gateway restart
- Observe: startup log shows http server listening (N plugins: ...) — slack absent from list; no slack socket mode connected log entry; channel status shows SETUP
Confirmed fix: openclaw config set plugins.allow '["slack"]' + restart → slack appears in loaded plugins, socket connects.
Expected behavior
On 2026.4.26, Slack auto-loaded and connected without plugins.allow set. The expected behavior is that upgrading to 2026.6.5 preserves that — Slack loads on startup without requiring manual config changes.
Actual behavior
After upgrading to 2026.6.5 and restarting, Slack silently failed to load. Gateway logged http server listening (10 plugins: ...) with slack absent from the list. No slack socket mode connected entry appeared. Channel status showed SETUP. User received no messages and had no indication the channel was down until attempting to send.
OpenClaw version
2026.4.26 → 2026.6.5
Operating system
Linux — CentOS Stream 9 (5.14.0-687.12.1.el9_8.x86_64)
Install method
npm install -g openclaw — global npm install, running as a systemd user service on a Bluehost VPS.
Model
anthropic/claude-sonnet-4-6
Provider / routing chain
Direct — Anthropic API (api.anthropic.com), no proxy or router.
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
clawsweeper commentedon Jun 10, 2026
Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 21, 2026, 3:36 PM ET / 19:36 UTC.
Summary
Keep open: current main and the latest release still require explicit trust for configured non-bundled/global channel plugins, and the only direct fix attempts for this Slack upgrade regression are closed unmerged PRs.
Reproducibility: yes. Source inspection shows a configured global/non-bundled channel plugin without explicit trust is blocked from startup, and the startup logger does not surface that blocker; I did not run a live Slack upgrade.
Root-cause cluster
Relationship:
canonicalCanonical: #91873
Summary: This issue remains the canonical tracker for the Slack/global-plugin explicit-trust upgrade regression; related direct fix attempts are closed unmerged, and generic open plugin-warning work does not own the configured Slack startup blocker.
Members:
partial_overlap: fix(plugins): auto-enable non-bundled installed plugins when allowlist is empty #95056 - Closed unmerged PR targeted automatic loading of non-bundled installed plugins for this issue.partial_overlap: fix(gateway): warn at startup when a configured channel is blocked from loading #93657 - Closed unmerged PR targeted the loud startup-warning part of this issue.partial_overlap: fix: warn when previously installed plugin disappears from discovery (#91873) #94983 - Closed unmerged PR targeted a disappeared-plugin warning path related to this issue.adjacent_distinct: fix(issue): resolve #91873 [Bug]: Slack channel silently drops after upgrade to 2026.6. #92723 - Closed unmerged PR mentioned this issue but changed an unrelated release-helper path.adjacent_distinct: fix(issue): resolve #91873 [Bug]: Slack channel silently drops after upgrade to 2026.6. #92729 - Closed unmerged PR mentioned this issue but changed QA Lab runtime code rather than plugin startup or trust behavior.Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.
Next step
Manual review is needed before another fix PR because maintainers must choose between restoring implicit external-plugin loading and keeping fail-closed trust with migration/startup diagnostics.
Review details
Best possible solution:
Keep the fail-closed plugin trust boundary only if upgrade, doctor, startup, or status paths make blocked configured external channels impossible to miss; otherwise add a bounded compatibility migration or activation path for upgraded configured channels.
Do we have a high-confidence way to reproduce the issue?
Yes. Source inspection shows a configured global/non-bundled channel plugin without explicit trust is blocked from startup, and the startup logger does not surface that blocker; I did not run a live Slack upgrade.
Is this the best way to solve the issue?
Unclear on exact fix shape. Automatic re-enablement would address the compatibility regression but needs security/product approval; a migration plus startup/status warning is the safer path if fail-closed trust remains intentional.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
Codex review notes: model internal, reasoning high; reviewed against 6daf9307e0b9.
Label changes
Label changes:
clawsweeper:fix-shape-clear: Current issue advisory state no longer selects this label.Label justifications:
P1: A recent upgrade can leave a configured Slack messaging workflow unloaded without an operator-visible startup failure.impact:message-loss: When Slack does not load, inbound Slack messages and replies can be missed until the operator notices the channel is down.impact:other: The issue also affects external plugin startup and upgrade compatibility, a maintainer-visible surface outside the narrower owned impact labels.Evidence reviewed
What I checked:
channels.slackis configured. (src/plugins/gateway-startup-plugin-ids.ts:1861, 6daf9307e0b9)evaluateEffectiveChannelPluginreturnsblockedReason: "untrusted-plugin"for global or config-origin non-bundled channel owners unless the manifest owner is explicitly trusted. (src/plugins/channel-presence-policy.ts:251, 6daf9307e0b9)logGatewayStartupemits the model line, ready banner, log-file line, Nix notice, and dangerous-config warnings, but it does not call the configured-channel blocker scanner. (src/gateway/server-startup-log.ts:59, 6daf9307e0b9)external plugin "<id>" is installed without explicit trustwarnings for configured channel blockers, which supports the source reproduction but does not satisfy the gateway-startup warning ask. (src/commands/doctor/shared/channel-plugin-blockers.ts:337, 6daf9307e0b9)src/plugins/channel-plugin-ids.test.ts:2915, 6daf9307e0b9)src/plugins/gateway-startup-plugin-ids.ts:1861, c645ec4555c0)Likely related people:
src/plugins/gateway-startup-plugin-ids.ts,src/plugins/channel-presence-policy.ts,src/plugins/channel-plugin-ids.test.ts)src/commands/doctor/shared/channel-plugin-blockers.ts,src/commands/doctor/shared/channel-plugin-blockers.test.ts)src/plugins/gateway-startup-plugin-ids.ts,src/plugins/channel-plugin-ids.test.ts)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper autofix,@clawsweeper automerge,@clawsweeper fix ci, or@clawsweeper address review.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.steipete commentedon Jul 6, 2026
Fixed on current
mainby #96397 / 16b275a.The Gateway now checks configured channel ownership after startup and emits a warning when an external Slack plugin is installed but blocked by explicit trust. The warning names
channels.slackand gives the supported repair: enableplugins.entries.slack.enabled=true(and includeslackinplugins.allowwhen that restrictive allowlist is configured). The merged PR includes focused startup tests plus real Gateway proof for both blocked and trusted channel plugins.We are keeping the fail-closed external-plugin trust boundary; the supported alternative to implicit loading is explicit enablement with a visible startup diagnostic. The current latest release, v2026.6.11, predates this merge, so the warning will appear in the next release containing the commit above.
Closing as fixed on
main. Thanks for the clear upgrade report—it directly motivated the startup diagnostic.