openclaw - 💡(How to fix) Fix Slack channel never initialises on v2026.3.28 — no socket connection, channel absent from status [2 comments, 1 participants]

herby101 · 2026-03-31T01:52:12Z

[openclaw] Slack channel does not initialise at all on v2026.3.28. Fresh app, clean config, correct tokens — gateway boots fine but Slack never appears in open… Slack channel does not initialise at all on v2026.3.28. Fresh app, clean config, correct tokens — gateway boots fine but Slack never appears in `openclaw status` channels table and there are zero Slack-related log entries after startup. ## Summary Slack channel does not initialise at all on v2026.3.28. Fresh app, clean config, correct tokens — gateway boots fine but Slack never appears in `openclaw status` channels table and there are zero Slack-related log entries after startup. ## Environment - OpenClaw: 2026.3.28 (f9b1079) - macOS: 26.2 (arm64) - Node: 25.8.1 - Install: npm global (`/opt/homebrew/lib/node_modules/openclaw`) ## Steps to reproduce 1. Create a fresh Slack app (Socket Mode, new bot + app tokens) 2. Add correct config to `openclaw.json`: ```json { "channels": { "slack": { "enabled": true, "mode": "socket", "botToken": "xoxb-...", "appToken": "xapp-...", "dmPolicy": "allowlist", "groupPolicy": "allowlist", "allowFrom": ["U1EAGPZJ8"], "streaming": "partial", "nativeStreaming": true, "ackReaction": "👀" } } } ``` 3. Restart gateway (`openclaw gateway restart`) 4. Run `openclaw status` ## Expected Slack channel appears in channels table, socket connects, log shows socket mode init. ## Actual - Channels table in `openclaw status` is **completely empty** - `openclaw channels status --probe` returns nothing - Gateway startup log has **zero Slack-related entries** — no connection attempt, no error, no socket init, no extension load - `openclaw doctor` reports no Slack warnings/errors (it doesn't know Slack is configured) ## Startup log (relevant section — no Slack entries) Gateway boots cleanly, LCM loads, webchat connects, cron starts — but nothing for Slack: ``` [gateway] listening on ws://127.0.0.1:18789 (PID 77782) [gateway] qmd memory startup initialization armed for agent "main" [gateway/ws] webchat connected [cron] started (enabled=true, jobs=14) [gateway] agent model: anthropic/claude-sonnet-4-6 ``` No `slack`, `socket`, `xapp`, `bolt`, or channel init entries at any point post-restart. ## Additional context - Previously worked before v2026.3.27 update - Updated to v2026.3.28 via `sudo npm i -g openclaw@latest` - Tried: full clean wipe of Slack config + tokens, created brand new Slack app, fresh xoxb + xapp tokens, verified config in `openclaw.json`, restarted gateway — same result every time - Slack extension files exist at `/opt/homebrew/lib/node_modules/openclaw/dist/extensions/slack/` - Related to / possibly same root cause as #54777 (setSlackRuntime never called)

openclaw2026-03-31 01:52:12

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#58052•Fetched 2026-04-08 01:54:30

View on GitHub

Comments

Participants

Timeline

Reactions

Author

herby101

Participants

herby101

Timeline (top)

commented ×2closed ×1locked ×1

Slack channel does not initialise at all on v2026.3.28. Fresh app, clean config, correct tokens — gateway boots fine but Slack never appears in openclaw status channels table and there are zero Slack-related log entries after startup.

Error Message

Gateway startup log has zero Slack-related entries — no connection attempt, no error, no socket init, no extension load

Root Cause

Previously worked before v2026.3.27 update
Updated to v2026.3.28 via sudo npm i -g openclaw@latest
Tried: full clean wipe of Slack config + tokens, created brand new Slack app, fresh xoxb + xapp tokens, verified config in openclaw.json, restarted gateway — same result every time
Slack extension files exist at /opt/homebrew/lib/node_modules/openclaw/dist/extensions/slack/
Related to / possibly same root cause as #54777 (setSlackRuntime never called)

Code Example

{
  "channels": {
    "slack": {
      "enabled": true,
      "mode": "socket",
      "botToken": "xoxb-...",
      "appToken": "xapp-...",
      "dmPolicy": "allowlist",
      "groupPolicy": "allowlist",
      "allowFrom": ["U1EAGPZJ8"],
      "streaming": "partial",
      "nativeStreaming": true,
      "ackReaction": "👀"
    }
  }
}

---

[gateway] listening on ws://127.0.0.1:18789 (PID 77782)
[gateway] qmd memory startup initialization armed for agent "main"
[gateway/ws] webchat connected
[cron] started (enabled=true, jobs=14)
[gateway] agent model: anthropic/claude-sonnet-4-6

RAW_BUFFERClick to expand / collapse

Summary

Environment

OpenClaw: 2026.3.28 (f9b1079)
macOS: 26.2 (arm64)
Node: 25.8.1
Install: npm global (/opt/homebrew/lib/node_modules/openclaw)

Steps to reproduce

Create a fresh Slack app (Socket Mode, new bot + app tokens)
Add correct config to openclaw.json:

{
  "channels": {
    "slack": {
      "enabled": true,
      "mode": "socket",
      "botToken": "xoxb-...",
      "appToken": "xapp-...",
      "dmPolicy": "allowlist",
      "groupPolicy": "allowlist",
      "allowFrom": ["U1EAGPZJ8"],
      "streaming": "partial",
      "nativeStreaming": true,
      "ackReaction": "👀"
    }
  }
}

Restart gateway (openclaw gateway restart)
Run openclaw status

Expected

Slack channel appears in channels table, socket connects, log shows socket mode init.

Actual

Channels table in openclaw status is completely empty
openclaw channels status --probe returns nothing
Gateway startup log has zero Slack-related entries — no connection attempt, no error, no socket init, no extension load
openclaw doctor reports no Slack warnings/errors (it doesn't know Slack is configured)

Startup log (relevant section — no Slack entries)

Gateway boots cleanly, LCM loads, webchat connects, cron starts — but nothing for Slack:

[gateway] listening on ws://127.0.0.1:18789 (PID 77782)
[gateway] qmd memory startup initialization armed for agent "main"
[gateway/ws] webchat connected
[cron] started (enabled=true, jobs=14)
[gateway] agent model: anthropic/claude-sonnet-4-6

No slack, socket, xapp, bolt, or channel init entries at any point post-restart.

Additional context

Previously worked before v2026.3.27 update
Updated to v2026.3.28 via sudo npm i -g openclaw@latest
Tried: full clean wipe of Slack config + tokens, created brand new Slack app, fresh xoxb + xapp tokens, verified config in openclaw.json, restarted gateway — same result every time
Slack extension files exist at /opt/homebrew/lib/node_modules/openclaw/dist/extensions/slack/
Related to / possibly same root cause as #54777 (setSlackRuntime never called)

extent analysis

Fix Plan

To resolve the issue with the Slack channel not initializing, we need to ensure that the Slack extension is properly loaded and configured.

Verify Slack Extension: Confirm that the Slack extension files exist in the correct directory: /opt/homebrew/lib/node_modules/openclaw/dist/extensions/slack/.
Check Configuration: Ensure the openclaw.json configuration file has the correct Slack settings, as shown in the issue body.
Update Code: It seems like the setSlackRuntime function is not being called. We need to modify the code to call this function when the gateway starts.

Here's an example of how you can modify the gateway.js file to call setSlackRuntime:

// gateway.js
const slackExtension = require('./extensions/slack');

// ...

async function startGateway() {
  // ...
  await slackExtension.setSlackRuntime();
  // ...
}

startGateway();

Restart Gateway: After making the code changes, restart the gateway using openclaw gateway restart.

Verification

To verify that the fix worked, run openclaw status and check if the Slack channel appears in the channels table. Also, check the gateway startup log for Slack-related entries.

Extra Tips

Make sure to update the openclaw package to the latest version using sudo npm i -g openclaw@latest.
If the issue persists, try deleting the node_modules directory and running npm install again to ensure all dependencies are up-to-date.
Refer to the OpenClaw documentation for more information on configuring and troubleshooting the Slack extension.

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?

#installation #tensor shape #autograd error #model save/load #optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Data

Security

Network

Code

UI/UX

Text

System

Multimedia

Protocol

API

Engineering

openclaw - 💡(How to fix) Fix Slack channel never initialises on v2026.3.28 — no socket connection, channel absent from status [2 comments, 1 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Code Example

Summary

Environment

Steps to reproduce

Expected

Actual

Startup log (relevant section — no Slack entries)

Additional context

extent analysis

Fix Plan

Verification

Extra Tips

Still need to ship something?

TRENDING

openclaw - 💡(How to fix) Fix Slack channel never initialises on v2026.3.28 — no socket connection, channel absent from status [2 comments, 1 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Code Example

Summary

Environment

Steps to reproduce

Expected

Actual

Startup log (relevant section — no Slack entries)

Additional context

extent analysis

Fix Plan

Verification

Extra Tips

Still need to ship something?

RELATED_DISCOVERY

TRENDING