Cairn
NousResearch/hermes-agent

Multi-agent swarm orchestration slash commands

Cluster 25020 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

These items propose adding slash commands (/swarm, /Efficiency) to enable in-harness multi-agent orchestration and kanban-backed auto orchestration workflows. The members share a common theme of opt-in multi-agent coordination features.

Open issues1

  • Issue#35600feat: /swarm slash command for in-harness multi-agent orchestration

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: other 1

  • #35602 feat(swarm): add /swarm slash command for in-harness multi-agent orchestration · other
Closed issues · 1
  • Closed#25020[Feature]: Add an opt-in /Efficiency mode for kanban-backed auto orchestration
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.45: 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
hermes cli
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/25020.json
cluster/25020.md