NousResearch/hermes-agent

Partial clone packfile accumulation causing unbounded growth

Cluster 129712. Data as of

Nothing open on GitHub. Fix merged in #131679 on 2 Oct 2026. Check it covers your case.

The short answer

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

A bug causes each lazy fetch in a partial clone to create a new packfile that is never consolidated or garbage collected, leading to the .git directory growing to tens of gigabytes. The members address this by folding or compacting accumulated packfiles after fetch operations.

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.

  • #131679 A partial clone's .git stops growing: lazy-fetch packs fold on update and the commit-graph loop is off (#129712, salvage #129724, #127721)

    merged to main

    files: hermes_cli/gitlock.py, hermes_cli/update_cmd.py, hermes_cli/update_cmd_check.py, scripts/install.ps1, scripts/install.sh, tests/hermes_cli/test_gitlock.py, website/docs/getting-started/updating.md

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #129714 fix(desktop): compact partial clone packs after fetch · superseded by another PR → 4e3fcd5, #131679
  • #129724 fix(update): fold lazy-fetch packfiles so a partial clone's .git stops growing · done elsewhere → add6541, 4e3fcd5, #131679
Closed issues · 1
  • Closed#129712Updater/blobs workflow creates one packfile per lazy fetch, never gc's — .git grows to tens of GB (39 GiB observed)
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
#131679
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
2 Oct 2026

For your agent

The same facts, typed.