Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Bug]: Vision routing issue in Hermes Agent v0.14.x with MiniMax custom provider

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…

Error Message

Operating System

Ubuntu 24.04

Python Version

No response

Hermes Version

No response

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Code Example

auxiliary:
  vision:
    base_url: [https://api.minimaxi.com/v1](https://api.minimaxi.com/v1)

### Expected Behavior

The agent should correctly identify the custom provider as `minimax-cn` or apply the Anthropic image block schema transformation so MiniMax can parse the image successfully.

### Actual Behavior

The provider is resolved as `custom`, skipping `_convert_openai_images_to_anthropic(...)`. Standard OpenAI image schema is sent, which MiniMax silently ignores (input tokens remain around 14, and dashboard image quota remains 0).

### Affected Component

Configuration (config.yaml, .env, hermes setup)

### Messaging Platform (if gateway-related)

_No response_

### Debug Report

---

### Operating System

Ubuntu 24.04

### Python Version

_No response_

### Hermes Version

_No response_

### Additional Logs / Traceback (optional)
RAW_BUFFERClick to expand / collapse

Bug Description

Text generation works correctly, but vision/image understanding fails silently. The model responds with "I cannot see the uploaded image" while the HTTP request itself succeeds (200 OK).

Steps to Reproduce

  1. Configure custom provider with MiniMax base_url in config.yaml:
auxiliary:
  vision:
    base_url: [https://api.minimaxi.com/v1](https://api.minimaxi.com/v1)

### Expected Behavior

The agent should correctly identify the custom provider as `minimax-cn` or apply the Anthropic image block schema transformation so MiniMax can parse the image successfully.

### Actual Behavior

The provider is resolved as `custom`, skipping `_convert_openai_images_to_anthropic(...)`. Standard OpenAI image schema is sent, which MiniMax silently ignores (input tokens remain around 14, and dashboard image quota remains 0).

### Affected Component

Configuration (config.yaml, .env, hermes setup)

### Messaging Platform (if gateway-related)

_No response_

### Debug Report

```shell
Report   https://paste.rs/abc123
agent.log   https://paste.rs/def456
gateway.log   https://paste.rs/ghi789

Operating System

Ubuntu 24.04

Python Version

No response

Hermes Version

No response

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

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