# NousResearch/hermes-agent · CLI lock handling and recovery consistency fixes

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #86527: _early_recovery: stale update-incomplete lock is deleted but repair is skipped — state inconsistent, repair deferred to next launch

## Prior & competing PRs

- **#87640: fix(cli): batch resume dedup, oneshot yolo ordering, atomic update locks**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`
- **#127755: fix(cli): retry lock acquire after deleting stale recovery lock**. closed without merge
  - maintainer direction: category `wontfix_bydesign`; implication `wontfix`; refs `#86527`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`