macOS: Claude Code CLI shows as bare version string (e.g. "2.1.195") in Privacy & Security, not a readable app name

Open 💬 0 comments Opened Jul 9, 2026 by korentomas

Environment

  • macOS (Darwin 25.5.0)
  • Claude Code 2.1.205, installed at ~/.local/bin/claude (CLI binary, no .app bundle)

What happens

In System Settings → Privacy & Security → Files and Folders (and Documents Folder), Claude Code appears as its bare version string — e.g. 2.1.195, 2.1.205 — with a generic/blank or "?" icon, instead of a recognizable name like "Claude Code".

Because macOS keys the TCC entry by version/signature, every update spawns a new entry and the old ones pile up. I currently have both 2.1.195 and 2.1.205 listed, each with its own "Documents Folder" toggle. (Screenshot: two entries labelled only 2.1.195 and 2.1.205.)

Why it matters

  • Users can't tell what is requesting Documents-folder access — it reads like an unknown app, which is a security-trust red flag (I initially thought something suspicious had been granted access).
  • Stale per-version entries accumulate with no indication they're the same tool.

Expected

  • A stable, human-readable identity ("Claude Code") and icon in the TCC / Privacy panes.
  • Permission that carries across updates instead of creating a new entry per version.
  • Likely requires a proper CFBundleDisplayName / CFBundleIdentifier and a stable code-signing identity on the CLI binary so TCC treats successive versions as the same app.

Repro

  1. Install Claude Code, let it request/grant Documents-folder access.
  2. Update to a newer version, grant again.
  3. Open System Settings → Privacy & Security → Files and Folders — two entries appear, each labelled only by version number.

View original on GitHub ↗