Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix Slack connector silently drops file attachments in DM messages [3 pull requests, 2 comments, 2 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#50129•Fetched 2026-04-08 00:58:51
View on GitHub
Comments
2
Participants
2
Timeline
11
Reactions
0
Author
warren-t-c[bot]warren-t-c[bot]
Participants
Hollychou924Hollychou924warren-t-c[bot]warren-t-c[bot]
Timeline (top)
referenced ×7commented ×2cross-referenced ×2

Error Message

The Slack connector receives the text content of DM messages but silently drops file attachments. Files uploaded directly in a DM conversation are never downloaded to the media cache (~/.openclaw/media/inbound/), and no error or warning is logged.

  • No error or warning in gateway logs (journalctl --user -u openclaw-gateway.service)
  • The mediaMaxMb config defaults to 20MB, but no size-related error was logged even for attempts — suggesting the download is never attempted, not that it fails on size

Fix Action

Workaround

Upload files directly to the server via scp and process manually.

PR fix notes

PR #50200: fix(slack): fetch fresh download URL via files.info for DM file attachments

Description (problem / solution / changelog)

Summary

Slack DM message events may omit url_private_download and url_private on file objects in the event payload, causing all DM file attachments to be silently dropped — no download attempt, no error logged.

Root cause: resolveSlackMedia only checked file.url_private_download ?? file.url_private and returned null when both were missing. The existing downloadSlackFile in actions.ts already solved this by calling files.info to fetch fresh metadata, but the inbound message pipeline did not.

Fix: When both URLs are missing but file.id is present and a Slack WebClient is available, call files.info to retrieve a fresh download URL before giving up. This matches the pattern already used by downloadSlackFile.

Changes

  • extensions/slack/src/monitor/media.ts: Add optional client param to resolveSlackMedia and resolveSlackAttachmentContent; call files.info as fallback when download URLs are missing
  • extensions/slack/src/monitor/message-handler/prepare-content.ts: Pass client through to media resolvers
  • extensions/slack/src/monitor/message-handler/prepare.ts: Pass ctx.app.client to resolveSlackMessageContent
  • extensions/slack/src/monitor/message-handler/prepare-thread-context.ts: Pass client to thread starter media resolution
  • 3 new tests covering: successful fallback, fallback with no URL in files.info, and files.info API failure

Test plan

  • pnpm test:extensions — all 2680 tests pass (including 3 new tests)
  • pnpm tsgo — no type errors
  • Manual: send a file attachment via Slack DM and verify it appears in ~/.openclaw/media/inbound/

Closes #50129

Changed files

  • extensions/slack/src/monitor/media.test.ts (modified, +77/-0)
  • extensions/slack/src/monitor/media.ts (modified, +17/-1)
  • extensions/slack/src/monitor/message-handler/prepare-content.ts (modified, +3/-0)
  • extensions/slack/src/monitor/message-handler/prepare-thread-context.ts (modified, +1/-0)
  • extensions/slack/src/monitor/message-handler/prepare.ts (modified, +1/-0)

PR #1: fix(slack): reliably ingest Slack file images instead of filename placeholders

Description (problem / solution / changelog)

Summary

Fixes Slack inbound file/image ingestion regressions end-to-end (including Errol runtime validation):

  • Use files.info hydration when Slack events include file id without usable download URLs.
  • Use the correct media-read token path (userToken fallback) in monitor context, so file reads are not restricted to bot-token-only paths.
  • Harden Slack media fetch init handling to avoid passing incompatible fetch guard hook options into Node fetch, which caused silent download failure + filename-only placeholders.
  • Ensure staged inbound media filenames are unique across turns to avoid cross-turn collisions.
  • Add regression tests for id-only payload hydration and sandbox media staging collisions.

Validation

  • pnpm vitest extensions/slack/src/monitor/media.test.ts --run
  • pnpm vitest extensions/slack/src/monitor/message-handler/prepare.test.ts --run
  • pnpm vitest extensions/slack/src/monitor/message-handler/prepare-thread-context.test.ts --run
  • pnpm vitest src/auto-reply/reply.triggers.trigger-handling.stages-inbound-media-into-sandbox-workspace.test.ts --run
  • Live Errol Docker verification in Slack thread: image content now resolved (not placeholder-only filename).

AI assistance

This PR was AI-assisted (Hedwig/OpenClaw + Codex) and then validated with targeted tests and live runtime verification.

Related Slack file issues (tagging all matches)

Refs #50129 Refs #51050 Refs #62088 Refs #51458 Refs #62623 Refs #62551 Refs #61862 Refs #41657 Refs #45574 Refs #61850 Refs #36507 Refs #13634 Refs #44544 Refs #38457 Refs #47600 Refs #56508 Refs #52962 Refs #18426 Refs #62218 Refs #33368 Refs #15087 Refs #18642 Refs #7536 Refs #24681 Refs #23349 Refs #29304 Refs #7110 Refs #13740 Refs #15190 Refs #3595 Refs #3519 Refs #14258 Refs #6008

Changed files

  • extensions/slack/src/monitor/context.ts (modified, +3/-0)
  • extensions/slack/src/monitor/media.test.ts (modified, +58/-1)
  • extensions/slack/src/monitor/media.ts (modified, +84/-18)
  • extensions/slack/src/monitor/message-handler/prepare-thread-context.test.ts (modified, +109/-0)
  • extensions/slack/src/monitor/message-handler/prepare-thread-context.ts (modified, +30/-11)
  • extensions/slack/src/monitor/message-handler/prepare.ts (modified, +1/-1)
  • extensions/slack/src/monitor/monitor.media.test.ts (modified, +41/-2)
  • extensions/slack/src/monitor/provider.ts (modified, +1/-0)
  • src/auto-reply/reply.triggers.trigger-handling.stages-inbound-media-into-sandbox-workspace.test.ts (modified, +42/-6)
  • src/auto-reply/reply/stage-sandbox-media.ts (modified, +11/-4)

PR #62792: Fix Slack file access in channels and DMs

Description (problem / solution / changelog)

  • Tooling note: AI-assisted development (Hedwig/OpenClaw + Codex), with human validation and final review by @armsteadj1.

Summary

Describe the problem and fix in 2–5 bullets:

If this PR fixes a plugin beta-release blocker, title it fix(<plugin-id>): beta blocker - <summary> and link the matching Beta blocker: <plugin-name> - <summary> issue labeled beta-blocker. Contributors cannot label PRs, so the title is the PR-side signal for maintainers and automation.

  • Problem: Slack inbound image/file messages sometimes reached the model as filename placeholders only ([Slack file: IMG_4935.jpg]) instead of actual media content.
  • Why it matters: Image understanding and downstream workflows fail, causing repeated user retries and broken Slack UX.
  • What changed: Fixes the reproduced Slack filename-placeholder regression in this media ingestion path by hardening Slack media hydration/fetch, using the resolved media-read token path, and preventing cross-turn staged filename collisions.
  • What did NOT change (scope boundary): No UI changes, no outbound Slack behavior changes, and no claim that every historical Slack-file issue is resolved.

Change Type (select all)

  • Bug fix
  • Feature
  • Refactor required for the fix
  • Docs
  • Security hardening
  • Chore/infra

Scope (select all touched areas)

  • Gateway / orchestration
  • Skills / tool execution
  • Auth / tokens
  • Memory / storage
  • Integrations
  • API / contracts
  • UI / DX
  • CI/CD / infra

Linked Issue/PR

  • Closes #50129
  • Related #51050
  • Related #51458
  • Related #62088
  • This PR fixes a bug or regression

Root Cause (if applicable)

For bug fixes or regressions, explain why this happened, not just what changed. Otherwise write N/A. If the cause is unclear, write Unknown.

  • Root cause: Slack file events can arrive with partial metadata and restricted URL access semantics; combined with brittle media fetch init handling and token-read path selection, the ingestion path sometimes failed and fell back to filename placeholders.
  • Missing detection / guardrail: Tests did not lock in this specific Slack file metadata/token-read + staged-media collision path.
  • Contributing context (if known): Threaded Slack flows with repeated filenames and file payload variation increased failure probability.

Regression Test Plan (if applicable)

For bug fixes or regressions, name the smallest reliable test coverage that should catch this. Otherwise write N/A.

  • Coverage level that should have caught this:
    • Unit test
    • Seam / integration test
    • End-to-end test
    • Existing coverage already sufficient
  • Target test or file:
    • extensions/slack/src/monitor/media.test.ts
    • extensions/slack/src/monitor/message-handler/prepare.test.ts
    • extensions/slack/src/monitor/message-handler/prepare-thread-context.test.ts
    • src/auto-reply/reply.triggers.trigger-handling.stages-inbound-media-into-sandbox-workspace.test.ts
  • Scenario the test should lock in: Slack file events with partial metadata still produce real media payloads, and repeated inbound basenames across turns do not collide.
  • Why this is the smallest reliable guardrail: It exercises the failing boundary directly without requiring a full external Slack E2E harness.
  • Existing test that already covers this (if any): Existing Slack media/prepare coverage exists; this PR extends edge-path coverage.
  • If no new test is added, why not: N/A

User-visible / Behavior Changes

List user-visible changes (including defaults/config). If none, write None.

Slack image/file messages now resolve as actual media content more reliably in the affected ingestion path instead of filename-only placeholders.

Diagram (if applicable)

For UI changes or non-trivial logic flows, include a small ASCII diagram reviewers can scan quickly. Otherwise write N/A.

Before:
[Slack file event] -> [media fetch/hydration path fails] -> [placeholder only]

After:
[Slack file event] -> [robust hydration + read-token path + safe fetch init] -> [media staged] -> [model sees image]New permissions/capabilities? (No)Secrets/tokens handling changed? (Yes)New/changed network calls? (No)Command/tool execution surface changed? (No)Data access scope changed? (No)If any Yes, explain risk + mitigation:Risk: token selection for Slack media reads changed in this path.Mitigation: constrained to existing configured Slack token sources and media-read flow only; no new secret source or broader access added.OS: macOS host + Docker runtimeRuntime/container: Errol gateway in Docker (openclaw:local)Model/provider: openai-codex/gpt-5.3-codex (Errol runtime default)Integration/channel (if any): Slack (threaded channel flow)Relevant config (redacted): Slack bot/app tokens configured; Errol isolated config/workspace/port.Send Slack thread message with attached image (same repro case where response only saw filename placeholder).Observe pre-fix behavior (placeholder-only).Apply fix branch, rebuild/restart Errol, resend same image flow.Assistant can access and reason over actual image content.Before: placeholder-only behavior reproduced.After: image content was successfully resolved and identified.Attach at least one:Failing test/log before + passing afterTrace/log snippetsScreenshot/recordingPerf numbers (if relevant)What you personally verified (not just CI), and how:Verified scenarios:Reproduced filename-placeholder failure in live Slack thread.Verified post-fix behavior resolved actual image content in same thread flow.Edge cases checked:Slack file metadata hydration path.Repeated inbound basename staging across turns.What you did not verify:Broad claim across all historical Slack-file issues.Full multi-workspace/perf matrix beyond this runtime path.I replied to or resolved every bot review conversation I addressed in this PR.I left unresolved only the conversations that still need reviewer or maintainer judgment.If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.Backward compatible? (Yes)Config/env changes? (No)Migration needed? (No)If yes, exact upgrade steps:List only real risks for this PR. Add/remove entries as needed. If none, write None.Risk:Slack tenant/app-specific file payload variance may expose additional untested edge cases.Mitigation:Coverage added for the reproduced edge path and constrained changes to Slack media ingestion only.Risk:Token-read path change could behave differently in uncommon token setups.Mitigation:Uses existing resolved read-token path with fallback; no new token source introduced.

## Changed files

- `extensions/slack/src/monitor/context.ts` (modified, +3/-0)
- `extensions/slack/src/monitor/media.test.ts` (modified, +173/-0)
- `extensions/slack/src/monitor/media.ts` (modified, +204/-36)
- `extensions/slack/src/monitor/message-handler/prepare-content.ts` (modified, +3/-0)
- `extensions/slack/src/monitor/message-handler/prepare-thread-context.test.ts` (modified, +109/-0)
- `extensions/slack/src/monitor/message-handler/prepare-thread-context.ts` (modified, +37/-11)
- `extensions/slack/src/monitor/message-handler/prepare.ts` (modified, +2/-0)
- `extensions/slack/src/monitor/monitor.media.test.ts` (modified, +41/-2)
- `extensions/slack/src/monitor/provider.ts` (modified, +1/-0)
- `src/auto-reply/reply.triggers.trigger-handling.stages-inbound-media-into-sandbox-workspace.test.ts` (modified, +66/-6)
- `src/auto-reply/reply/stage-sandbox-media.ts` (modified, +39/-4)
- `src/commands/agent-via-gateway.test.ts` (modified, +25/-26)
RAW_BUFFERClick to expand / collapse

Bug Description

The Slack connector receives the text content of DM messages but silently drops file attachments. Files uploaded directly in a DM conversation are never downloaded to the media cache (~/.openclaw/media/inbound/), and no error or warning is logged.

Steps to Reproduce

  1. Send a file attachment (e.g., .mp4 video) via Slack DM to the bot
  2. The text of the message is received and processed normally
  3. The file attachment is silently ignored — no download attempt, no log entry

Expected Behavior

File attachments in DM messages should be:

  1. Detected from the Slack event payload (files array)
  2. Downloaded via authenticated Slack URL (url_private_download with bot token)
  3. Saved to the media cache (~/.openclaw/media/inbound/)
  4. Made available to the agent session as an attachment reference

Actual Behavior

  • Message text arrives normally
  • File attachments are completely ignored
  • No error or warning in gateway logs (journalctl --user -u openclaw-gateway.service)
  • The ~/.openclaw/media/inbound/ directory shows no new files after sending attachments
  • Confirmed via Slack API that the files exist on the message — the Slack side is correct

Environment

  • OpenClaw Gateway (latest, systemd user service)
  • Channel: Slack (DM conversation)
  • File tested: .mp4 video (~456MB), sent 3 times
  • OS: Ubuntu 24.04, ARM64 (DGX Spark)

Investigation Notes

  • The inbound media directory contains PDFs, PNGs, and other files from earlier channel messages, so the media pipeline works in general
  • The issue appears specific to DM file attachments (or possibly all Slack file attachments depending on how they are sent)
  • The mediaMaxMb config defaults to 20MB, but no size-related error was logged even for attempts — suggesting the download is never attempted, not that it fails on size
  • Gateway logs around the time of file sends show only [skills] Skipping skill path that resolves outside its configured root — no media-related entries at all

Workaround

Upload files directly to the server via scp and process manually.

Impact

Blocks automated processing of file-based workflows (e.g., video ingestion for meeting transcription, document intake from Slack) where users send files in DM or channel conversations.

extent analysis

Fix Plan

To resolve the issue of silently dropped file attachments in Slack DM messages, we need to modify the Slack connector to properly handle file downloads. Here are the steps:

  • Update the Slack event handler to check for the files array in the event payload.
  • Use the url_private_download field with the bot token to download the file.
  • Save the downloaded file to the media cache (~/.openclaw/media/inbound/).

Example code snippet:

import requests

# ...

def handle_slack_event(event):
    # ...
    if 'files' in event:
        for file in event['files']:
            file_url = file['url_private_download']
            file_token = 'xoxb-' + bot_token  # assuming bot_token is defined
            headers = {'Authorization': f'Bearer {file_token}'}
            response = requests.get(file_url, headers=headers, stream=True)
            if response.status_code == 200:
                file_path = f'~/.openclaw/media/inbound/{file["name"]}'
                with open(file_path, 'wb') as f:
                    for chunk in response.iter_content(1024):
                        f.write(chunk)
                # Make the file available to the agent session as an attachment reference
                # ...
            else:
                # Log the error
                print(f'Error downloading file: {response.status_code}')
    # ...

Verification

To verify that the fix worked, send a file attachment via Slack DM to the bot and check that:

  • The file is downloaded to the media cache (~/.openclaw/media/inbound/).
  • The file is made available to the agent session as an attachment reference.
  • No error or warning is logged in the gateway logs (journalctl --user -u openclaw-gateway.service).

Extra Tips

  • Make sure to handle large files properly by using a streaming download approach to avoid loading the entire file into memory.
  • Consider adding logging and error handling to ensure that any issues with file downloads are properly reported and handled.

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…
#api#ssr#installation#tensor shape#autograd error#docker error#permission error#memory optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING