Cairn
NousResearch/hermes-agent

Align memory status and runtime availability predicates

Cluster 80388 · agent. 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.

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.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #80517 fix(tools,cli): never downgrade lazy deps at runtime; truthful memory status · done elsewhere → 74f726c, #80390, #80388
  • #80555 fix(memory): status reflects runtime lazy_deps predicate · done elsewhere → 4cbf862, 6a5a6a0
Closed issues · 1
  • Closed#80388hermes memory status reports "available ✓" while every retain fails — status and runtime use different availability predicates
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
agent
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/80388.json
cluster/80388.md