NousResearch/hermes-agent

Desktop sibling worktree project ownership bug

Cluster 114638. Data as of

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

The short answer

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

These issues address a bug where sibling worktree sessions appear under incorrect or multiple projects in the desktop app. The work involves fixing project ownership assignment so worktree sessions are listed under only the correct project.

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.

  • #114952 fix(desktop): sibling-worktree session is listed under one Project only (#114638, salvage #114643)

    merged to main

    files: apps/desktop/src/app/chat/sidebar/index.tsx, apps/desktop/src/app/chat/sidebar/projects/index.ts, apps/desktop/src/app/chat/sidebar/projects/workspace-groups.test.ts, apps/desktop/src/app/chat/sidebar/projects/workspace-groups.ts, apps/desktop/src/lib/session-project-label.ts, apps/desktop/src/store/projects.ts, apps/desktop/src/store/session-color.ts, apps/shared/src/gateway-contract.generated.ts, apps/shared/src/gateway-contract.openrpc.json, tests/tui_gateway/test_project_tree.py, tui_gateway/contracts/projects_pets.py, tui_gateway/project_tree.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #114643 fix(desktop): retain sibling worktree project ownership · merged via another change → b111e41, #114952, #114638, #114643
Closed issues · 1
  • Closed#114638[Bug]: Desktop sibling worktree session appears under both repo and ancestor Projects
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

Merged PRs
#114952
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.