# NousResearch/hermes-agent · Align memory status and runtime availability predicates

## Open now

- Nothing open on GitHub.

A bug caused the memory status check to report availability using a different predicate than the one used at runtime, producing misleading 'available' indicators while actual operations encountered errors. These changes align the status reporting and runtime logic to use the same availability predicate.

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

- #80388: hermes memory status reports "available ✓" while every retain fails — status and runtime use different availability predicates

## Prior & competing PRs

- **#80517: fix(tools,cli): never downgrade lazy deps at runtime; truthful memory status**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `74f726c17675642c2eff3033632e812f5f0e6614`, `#80390`, `#80388`
- **#80555: fix(memory): status reflects runtime lazy_deps predicate**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `4cbf862abe4`, `6a5a6a05d2d`

## Fix status

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