Cairn
NousResearch/hermes-agent

Kanban worker spawn mode in headless/no-TTY environments

Cluster 23844 · cron. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 3 PRs 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 0 PRs.

Multiple issues and fixes addressing how kanban workers are spawned in headless or no-TTY contexts, specifically around forcing CLI or oneshot (-z) mode instead of interactive/TUI modes that cause crashes or protocol violations.

Open issues1

  • Issue#28992[Feature]: Use -z (oneshot) mode for kanban worker spawn instead of chat -q

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: done elsewhere 2 · other 1

  • #23851 fix(kanban): use -z (one-shot) mode for worker spawn instead of chat -q · other
  • #35629 fix(cli): headless chat -q falls back to oneshot mode without TTY · done elsewhere → e87c495
  • #40108 fix(kanban): force cli for worker subprocesses · done elsewhere → e87c495
Closed issues · 2
  • Closed#23844fix(kanban): dispatcher worker spawn broken in headless/no-TTY environments
  • Closed#40095Kanban workers crash (protocol violation) when display.interface: tui — headless worker launches TUI, exits rc=0
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
Closed issues
2
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/23844.json
cluster/23844.md