Cairn
NousResearch/hermes-agent

Fix kanban board arg priority over env var

Cluster 30678 · cron. Data as of

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

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #131913. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #131913. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address a bug where an explicit board argument was incorrectly overridden by the HERMES_KANBAN_DB environment variable. The fix ensures an explicitly passed board value takes precedence over the environment-based default.

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.

  • #131913 fix(kanban): explicit board (param or --board scope) trumps env pin [risk 0.60]

    merged to main

    files: agent/delegation_context.py, gateway/kanban_watchers.py, gateway/kanban_watchers_dispatcher.py, gateway/kanban_watchers_notifier.py, hermes_cli/kanban_db.py, tests/hermes_cli/test_kanban_board_path_priority.py, tests/hermes_cli/test_kanban_boards.py

3 PRs closed without merging

From the close comments: superseded by another PR 2 · done elsewhere 1

  • #30681 fix(kanban): explicit board= arg outranks HERMES_KANBAN_DB env override · superseded by another PR → #131913, #107195
  • #107195 fix(kanban): explicit board param trumps env pin t_3f1c63a5 · done elsewhere → 8e8eabf, 46904a3, aea28d4, f515a3b, 17a5519, 6995d49, #107195, #30678, #172554, #30681, #63026, #88276, #102692, #66552
  • #129543 fix(kanban): honor explicit board over DB pin · superseded by another PR → #131913, #107195
Closed issues · 1
  • Closed#30678kanban board override is ignored in worker env because HERMES_KANBAN_DB outranks explicit board
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
cron
Merged PRs
#131913
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
3 Oct 2026

For your agent

The same facts, typed.

cluster/30678.json
cluster/30678.md