Cairn
NousResearch/hermes-agent

Desktop branch-from-message Hermes session forking

Cluster 40950 · apps/desktop. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items concern implementing and fixing Hermes-native session branching when forking from a message on desktop, including a reported defect where branched sessions lack a parent reference and history copy.

Open issues1

  • Issue#40950[Feature]: Desktop fork-from-message should use Hermes-native session branching

Open PRs1

  • PR#40973feat(desktop): back branch-from-message with Hermes-native session forks (#40950)
Closed issues · 1
  • Closed#66685bug(desktop): session branch creates unlinked orphan — no parent_session_id, no history copy
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: 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
apps/desktop
Closed issues
1
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/40950.json
cluster/40950.md