claude-code - 💡(How to fix) Fix [BUG] claude binary re-registers as new app in macOS Privacy & Security on every version update (versioned install path, not code signing) [3 comments, 3 participants]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Summary

Every Claude Code update forces re-authorization of macOS privacy permissions (Full Disk Access, Automation, etc.) because each version installs to a unique versioned path. macOS TCC resolves symlinks to the real executable path and treats each version as a distinct application.

Evidence

Full Disk Access in System Settings shows each version as a separate, unrecognized app:

By contrast, Claude Desktop appears as a single stable "Claude" entry and does not exhibit this behavior.

codesign output (2.1.111)

Executable=/Users/<user>/.local/share/claude/versions/2.1.111 Identifier=com.anthropic.claude-code Authority=Developer ID Application: Anthropic PBC (Q6L2SF6YDW) Authority=Developer ID Certification Authority Authority=Apple Root CA TeamIdentifier=Q6L2SF6YDW

The signing identity is stable and correct — this is NOT a code signing issue.

Root Cause

macOS TCC tracks permissions by resolved executable path, not bundle identifier. Each update installs to ~/.local/share/claude/versions/<version>/, so every release is a new path = new app to TCC.

Impact

• Re-authorization required after every update
• Orphaned permission entries accumulate in System Settings
• Particularly disruptive for integrations requiring Full Disk Access (e.g., iMessage plugin)

Suggested Fix

Register a stable, non-versioned symlink path (e.g., ~/.local/share/claude/current) with TCC instead of the versioned path — and ensure the symlink is what macOS tracks. This is a standard pattern for versioned Electron/CLI app installs.

Environment

• macOS 26.3.1
• Claude Code 2.1.111 (affects all versions observed: 2.1.97+)
• Installed via native installer

What Should Happen?

New versions of Claude should not require re-authorizing full-disk access.

Error Messages/Logs

Executable=/Users/<user>/.local/share/claude/versions/2.1.111
Identifier=com.anthropic.claude-code
Authority=Developer ID Application: Anthropic PBC (Q6L2SF6YDW)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
TeamIdentifier=Q6L2SF6YDW

Steps to Reproduce

Steps to Reproduce

1. Install Claude Code and grant Full Disk Access when prompted
2. Open System Settings → Privacy & Security → Full Disk Access
3. Confirm claude appears in the list with the toggle enabled
4. Install any Claude Code update (version increment, any size)
5. Attempt to use a feature requiring Full Disk Access (e.g., iMessage plugin)
6. Observe: macOS prompts for Full Disk Access again
7. Return to System Settings → Privacy & Security → Full Disk Access
8. Observe: the new version appears as a separate entry; the previous version entry remains, toggle off

Expected Result

Claude Code retains Full Disk Access permission across updates — single entry persists in System Settings.

Actual Result

Each version creates a new entry named after its version number (e.g., 2.1.110, 2.1.111). Previous entries remain as orphaned, disabled entries. Permissions must be re-granted after every update.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.110

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

No response