openclaw - 💡(How to fix) Fix [Bug] Slack inbound images broken in 2026.4.5 — speech-core/runtime-api.js resolution failure [1 participants]

Official PRs (…)
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.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62318Fetched 2026-04-08 03:06:07
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2

OpenClaw version: 2026.4.5 (3e72c03) Channel: Slack (socket mode) OS: Ubuntu 24 on AWS EC2 Node: 22.22.1

What happened: Slack images stopped being forwarded to the model. The agent receives the message but the image is never downloaded from Slack. The model either hallucinates a description or says it can't access the file.

Logs show:

  • Unable to resolve bundled plugin public surface speech-core/runtime-api.js
  • slack inbound debounce flush failed
  • [tools] image failed: Local media file not found
  • No download/fetch attempts visible in logs for inbound Slack files

What I tried:

  • Confirmed files:read scope and file_shared event subscription
  • Rolled back Node.js 22.22.2 → 22.22.1
  • Rolled back ffmpeg/libav packages to pre-upgrade versions
  • Reinstalled OpenClaw 2026.4.5 via npm (fixed speech-core crash but images still not downloaded)

What fixed it: Downgrading to OpenClaw 2026.3.28. Images work perfectly on that version.

Previous working version: 2026.3.28 Broken version: 2026.4.5

Error Message

  1. Check logs: no download/fetch attempt, speech-core/runtime-api.js resolution error on first attempt

Root Cause

OpenClaw version: 2026.4.5 (3e72c03) Channel: Slack (socket mode) OS: Ubuntu 24 on AWS EC2 Node: 22.22.1

What happened: Slack images stopped being forwarded to the model. The agent receives the message but the image is never downloaded from Slack. The model either hallucinates a description or says it can't access the file.

Logs show:

  • Unable to resolve bundled plugin public surface speech-core/runtime-api.js
  • slack inbound debounce flush failed
  • [tools] image failed: Local media file not found
  • No download/fetch attempts visible in logs for inbound Slack files

What I tried:

  • Confirmed files:read scope and file_shared event subscription
  • Rolled back Node.js 22.22.2 → 22.22.1
  • Rolled back ffmpeg/libav packages to pre-upgrade versions
  • Reinstalled OpenClaw 2026.4.5 via npm (fixed speech-core crash but images still not downloaded)

What fixed it: Downgrading to OpenClaw 2026.3.28. Images work perfectly on that version.

Previous working version: 2026.3.28 Broken version: 2026.4.5

Fix Action

Fix / Workaround

Steps to reproduce:

  1. Install OpenClaw 2026.4.5 via npm
  2. Configure Slack channel in socket mode with bot token
  3. Confirm files:read scope and file_shared bot event are set
  4. Send any image (PNG, JPG) to the bot via Slack DM
  5. Observe: agent responds but image is never downloaded — model hallucinates or says it can't access the file
  6. Check logs: no download/fetch attempt, speech-core/runtime-api.js resolution error on first attempt
  7. Downgrade to 2026.3.28 — images work immediately
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

OpenClaw version: 2026.4.5 (3e72c03) Channel: Slack (socket mode) OS: Ubuntu 24 on AWS EC2 Node: 22.22.1

What happened: Slack images stopped being forwarded to the model. The agent receives the message but the image is never downloaded from Slack. The model either hallucinates a description or says it can't access the file.

Logs show:

  • Unable to resolve bundled plugin public surface speech-core/runtime-api.js
  • slack inbound debounce flush failed
  • [tools] image failed: Local media file not found
  • No download/fetch attempts visible in logs for inbound Slack files

What I tried:

  • Confirmed files:read scope and file_shared event subscription
  • Rolled back Node.js 22.22.2 → 22.22.1
  • Rolled back ffmpeg/libav packages to pre-upgrade versions
  • Reinstalled OpenClaw 2026.4.5 via npm (fixed speech-core crash but images still not downloaded)

What fixed it: Downgrading to OpenClaw 2026.3.28. Images work perfectly on that version.

Previous working version: 2026.3.28 Broken version: 2026.4.5

Steps to reproduce

Steps to reproduce:

  1. Install OpenClaw 2026.4.5 via npm
  2. Configure Slack channel in socket mode with bot token
  3. Confirm files:read scope and file_shared bot event are set
  4. Send any image (PNG, JPG) to the bot via Slack DM
  5. Observe: agent responds but image is never downloaded — model hallucinates or says it can't access the file
  6. Check logs: no download/fetch attempt, speech-core/runtime-api.js resolution error on first attempt
  7. Downgrade to 2026.3.28 — images work immediately

Expected behavior

Expected behavior: When a user sends an image via Slack DM, the gateway should download the file from Slack's API using the bot token, encode it as base64, and pass it to the vision-capable model as part of the message context — as it does in version 2026.3.28.

Actual behavior

Actual behavior: The gateway receives the Slack message event but never downloads the attached file. The model is told an image exists but receives no image data. It either hallucinates a description of the image or responds saying it cannot access the file. Logs show zero download/fetch attempts for the Slack file URL.

OpenClaw version

2026.4.5 (3e72c03)

Operating system

2026.4.5 (3e72c03)

Install method

npm (global): npm install -g openclaw

Model

anthropic/claude-sonnet-4-20250514 (also tested with google/gemini-2.5-flash — same issue)

Provider / routing chain

Direct API (Anthropic + Google). No router. Primary: anthropic/claude-sonnet-4-20250514, fallbacks: google/gemini-2.5-flash, google/gemini-2.5-pro, google/gemini-3.1-flash

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.3.28 to resolve the issue with images not being downloaded from Slack.

Guidance

  • Verify that the files:read scope and file_shared event subscription are correctly configured in the Slack bot settings.
  • Check the logs for any errors related to the speech-core/runtime-api.js plugin, as this may be contributing to the issue.
  • Attempt to download the image manually using the Slack API and the bot token to isolate the issue.
  • Consider testing with a different model or provider to determine if the issue is specific to the current setup.

Example

No code snippet is provided as the issue seems to be related to a specific version of OpenClaw and its interaction with the Slack API.

Notes

The issue appears to be a regression introduced in OpenClaw version 2026.4.5, and downgrading to version 2026.3.28 resolves the issue. However, this may not be a permanent solution, and further investigation may be needed to identify the root cause.

Recommendation

Apply the workaround by downgrading to OpenClaw version 2026.3.28, as this has been confirmed to resolve the issue. This should be done until a fixed version of OpenClaw is released that addresses the regression.

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?
Loading…

FAQ

Expected behavior

Expected behavior: When a user sends an image via Slack DM, the gateway should download the file from Slack's API using the bot token, encode it as base64, and pass it to the vision-capable model as part of the message context — as it does in version 2026.3.28.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING