Cairn
NousResearch/hermes-agent

Expose queue depth/status as public gateway API

Cluster 28555 · gateway. 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 items add public API methods to the gateway for retrieving queue depth and status information. The work appears focused on making internal queue metrics accessible externally, including support for busy_input_mode queues.

Open issues1

  • Issue#28555feat(gateway): expose queue depth/status API for busy_input_mode queue

Open PRs1

  • PR#28586feat(gateway): expose get_queue_depth and get_queue_status public API

1 PR closed without merging

From the close comments: other 1

  • #28567 feat(gateway): expose queue depth API (#28555) · other → #28586, #28555
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
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/28555.json
cluster/28555.md