Cairn

Kanban per-task model override CLI wiring

NousResearch/hermes-agent · cluster 24206 · cron

Data as of

Nothing open on GitHub. Fix merged in #69876. Check it covers your case.

The short answer

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

These issues and pull requests concern adding and correctly routing a per-task model override parameter through the kanban create command, CLI flags, MCP tool, and worker spawn paths. Multiple entries address gaps where the flag existed but was discarded or not wired through to the dispatcher or worker.

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.

  • #69876 feat(kanban): per-task model dropdown — override worker model+provider from the board

    merged to main

    files: hermes_cli/kanban.py, hermes_cli/kanban_db.py, plugins/kanban/dashboard/dist/index.js, plugins/kanban/dashboard/plugin_api.py, tests/plugins/test_kanban_model_override.py, tools/kanban_tools.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #46403 feat(kanban): allow create tasks to pin worker model · other
  • #67518 fix(kanban): add --model to create + fix dispatcher -m placement (#67459) · done elsewhere → c1b0f6f, #69876, #67459, #67518
Closed issues · 4
  • Closed#24206Feature Request: Support per-task model override for Kanban workers
  • Closed#46376[Enhancement] kanban create: expose --model-override parameter (CLI + MCP tool)
  • Closed#47949Feature Request: Add --model parameter to kanban create for per-task model override
  • Closed#67459tasks.model_override: no write surface, and the dispatcher's -m is discarded by the chat subparser
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.25: 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
cron
Merged PRs
#69876
Closed issues
4
Attempts
2 PRs closed without merging
Fix link checked
23 Jul 2026

For your agent

The same facts, typed.

cluster/24206.json
cluster/24206.md