Cairn
NousResearch/hermes-agent

Anthropic/Kimi base_url trailing /v1 causing doubled /v1 paths

Cluster 21297 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
9items grouped
Known?
Yes. 9 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 5 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 1 PR.

Members describe a shared problem where an Anthropic-style base_url ending in /v1 (including the kimi-coding provider's /coding/v1) can lead to a doubled /v1/v1/messages URL and HTTP 404 errors. Several pull requests propose stripping or normalizing the trailing /v1; this label does not assert whether any were merged or fixed the issue.

Open issues0

No open issues.

Open PRs1

  • PR#23260fix(kimi): strip trailing v1 for anthropic endpoints

5 PRs closed without merging

From the close comments: done elsewhere 2 · superseded by another PR 2 · duplicate 1

  • #21308 fix(provider): kimi-coding double /v1 in Anthropic Messages URL · duplicate → #15200
  • #24873 fix(anthropic): strip native SDK /v1 base URL suffix · superseded by another PR → #24876
  • #24877 fix(anthropic): strip native base url v1 suffix · superseded by another PR
  • #25135 fix: normalize Kimi runtime base URL · done elsewhere → 1d8b9e6
  • #37656 fix(anthropic): strip trailing /v1 from base_url in build_anthropic_client (#24833) · done elsewhere
Closed issues · 3
  • Closed#21297kimi-coding provider returns HTTP 404 on every request — double /v1 in Anthropic Messages URL
  • Closed#24833Anthropic provider 404s when base_url includes /v1 (SDK adds its own)
  • Closed#25104[Bug]: kimi-coding Anthropic Messages runtime keeps /coding/v1 and produces /v1/v1/messages
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.19: 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
Closed issues
3
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/21297.json
cluster/21297.md