Slack: Local image sends broken after 2026.2.26 update — LocalMediaAccessError
Slack: Local image sends broken after 2026.2.26 update — LocalMediaAccessErroSetup: Multi-agent, sandboxed agents (Docker), Slack via Socket Mode
Symptom: Since today's update (2026.2.26), agents can no longer send locally generated images via Slack. The MEDIA:/path/to/file.png response syntax returns:
LocalMediaAccessError: Local media path is not under an allowed directory:
/home/claw/.openclaw/workspace-elena/media/image.png
This worked fine before the update.
What I investigated:
mediaLocalRoots exists in config for BlueBubbles but not for Slack — the SlackAccountSchema uses .strict() and rejects the key, breaking gateway startup
The message tool with buffer (base64) parameter is a potential workaround, but sandboxed agents may have limited tool access
Questions:
Is there a supported way to whitelist local paths for Slack media sends in 2026.2.26?
Was the LocalMediaAccessError path check on Slack intentionally added in this release, or is it a regression?
Is mediaLocalRoots planned for the Slack adapter (like BlueBubbles has it)?
Happy to test patches. Thanks
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
