macOS TCC prompt shows version string ("2.1.112") instead of app name
Resolved 💬 4 comments Opened Apr 17, 2026 by ideabrian Closed Apr 20, 2026
Summary
On macOS Sequoia, when Claude Code triggers a TCC (Transparency, Consent, and Control) prompt — e.g., Files and Folders → Network Volume access — the dialog identifies the app as the version string 2.1.112 rather than "Claude Code."
Reproduction
- macOS 24.3.0 (Sequoia), Claude Code CLI v2.1.112 installed at
~/.local/bin/claude - Have an SMB share mounted at
/Volumes/<name> - Run
claudeand ask it to enumerate mounts (e.g.,ls /Volumes,df -h,lsof | grep smbfs) - macOS TCC prompts:
"2.1.112" would like to access files on a network volume.
The dialog has no app name, no icon specific to Claude Code — just the version string.
Cause (likely)
The claude binary is distributed as a bun-bundled standalone executable without a .app bundle or an Info.plist that sets CFBundleName. macOS TCC falls back to CFBundleShortVersionString when no human-readable name is available.
Impact
- Users cannot identify what app is asking → defensive users deny by default
- Looks unprofessional; undermines trust in the CLI
- Confuses which binary the prompt refers to on systems with multiple versions installed side by side
Suggested fix
Either:
- Wrap the CLI in a signed
.appbundle with a properInfo.plist(CFBundleName = "Claude Code", bundle identifier likecom.anthropic.claude-code, icon), OR - Embed a minimal
Info.plistin the standalone binary viald -sectcreate __TEXT __info_plist Info.plistat build time, setting at minimumCFBundleNameandCFBundleIdentifier.
Option 2 is lighter-touch and works for unsigned standalone binaries.
Environment
- macOS: 24.3.0 (Sequoia)
- Claude Code: v2.1.112
- Install method:
~/.local/bin/claude(standalone) - Shell: zsh
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗