Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix image tool: MiniMax API returns 'chat content is empty (2013)' when processing iMessage images [1 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#63236•Fetched 2026-04-09 07:56:30
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
renxiangtwrenxiangtw
Participants
renxiangtwrenxiangtw

Error Message

Image resized to fit limits: 2142x2296px 312.6KB -> 66.1KB (-78.9%)  // Image is received and resized
Image model failed (minimax/MiniMax-M2.7): 400 {...2013...}  // But MiniMax API fails

Code Example

Image model failed (minimax/MiniMax-M2.7): 400 {"type":"error","error":{"type":"invalid_request_error","message":"invalid params, chat content is empty (2013)"}}

---

Image resized to fit limits: 2142x2296px 312.6KB -> 66.1KB (-78.9%)  // Image is received and resized
Image model failed (minimax/MiniMax-M2.7): 400 {...2013...}  // But MiniMax API fails
RAW_BUFFERClick to expand / collapse

Bug Description

When receiving images via iMessage channel, the image tool fails with:

Image model failed (minimax/MiniMax-M2.7): 400 {"type":"error","error":{"type":"invalid_request_error","message":"invalid params, chat content is empty (2013)"}}

Steps to Reproduce

  1. Receive an image via iMessage channel
  2. Try to analyze the image with the image tool
  3. Get error 2013

Environment

  • OpenClaw: 2026.4.8 (9ece252)
  • Model: minimax/MiniMax-M2.7 / M2.7-highspeed
  • Channel: iMessage

Technical Details

  • Images are downloaded to: /Users/renxiang/.openclaw/media/inbound/
  • The OSS URL format: https://minimax-algeng-chat-tts.oss-cn-wulanchabu.aliyuncs.com/...
  • When MiniMax API receives the OSS URL, it returns 2013 error
  • The URL appears to be an internal Alibaba Cloud URL that may not be accessible from MiniMax's servers

Attempted Fixes

  • Setting tools.media.image.enabled: true — did not help
  • Passing local file path directly — same error
  • Manual OSS URL access — returns 403 (expired signature)

Expected Behavior

The image tool should successfully analyze images received via iMessage.

Logs

Image resized to fit limits: 2142x2296px 312.6KB -> 66.1KB (-78.9%)  // Image is received and resized
Image model failed (minimax/MiniMax-M2.7): 400 {...2013...}  // But MiniMax API fails

extent analysis

TL;DR

The most likely fix is to ensure the OSS URL is accessible from MiniMax's servers or to use a different image processing endpoint that can handle internal Alibaba Cloud URLs.

Guidance

  • Verify that the OSS URL is accessible from the MiniMax API servers by checking the URL's access controls and permissions.
  • Consider using a proxy server or a different image processing endpoint that can handle internal Alibaba Cloud URLs.
  • Check the expiration time of the OSS URL signature and ensure it is not expired when passing it to the MiniMax API.
  • Test the image analysis with a publicly accessible image URL to isolate the issue.

Example

No code snippet is provided as the issue seems to be related to the accessibility of the OSS URL.

Notes

The issue may be specific to the MiniMax API and its ability to access internal Alibaba Cloud URLs. The fix may require coordination with the MiniMax API team or the use of a different image processing endpoint.

Recommendation

Apply a workaround by using a proxy server or a different image processing endpoint that can handle internal Alibaba Cloud URLs, as upgrading to a fixed version is not mentioned in 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…
#api#vector store#embedding generation#cache error#pipeline 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