NousResearch/hermes-agent

worktree prune incorrectly deletes unmerged branches without remote

Cluster 111895. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #112206 on 16 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 #112206. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #112206. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #112206 Pick up a Lab task

A bug where hermes worktree prune misidentifies unmerged local commits as fully merged when no remote is configured, causing force-deletion of branches with unique commits. Fixes and tests address preserving local-only commits during pruning.

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.

#112206 fix(worktree): prune keeps unique local commits in repos with no remote (#111895, salvage #111897)

merged to main

files: hermes_cli/worktree_gc.py, hermes_cli/worktree_ops.py, tests/hermes_cli/test_worktree.py, tests/hermes_cli/test_worktree_gc.py, website/docs/user-guide/cli.md

2 PRs closed without merging

From the close comments: merged via another change 1 · other 1

#111897 fix(worktree): preserve commits without remote refs · merged via another change → 0a3e792, #112206
#112289 fix(worktree): prove no-remote reclaim against local primary · other → #112206, #111897

Closed issues · 1

Closed#111895[Bug]: `hermes worktree prune` calls unmerged worktrees "clean and fully merged/pushed" and force-deletes their branches in repos with no remote

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: #112206
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/111895.json
cluster/111895.md