Cairn
NousResearch/hermes-agent

CLI lock handling and recovery consistency fixes

Cluster 86527 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address bugs in lock acquisition, stale lock cleanup, and the ordering or atomicity of update and recovery operations in the CLI. A known issue notes that deleting a stale incomplete-update lock without running repair leaves state inconsistent until the next launch.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: closed without comment 1 · won't fix / by design 1

  • #87640 fix(cli): batch resume dedup, oneshot yolo ordering, atomic update locks · closed without comment
  • #127755 fix(cli): retry lock acquire after deleting stale recovery lock · won't fix / by design → #86527
Closed issues · 1
  • Closed#86527_early_recovery: stale update-incomplete lock is deleted but repair is skipped — state inconsistent, repair deferred to next launch
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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/86527.json
cluster/86527.md