NousResearch/hermes-agent

Per-call and per-turn model override features

Cluster 29914 · agent. Data as of

1 open item. Fix merged in #67113 on 18 Jul 2026. Check it covers your case.

The short answer

1open issue
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #67113. 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
1 issue and 0 PRs.

These issues and pull requests concern adding the ability to override the model on a per-turn, per-image-generation, or per-tool-call basis, rather than relying solely on a global model setting. Topics include agent-driven model selection, one-turn overrides, and honoring model fields in image generation calls.

Open issues1

  • Issue#61216[Feature] Let agent choose image generation model per-call

Open PRs0

No open pull requests.

Fixes on record

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

  • #67113 feat: /model --once one-turn model override (salvages #29923)

    merged to main

    files: cli.py, contributors/emails/[email protected], gateway/run.py, gateway/slash_commands.py, hermes_cli/model_switch.py, tests/gateway/test_model_switch_persistence.py, tests/hermes_cli/test_cli_model_once.py, tests/hermes_cli/test_model_switch_once_flags.py, tests/test_tui_gateway_server.py, tui_gateway/server.py, website/docs/user-guide/configuring-models.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #29923 Add per-turn and per-image model overrides · merged via another change → #67113, #59815
Closed issues · 1
  • Closed#29914Add first-class per-turn and per-tool-call model overrides
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.56: 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
#67113
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
18 Jul 2026

For your agent

The same facts, typed.