Cairn
NousResearch/hermes-agent

Kanban per-provider concurrency budget feature and fix

Cluster 123654 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 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 1 PR.

These members cover the addition of a per-provider concurrency budget in the Kanban system, keyed on each run's looked-up provider. They include the feature request, implementation, and a related fix targeting the resolved run provider key.

Open issues1

  • Issue#123654[Feature]: Kanban per-provider concurrency budget keyed on each run's resolved provider

Open PRs1

  • PR#128752feat(kanban): per-provider concurrency budget

1 PR closed without merging

From the close comments: done elsewhere 1

  • #124918 fix(kanban): per-provider concurrency budget keyed on resolved run provider · done elsewhere
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
cron
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/123654.json
cluster/123654.md