Summary

When an image is sent to OpenClaw via a channel (e.g. Telegram or iMessage), the image is correctly saved to media://inbound/ and processed by the AI model. However, the WebUI chat only displays a text placeholder (🖼️ Attached image) instead of rendering the actual image inline.

Steps to Reproduce

1. Send an image via Telegram or iMessage to the OpenClaw bot
2. OpenClaw receives the image, logs: Offloaded attachment. Saved: media://inbound/<filename>
3. The AI model processes and analyzes the image correctly
4. In the WebUI, the message shows 🖼️ Attached image — no preview is rendered

Expected Behavior

The WebUI should render the inbound image inline in the chat, similar to how other chat clients display received images.

Notes

• The files are physically stored at ~/.openclaw/media/inbound/
• The gateway HTTP server (port 18789) does not serve these files (returns 404)
• Image processing and AI analysis work correctly — this is purely a UI rendering issue
• A simple fix could be: serve media://inbound/ files via the gateway HTTP server (e.g. at /media/inbound/<filename>) and resolve media:// URIs to http://localhost:<port>/media/inbound/ in the WebUI

Environment

• OpenClaw: 2026.5.28 (e932160)
• macOS, gateway mode: local, port 18789