openclaw - 💡(How to fix) Fix [Bug] macOS WebChat screenshot shows locally but image not sent to AI [4 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#58876Fetched 2026-04-08 02:31:39
View on GitHub
Comments
4
Participants
2
Timeline
3
Reactions
0
Timeline (top)
commented ×3
RAW_BUFFERClick to expand / collapse

Environment

  • EasyClaw version: 1.3.28 (build 2026.3.30.307)
  • OS: macOS
  • Channel: WebChat (macOS Desktop App)

Problem Description

In EasyClaw macOS desktop app chat interface:

  1. Click the screenshot button, successfully capture screen
  2. Screenshot displays correctly in local chat (visible)
  3. After clicking send, AI completely cannot receive the image (only text message)

Steps to Reproduce

  1. Open EasyClaw macOS App
  2. Enter any agent conversation
  3. Click the screenshot button in chat box
  4. Screenshot displays correctly in dialog box
  5. Send message
  6. AI receives message without any image

Expected Behavior

Screenshot should be sent as image attachment along with message to AI backend

Initial Analysis

Local UI rendering works fine, but chat.send WebSocket message doesn't include image attachment data. Webchat frontend may not be correctly serializing/uploading images when sending.

extent analysis

TL;DR

Verify that the image attachment data is being correctly serialized and uploaded in the chat.send WebSocket message.

Guidance

  • Check the WebChat frontend code to ensure that the image attachment data is being properly handled and included in the chat.send WebSocket message.
  • Inspect the WebSocket message payload to confirm that the image data is being sent correctly.
  • Review the EasyClaw API documentation to ensure that the image attachment data is being formatted and sent according to the expected specifications.
  • Test the image sending functionality with a small image to rule out any potential issues with large file sizes.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The issue may be related to a bug in the WebChat frontend code or a misconfiguration of the EasyClaw API. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Modify the WebChat frontend code to correctly handle and include image attachment data in the chat.send WebSocket message, as this is the most likely cause of the issue.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING