# NousResearch/hermes-agent · Fix scratch pruning for relative-path worktrees

## Open now

- 1 issue, 1 PR open on GitHub.
- #118820: \[Bug\]: scratch pruning misses relative-path worktree registrations
- PR #118824: fix(scratch): prune relative linked worktrees

These items address a bug where scratch pruning fails to handle worktree registrations that use relative paths. The fixes involve resolving and pruning relative linked worktree gitdirs correctly.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Open related issues

- #118820: \[Bug\]: scratch pruning misses relative-path worktree registrations

## Prior & competing PRs

- **#118824: fix(scratch): prune relative linked worktrees**. open
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `736936c837`, `#118827`
  - files: `hermes_constants_scratch.py`, `tests/test_scratch_dir.py`
- **#118827: fix(scratch): resolve relative worktree gitdirs**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#118824`, `#118820`

## Fix status

- No merged fix on record.
- Subsystem: `agent`