macOS TCC breaks after auto-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/themes/235/file
Follow it to file my report. Show me the text before you send.

Growing. 10 reports and thumbs-up in the last 7 days and 6 the week before. Not fixed, and no vendor reply yet.

Prompts titled with a bare version number ("2.1.x would like to access data from other apps / control this Mac") appear after each update
Granted folder and Automation permissions are lost each version; stale version-number entries pile up in Privacy & Security
Voice dictation in sessions started before an update fails with "No audio detected from microphone" as TCC denies the old process
Updater deletes a build that running sessions still execute; the terminal then loses access to ~/Downloads or ~/Desktop despite Full Disk Access
"ClaudeCode.app is damaged" Gatekeeper rejection after update, reported together with permission resets

Nov 2, 2026"ClaudeCode.app is damaged and can't be opened": background-session helper fails codesign (2.1.316)#106841
Nov 1, 2026Background sessions crash with EPERM on cwd after auto-update on macOS (TCC per-version path)#106597
Oct 29, 2026Native version cleanup deletes a build that running sessions still execute: the version lock protects only the first process (macOS → TCC attribution fails, Terminal loses ~/Desktop)#105861
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 28, 2026macOS: auto-updater deletes a running session's binary; the TCC denial then blocks ~/Downloads for the whole terminal despite Full Disk Access#105824
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

Show all 21Show only the newest 10

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
Oct 6, 2026Voice input fails silently after auto-update due to broken process attribution (macOS)#99892
Oct 5, 2026macOS Gatekeeper rejection + TCC permissions reset on every Claude Code update#99838
Sep 30, 2026macOS App Management shows unidentified binary "2.1.285" without app name or icon#98422
Sep 29, 2026macOS TCC re-prompts on every daemon update due to versioned binary paths#98208
Sep 29, 2026macOS reports ClaudeCode.app as corrupted on version 2.1.284#98065
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: voice dictation dies in every running session after the auto-updater replaces claude.exe ("No audio detected from microphone"; TCC denies the old PID)#94687
Sep 16, 2026macOS: auto-update triggers repeated, unlabeled "<version> would like to access data from other apps" TCC prompt#94683