[BUG] Automation (TCC) permission for node resets after every Claude Code update

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 14, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

After updating Claude Code, macOS re-prompts for the "would like to access data from other apps" Automation permission for the requesting process (shown as node in System Settings → Privacy & Security → Automation), even though it was already granted and had persisted across prior updates. This suggests the requesting binary's code identity changes on update, causing TCC to treat it as a new/unrecognized requester.

What Should Happen?

Automation grants should persist across Claude Code updates, the same way they do for other signed apps (e.g. Chrome, which stays granted).

Error Messages/Logs

Steps to Reproduce

) Grant Claude Code's automation prompt once (Allow). 2) Confirm it works and the grant is listed under Automation settings. 3) Update Claude Code to the latest version. 4) Trigger the same automation action again → macOS re-prompts for permission as if never granted.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Previous version

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗