Cairn

Auto-appending /v1 to base URLs ignoring user choice

NousResearch/hermes-agent · cluster 43408 · hermes cli

Data as of

5 open items. Fix attempted, not merged.

The short answer

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

These issues and fixes concern a bug where the setup wizard and model commands automatically append /v1 to custom provider base URLs even when users explicitly decline it, with related problems around local-server detection heuristics.

Open issues2

  • Issue#43408Setup wizard ignores user choice when declining /v1 suffix
  • Issue#45543Bug: `_model_flow_custom` has two local-server detection / user-choice bugs (port false positive + user /v1 choice silently overridden)

Open PRs3

  • PR#43410fix: respect user choice when declining /v1 suffix in setup
  • PR#43988fix(models): skip /v1 URL heuristic for anthropic_messages providers
  • PR#45553fix(cli): use URL parsing for local-server detection and respect user /v1 rejection

1 PR closed without merging

From the close comments: other 1

  • #43433 fix(cli): respect user choice when declining /v1 suffix (#43408) · other
Closed issues · 2
  • Closed#43979hermes model command auto-appends /v1 to base_url even when api_mode is anthropic_messages
  • Closed#43982Custom provider base_url auto-modified when using hermes model/Telegram /model command
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
hermes cli
Closed issues
2
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/43408.json
cluster/43408.md