macOS Documents-access permission dialog shows bare version number ("2.1.216") as the app name — unassessable for users
Description
After a native auto-update, macOS TCC showed this permission prompt:
"2.1.216" would like to access files in your Documents folder. [Don't Allow] [Allow]
The requesting binary is Claude Code's versioned auto-update install, but nothing in the dialog says so. A user is being asked to grant Documents access to an unidentifiable dotted number.
Why it matters
- Users cannot assess the grant. "2.1.216" carries zero information about who is asking or why.
- It trains bad habits: the correct response to an unidentifiable binary requesting Documents access should be deny — but here denying breaks the tool, so users learn to click Allow on prompts they can't identify.
- It's a plausible social-engineering pattern to mimic: malware asking for broad file access under an anonymous-looking version string benefits from users being conditioned by legitimate prompts that look exactly like this.
- The prompt recurs on every version bump (each versioned binary is a new TCC identity), multiplying the exposure and adding grant-fatigue.
Expected
The dialog should identify the product — e.g. "Claude Code (2.1.216)" — via a proper bundle/display name (Info.plist CFBundleName on a signed wrapper), or TCC identity should attach to a stable, well-named parent binary so the grant also survives updates instead of re-prompting per version.
Environment
- macOS (Darwin 25.5.0)
- Claude Code native install, auto-updated to 2.1.216
- Project directory under ~/Documents, hence the Documents TCC prompt
Reported on behalf of a founder-user who spotted it and asked that it be passed along: "2.1.216 means nothing and to an uneducated user could be an attack vector. Useful descriptors help a user in assessing permission."
🤖 Filed via Claude Code on the user's behalf
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗