macOS: background osascript after auto-update triggers "<version> wants access to control iTerm" Automation prompt

Environment

• macOS 27 (Darwin 27.0.0), Apple Silicon
• Claude Code native installer, auto-updating; 2.1.287
• iTerm2 as terminal, background jobs (bg daemon) in use

What happens

About a minute after an auto-update, with no Claude Code session in use (I was watching a video in Chrome), macOS showed:

"2.1.287" wants access to control "iTerm". Allowing control will provide access to documents and data in "iTerm", and to perform actions within that app.

I didn't open any claude-cli:// link or start a session.

Timeline (unified log, 2026-10-01)

• 19:12:47: ~/.local/share/claude/versions/2.1.287 installed (file birth time)
• 19:13:23: bg daemon starts a spare: claude bg-pty-host … -- ~/.local/share/claude/versions/2.1.287 --bg-spare …
• 19:13:40: same process family requests kTCCServiceSystemPolicyAppDataDetailed for com.google.Chrome (responsible com.anthropic.claude-code, pid 69588)
• 19:13:41: pid 69588 spawns /usr/bin/osascript (pid 69632), which sends AppleEvents to iTerm and triggers the Automation prompt (tccd attribution: responsible com.anthropic.claude-code at versions/2.1.287, accessing com.apple.osascript)

Where it comes from

The only tell application "iTerm" script in the 2.1.287 binary is the deep-link terminal launcher (create window with default profile / write text …). The debug logs have no "Launching in terminal" entry, so it's unclear why that path runs after an update.

Expected

No AppleEvents to the terminal unless I actually open a deep link.

Related

The prompt recurs per version because TCC grants are keyed to the versioned binary path: #80899.