Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: iMessage attachments not coming through - permissions boundary for multi-agent setup [1 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#73625•Fetched 2026-04-29 06:17:15
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
aflo101aflo101
Participants
aflo101aflo101clawsweeper[bot]clawsweeper[bot]
Timeline (top)
closed ×1commented ×1labeled ×1

I am experiencing imessage attachments are no longer coming through once i setup a multi-agent deployment.

The image tool's allowed directory list is built per agent, using each agent's workspace directory as the base.

So:

• main can read from ~/.openclaw/state/workspace (my workspace) • user2 would get their own scoped roots based on workspace-user2

Neither agent gets /Users/<me>/Library/Messages/Attachments automatically — where the actual attachments live on my filesystem and where the bug lives.

Root Cause

I am experiencing imessage attachments are no longer coming through once i setup a multi-agent deployment.

The image tool's allowed directory list is built per agent, using each agent's workspace directory as the base.

So:

• main can read from ~/.openclaw/state/workspace (my workspace) • user2 would get their own scoped roots based on workspace-user2

Neither agent gets /Users/<me>/Library/Messages/Attachments automatically — where the actual attachments live on my filesystem and where the bug lives.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

I am experiencing imessage attachments are no longer coming through once i setup a multi-agent deployment.

The image tool's allowed directory list is built per agent, using each agent's workspace directory as the base.

So:

• main can read from ~/.openclaw/state/workspace (my workspace) • user2 would get their own scoped roots based on workspace-user2

Neither agent gets /Users/<me>/Library/Messages/Attachments automatically — where the actual attachments live on my filesystem and where the bug lives.

Steps to reproduce

Start Openclaw - with imessage channel configured and multi agents (tested with 2 workspaces) Send imessage to openclaw with attachment

Expected behavior

Openclaw uses the image tool to identify the attachments in the attachments directory - regardless of multi-agent boundaries.

Actual behavior

Neither agent gets /Users/<me>/Library/Messages/Attachments automatically — where the actual attachments live on the filesystem

OpenClaw version

2026.2.17

Operating system

macOS

Install method

No response

Model

claude-opus

Provider / routing chain

openclaw

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be resolved by configuring the image tool's allowed directory list to include the /Users/<me>/Library/Messages/Attachments path for each agent in the multi-agent deployment.

Guidance

  • Verify that the ~/Library/Messages/Attachments directory is accessible and contains the expected attachments.
  • Update the image tool's configuration to include the absolute path to the attachments directory for each agent, e.g., /Users/<me>/Library/Messages/Attachments.
  • Consider using a shared directory or a symbolic link to simplify the configuration and ensure consistency across agents.
  • Test the updated configuration by sending an iMessage with an attachment and verifying that the image tool can identify the attachment correctly.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The solution assumes that the image tool's configuration can be updated to include custom directories. If this is not possible, alternative solutions may be required.

Recommendation

Apply workaround: Update the image tool's configuration to include the absolute path to the attachments directory for each agent, as this is a more straightforward and immediate solution to the problem.

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

Openclaw uses the image tool to identify the attachments in the attachments directory - regardless of multi-agent boundaries.

#api#ssr#installation#tensor shape#autograd error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: iMessage attachments not coming through - permissions boundary for multi-agent setup [1 comments, 2 participants]