# NousResearch/hermes-agent · clone-all copies large local-model directories unintentionally

## Open now

- Nothing open on GitHub.

A bug where \`hermes profile create --clone-all\` duplicates large machine-scoped directories (\`models/\`, \`runtimes/\`, \`node/\`) per profile, and related fix attempts targeting that behavior.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #112187. Verify it addresses your case.
- **Recommended:** read PR #112187 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-112187`. 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.

## Closed / duplicate issues

- #111718: \[Bug\]: \`hermes profile create --clone-all\` copies the local-models runtime trees (\`models/\`, \`runtimes/\`, \`node/\`) — tens of GB of machine-scoped weights and binaries duplicated per profile

## Prior & competing PRs

- **#112187: fix(profiles): profile create --clone-all no longer copies the local-model trees models/, runtimes/, node/ (#111718, salvage #101340)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/backup.py`, `hermes_cli/profiles.py`, `hermes_constants.py`, `tests/hermes_cli/test_profiles.py`, `website/docs/reference/profile-commands.md`, `website/docs/user-guide/profiles.md`
- **#101340: fix(profiles): --clone-all skips the local-models runtime trees (models/, runtimes/, node/)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#112187`

## Fix status

- Merged to main in PR #112187 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-16`.