macOS permission prompts and Privacy settings show Claude Code as a bare version number (e.g. "2.1.83")

Status Closed — duplicate
Reported on v2.1.292
Maintainer reply None cached
Activity 2 comments · opened Oct 7, 2026 · closed Oct 11, 2026

Problem

On macOS, the native install of Claude Code identifies itself to the system only by its version number. Permission prompts read like "2.1.292 would like to control Google Chrome" or "2.1.83 would like to access files on a network volume", and System Settings > Privacy & Security lists entries named 2.1.83 and 2.1.292 with a generic icon.

There is nothing in the prompt that says "Claude Code". These prompts also tend to appear while I am in the middle of something else, with no indication of which action triggered them, so I am being asked to grant access to my network volumes, browsers, or contacts to something I cannot identify. With agentic tools doing more on their own, an unidentifiable process asking for system permissions is exactly the kind of prompt users should be able to evaluate properly, and right now they can't.

What I see

In System Settings > Privacy & Security:

  • 2.1.83 (generic icon): Network Volumes, enabled. This version is no longer installed on disk.
  • 2.1.292 (generic document icon): Automation for Brave Browser and Google Chrome.

Consequences

  1. Unidentifiable prompts. A version number does not tell the user which app is asking.
  2. Permissions do not carry over. Each update is treated as a new app, so access has to be granted again after updating.
  3. Stale entries pile up. Old versions that have been auto-deleted keep their entries, and their granted permissions, in Settings.

Likely cause

The executable is a bare Mach-O file named after its version (~/.local/share/claude/versions/<version>, symlinked from ~/.local/bin/claude). macOS uses the executable's file name as the label when there is no app bundle with a stable name and identity.

Suggested fix

Give the binary a stable, recognisable identity for TCC, for example a consistent executable name and code-signing identifier (or a minimal app bundle with a name and icon), so prompts read "Claude Code" and permissions persist across updates. It would also help if Claude Code said in the terminal which action is about to trigger a system permission prompt.

Environment

  • Claude Code 2.1.292, native install
  • macOS (Darwin 27.2.0), Apple Silicon

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗