# NousResearch/hermes-agent · Secure hermes backup file permissions and location

## Open now

- 1 issue, 0 PRs open on GitHub.
- #59735: hermes backup defaults to $HOME with no chmod -- doesn't inherit ~/.hermes's 0700 protection

These issues and PRs address the hermes backup defaulting to an insecure location and lacking restrictive file permissions, with fixes to set chmod 0600 on the backup zip and default its path under HERMES_HOME.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 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

- #59735: hermes backup defaults to $HOME with no chmod -- doesn't inherit ~/.hermes's 0700 protection

## Prior & competing PRs

- **#59738: fix(hermes_cli): chmod 0600 on hermes backup zip**. closed without merge · fix tier `suggested`
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#59736`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#59736: security(backup): default hermes backup under HERMES_HOME, chmod 0600**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

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