ACP /model command --provider flag parsing fixes

NousResearch/hermes-agent · cluster 27119 · acp

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 0 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
1 issue and 3 PRs.

A bug report and several fixes addressing the --provider flag being ignored or incorrectly parsed when the /model command is issued through ACP clients such as Scarf and Zed. Changes involve flag parsing logic and persistence in the ACP _cmd_model handler.

Open issues1

  • Issue#27119[Bug]: /model –provider flag ignored when sent via ACP (Scarf, Zed, etc.)”

Open PRs3

  • PR#27135fix(acp): parse /model --provider flag for ACP clients
  • PR#27173fix(acp): use parse_model_flags + persist_global in ACP _cmd_model
  • PR#27194fix(acp): preserve explicit --provider for named custom providers in ACP _cmd_model

1 PR closed without merging

From the close comments: duplicate 1

  • #27130 fix(acp): parse --provider flag in /model command via ACP clients · duplicate → #27173
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.40: 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
acp
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.