Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix [Bug]: Auxiliary title generation failed: HTTP 404: 404 page not found when using Minimax China [1 pull requests, 2 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
NousResearch/hermes-agent#17705•Fetched 2026-05-01 05:56:21
View on GitHub
Comments
2
Participants
2
Timeline
12
Reactions
0
Author
bgiraffebgiraffe
Participants
alt-glitchalt-glitchbgiraffebgiraffe
Timeline (top)
labeled ×5commented ×2cross-referenced ×2referenced ×2

Error Message

  1. When the agent reply, the error message come after no error message should be show error message pop

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Fixed

PR fix notes

PR #18026: test(auxiliary): guard raw-URL plumbing for Anthropic-compat endpoints (#17467)

Description (problem / solution / changelog)

Summary

Follow-up regression test suite for #17467 (merged as 4e296dcdd) — the fix for HTTP 404 errors on Anthropic-compatible auxiliary endpoints (MiniMax, MiniMax-CN, Kimi Coding, anthropic_messages custom proxies).

Closes:

  • #17705 — MiniMax-CN auxiliary title generation 404
  • #17413 — kimi-coding provider: auto selects broken fallback
  • #17086 — anthropic_messages custom endpoint URL rewrite strips /anthropic/
  • #10469 — CLI: OpenCode Go (minimax-m2.7) auxiliary client 404

What it guards

Two layers:

  1. Primitive-level (_endpoint_speaks_anthropic_messages, _maybe_wrap_anthropic) — confirms the detector returns True on raw /anthropic and False on rewritten /v1, and that the wrapper correctly rewraps plain OpenAI → AnthropicAuxiliaryClient only when given the raw URL.

  2. Call-site plumbing — exercises _resolve_api_key_provider() end-to-end with a simulated MiniMax pool entry and a simulated explicit-creds entry. Both must forward the RAW /anthropic URL to _maybe_wrap_anthropic. Reverting any of the 4 raw_base_url plumbing changes in #17467 produces a clear diagnostic failure:

    AssertionError: Explicit-creds path must forward RAW /anthropic URL.
Got: 'https://api.minimax.chat/v1'.

Regression guard validation

Planted the pre-fix code in agent/auxiliary_client.py:

  • Call-site tests: 2/2 FAIL with concrete diagnostic messages ✓
  • Primitive tests: correctly remain passing (they were always true at the helper level) ✓

Restored the fix: 12/12 pass ✓.

Test plan

  • scripts/run_tests.sh tests/agent/test_auxiliary_anthropic_url_preservation.py — 12/12 pass
  • Full related-tests sweep (219 tests across 9 files) — all green
  • Regression guard validated via plant-and-revert

Co-authored-by: oak [email protected]

Changed files

  • tests/agent/test_auxiliary_anthropic_url_preservation.py (added, +238/-0)

Code Example

Report       https://paste.rs/pRYhG                   agent.log    https://paste.rs/dTSrw                   gateway.log  https://paste.rs/2lGzt

---
RAW_BUFFERClick to expand / collapse

Bug Description

Fresh installed, every new chat that trigger Auxiliary title generation, it will reply a message "⚠ Auxiliary title generation failed: HTTP 404: 404 page not found"

Steps to Reproduce

  1. /new at Telegram or new chat in cli;
  2. Ask something
  3. When the agent reply, the error message come after

Expected Behavior

no error message should be show

Actual Behavior

error message pop

Affected Component

Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform (if gateway-related)

Telegram

Debug Report

Report       https://paste.rs/pRYhG                   agent.log    https://paste.rs/dTSrw                   gateway.log  https://paste.rs/2lGzt

Operating System

Debian GNU/Linux 12 (bookworm)

Python Version

Python: 3.11.2

Hermes Version

Hermes Agent v0.11.0 (2026.4.23)

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

extent analysis

TL;DR

The issue can likely be resolved by investigating and fixing the HTTP 404 error that occurs during Auxiliary title generation.

Guidance

  • Review the agent.log and gateway.log files (available at https://paste.rs/dTSrw and https://paste.rs/2lGzt respectively) to understand the context of the HTTP 404 error.
  • Verify the URL or endpoint used for Auxiliary title generation to ensure it is correct and accessible.
  • Check the Telegram API documentation to confirm if there are any specific requirements or restrictions for Auxiliary title generation.
  • Test the Auxiliary title generation process in isolation to determine if the issue is specific to the chat trigger or a more general problem.

Example

No code snippet is provided as the issue does not contain sufficient information about the implementation details.

Notes

The root cause of the issue is not explicitly stated, and the provided logs may contain more detailed information about the error. The fix may involve updating the endpoint URL, modifying the request headers, or handling the HTTP 404 error differently.

Recommendation

Apply workaround: Investigate and fix the HTTP 404 error to prevent the "Auxiliary title generation failed" message. This approach is recommended as it directly addresses the reported error and may resolve the issue without requiring a version upgrade or more extensive changes.

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…
#database connection#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