NousResearch/hermes-agent

Custom provider target_model ignored on resolve path

Cluster 93092. Data as of 2026-10-29 11:48 UTC

Nothing open on GitHub. Fix merged in #93356 on 24 Aug 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 #93356. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #93356. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #93356 Pick up a Lab task

These items concern a bug where target_model is silently ignored when resolving a named custom provider that has a default model, along with a broader fix batch covering several unrelated single-site issues. The custom-provider target_model resolution problem is the dominant shared theme.

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.

#93356 fix: five independent single-site fixes — target_model on custom providers, STT error surfacing, stale cron next_run_at, browser-use PATH floor, draft-sweep age gate (#93092, #93045, #93049, #93115, #93055)

merged to main

files: apps/desktop/src/plugins/hermes-bots/plugin.js, apps/desktop/src/plugins/hermes-bots/tests/hide-bot-chats.test.mjs, contributors/emails/[redacted:email], contributors/emails/[redacted:email], cron/jobs.py, hermes_cli/runtime_provider.py, tests/cron/test_due_stale_cron_edit.py, tests/hermes_cli/test_runtime_provider_resolution.py, tests/tools/test_browser_use_cli.py, tests/tools/test_transcription_tools.py, tools/browser_use_cli.py, tools/transcription_tools.py

1 PR closed without merging

From the close comments: merged via another change 1

#93094 fix(providers): honor target_model on the custom-provider resolve path · merged via another change → #78573, #93356

Closed issues · 1

Closed#93092[Bug]: resolve_runtime_provider ignores target_model when requested provider is a named custom provider with a default model — auxiliary.<task>.model silently falls back to the provider default

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

Merged PRs: #93356
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 24 Aug 2026

For your agent

The same facts, typed.

cluster/93092.json
cluster/93092.md