NousResearch/hermes-agent

Custom endpoint base URL missing /v1 causes chat 404s

Cluster 65488 · agent/transports. Data as of 2026-10-28 11:56 UTC

Nothing open on GitHub. Fix merged in #115828 on 19 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #115828 Pick up a Lab task

The members concern custom OpenAI-compatible endpoints entered without /v1, where model detection works but chat requests reportedly return 404. One issue describes the problem and two pull requests propose changes to how the base URL is saved or handled; their outcomes are not established here.

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.

#115828 fix(dashboard): custom endpoint typed without /v1 saves the URL that served /models, so chat no longer 404s (#65488, salvage #65489)

merged to main

files: apps/desktop/src/api/config.ts, apps/desktop/src/app/settings/custom-endpoints-settings.test.tsx, apps/desktop/src/app/settings/custom-endpoints-settings.tsx, apps/desktop/src/store/onboarding.test.ts, apps/desktop/src/store/onboarding.ts, apps/desktop/src/types/hermes.ts, hermes_cli/web_routers/config_env.py, tests/hermes_cli/test_web_routers_endpoint_probe.py, tests/hermes_cli/test_web_server.py, website/docs/user-guide/local-models.md

1 PR closed without merging

From the close comments: merged via another change 1

#65489 fix(providers): resolve `/v1` base-url mismatch between model detection and chat · merged via another change → 754d229, #115828, #65488, #65489

Closed issues · 1

Closed#65488Custom OpenAI-compatible endpoint saved without /v1: model detection succeeds but every chat call 404s

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.67: 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/transports
Merged PRs: #115828
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 19 Sep 2026

For your agent

The same facts, typed.

cluster/65488.json
cluster/65488.md