NousResearch/hermes-agent

compression tip visibility broken by reset forks

Cluster 114271. Data as of 2026-10-24 13:18 UTC

Nothing open on GitHub. Fix merged in #114927 on 18 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #114927. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #114927. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #114927, then check it covers your case.

Read #114927 Pick up a Lab task

A bug where reset-fork siblings hijack or obscure the compression lineage tip, making it invisible in /resume and session list views. Multiple fix attempts address excluding reset-from siblings from compression tip projection logic.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#114927 fix(sessions): compression lineage tip stays visible in /resume and the session list when a reset fork exists (#114271, salvage #114287)

merged to main

files: gateway/slash_commands_session.py, hermes_state_compression.py, hermes_state_gateway.py, hermes_state_messages.py, hermes_state_sessions.py, tests/gateway/test_resume_command.py, tests/hermes_state/test_compression_lineage_guard.py, tests/hermes_state/test_hermes_state.py, website/docs/reference/slash-commands.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

#114287 fix(state): keep reset forks from stealing the compression lineage tip · merged via another change → 52a293f, #114927, #114271, #114287
#114298 fix: exclude _reset_from siblings from compression tip projection · superseded by another PR → #114287

Closed issues · 1

Closed#114271Compression tip invisible in /resume + desktop list: reset sibling hijacks tip projection, cross-surface continuation unrecoverable

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

Merged PRs: #114927
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/114271.json
cluster/114271.md