NousResearch/hermes-agent

Auxiliary client base_url and api_mode handling for custom endpoints

Cluster 16254 · agent. Data as of 2026-10-24 20:38 UTC

Nothing open on GitHub. Fix merged in #85466 on 13 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #85466. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #85466. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #85466, then check it covers your case.

Read #85466 Pick up a Lab task

These items appear related to how the auxiliary client treats custom or explicit base URLs, including api_mode handling, Anthropic-style endpoint paths (/anthropic, /v1 for Kimi), and reading key_env from task config. One is a bug report and the others are fix pull requests; their outcomes are not stated in the titles.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#85466 fix(auxiliary): keep /anthropic base_url for anthropic_messages custom endpoints (salvage #64891)

merged to main

files: agent/auxiliary_client.py, tests/agent/test_auxiliary_explicit_base_anthropic.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · stale or abandoned 1

#16256 fix(aux-client): honor api_mode in explicit_base_url path; read key_env in task config (#16254) · stale or abandoned
#22289 fix(auxiliary): strip /v1 from Kimi base URL before Anthropic SDK wraps it · done elsewhere → 413990c

Closed issues · 1

Closed#16254[Bug]: 'custom = OpenAI' hardcoded assumption: explicit_base_url path ignores api_mode (sibling of #7661/#15033, plus key_env never parsed in aux config)

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem: agent
Merged PRs: #85466
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 13 Aug 2026

For your agent

The same facts, typed.

cluster/16254.json
cluster/16254.md