Cairn
NousResearch/hermes-agent

serve-restart marker cleanup and failure messaging

Cluster 134995 · hermes cli. 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 address how a dashboard respawn error is communicated and how stale serve-restart markers tied to stopped PIDs are properly cleared when a respawn cannot be scheduled.

Open issues1

  • Issue#134995[Bug]: pending serve-restart marker is keyed on the stopped PID, every hermes invocation warns until a manual restart

Open PRs1

  • PR#135003fix(cli): discharge a serve-restart marker when its respawn is booked failed

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #135155 fix(update): name the remedy when a dashboard respawn fails · superseded by another PR → #135003
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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/134995.json
cluster/134995.md