macOS signing and TCC permission persistence issues

NousResearch/hermes-agent · cluster 43365 · apps/desktop

Data as of

Nothing open on GitHub. Fix merged in #73681. Check it covers your case.

The short answer

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

These items concern macOS app signing identity (switching to Developer ID) and the resulting problem of TCC permissions—microphone, accessibility, automation, and full disk access—being revoked after each rebuild or update. The common thread is that an unstable or ad-hoc signing identity causes macOS to treat each build as a new app, resetting granted permissions.

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.

  • #73681 fix(desktop): stable macOS signing identity so TCC grants survive local rebuilds

    merged to main

    files: hermes_cli/config.py, hermes_cli/main.py, scripts/install.sh, tests/hermes_cli/test_gui_command.py, tests/hermes_cli/test_set_config_value.py, website/docs/user-guide/desktop.md

Closed issues · 5
  • Closed#43365[Bug]: macOS TCC permissions (Accessibility/Automation) reset after every Hermes Desktop update
  • Closed#43788fix(desktop): preserve macOS microphone permission across updates
  • Closed#49110feat: sign Hermes.app with Apple Developer ID for stable macOS TCC permissions
  • Closed#52010[Bug]: macOS Full Disk Access (Files & Folders) revoked after every Hermes Desktop update
  • Closed#68618[macOS] Switch from adhoc to Developer ID signing for TCC permission persistence
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.26: 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

Subsystem
apps/desktop
Merged PRs
#73681
Closed issues
5
Attempts
0 PRs closed without merging
Fix link checked
28 Jul 2026

For your agent

The same facts, typed.