# NousResearch/hermes-agent · Handling corrupt archive members during import

## Open now

- Nothing open on GitHub.

These members concern how the import process behaves when a backup archive contains a corrupt or damaged member, including a bug report about a crash and data overwriting, and at least two differing fix approaches around when or whether to abort.

## 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 #121498. Verify it addresses your case.
- **Recommended:** read PR #121498 (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-121498`. 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

- #121258: \[Bug\]: \`hermes import\` of an archive with one corrupt member crashes with a zlib.error traceback after overwriting part of the home

## Prior & competing PRs

- **#121498: fix(import): refuse a damaged backup archive before anything is overwritten**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/backup.py`, `hermes_cli/main.py`, `tests/e2e/core/upgrade/test_update_userstate_import.py`, `tests/hermes_cli/test_backup.py`, `website/docs/reference/cli-commands.md`
- **#121263: fix(backup): continue import after corrupt member**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#121498`, `#121258`

## Fix status

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