macOS permission re-prompts on update

“A folder-access prompt appears again, naming the new version file.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/391/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Growing. 5 reports and thumbs-up in the last 7 days and 3 the week before, down from 6 a week at the early-October peak. Not fixed, and no vendor reply yet.

macOS privacy prompts reappear after every auto-update, labeled by version number. Permissions are registered by path (client_type=1) for each ~/.local/share/claude/versions/<version> binary, so prompts show "2.1.236" and stale entries cannot be removed.

Is this your bug?

File my report

Where: macOS native install
Error text: No such bundle identifier
Versions: 2.1.237 to 2.1.316
Platforms: macOS
How bad: Breaks a normal workflow. Some reports say it used to work.

Part of: macOS TCC breaks after auto-update4 bugs

ClaudeCode.app reported damaged7 people
Voice dictation dies after update5 people
Updater deletes running binary2 people

Not quite your bug?

Keychain Always Allow not persisting3 people

Original reports14, newest first

Nov 1, 2026Background sessions crash with EPERM on cwd after auto-update on macOS (TCC per-version path)#106597
Oct 28, 2026[macOS] TCC re-prompts for folder access after every native auto-update — permissions are keyed to the per-version binary path#105847
Oct 23, 2026macOS Documents permission prompt shows version number instead of "Claude"#104605
Oct 23, 2026macOS: background sessions lose Desktop (TCC) access after every update; Files and Folders gets one "claude" entry per version#104514
Oct 21, 2026macOS: Files & Folders gains a version-named entry on every update; denied entries cannot be removed (follow-up to #79053, #76615)#104167
Oct 20, 2026macOS TCC App Management prompt reappears after every update (native installer runs unbundled binary by version path)#103681
Oct 10, 2026macOS keeps prompting '"2.1.x" would like to control this Mac' after every update (native install binary path changes per version)#101084
Oct 8, 2026macOS Accessibility/Automation permission prompt doesn't identify Claude Code as the requester#100479
Oct 7, 2026macOS permission prompts and Privacy settings show Claude Code as a bare version number (e.g. "2.1.83")#100256
Sep 30, 2026macOS App Management shows unidentified binary "2.1.285" without app name or icon#98422

Show all 14Show only the newest 10

Sep 29, 2026macOS TCC re-prompts on every daemon update due to versioned binary paths#98208
Sep 25, 2026macOS: Claude Code shows up as three identities (Desktop "Claude", "claude", and per-version "2.1.x") with four separate copies on disk#97338
Sep 16, 2026macOS TCC permissions lost on auto-update due to versioned binary paths#94878
Sep 16, 2026macOS: auto-update triggers repeated, unlabeled "<version> would like to access data from other apps" TCC prompt#94683