anthropics / anthropics/claude-code
Repeated "access data from other apps" (kTCCServiceSystemPolicyAppData) permission prompts every 2-3 minutes
- Langage dominant
- Python
- Étoiles
- 145k
- Forks
- 23.1k
- Métriques de merge des PR
- Métriques de PR en attente
Description
**App version:** claude-code 2.1.258 (macOS desktop app)
**Description:**
The desktop app repeatedly triggers the macOS "'claude' would like to access data from other apps" privacy prompt (Automation/App Data permission), roughly every 2-3 minutes, even when the app is idle and not actively being used for a task.
**Diagnosis from system logs (`log show --predicate 'process == "tccd"'`):**
Each recurrence corresponds to a new internal subprocess PID spawned by the app (e.g. parent 14937 → child 14998 in one instance, parent 9695 → child 9733 in another), each triggering a fresh `kTCCServiceSystemPolicyAppData` prompt via sandboxd. TCC does not appear to remember a prior Allow/Don't Allow answer across these subprocess launches — suggesting the code signature/identity isn't stable between spawns, so macOS treats each one as an unverified requester.
**Impact:** Interrupts the user every 2-3 minutes regardless of whether Claude Code is in use.
**Expected:** Permission should be requested once and persist, or the background process triggering repeated `kTCCServiceSystemPolicyAppData` checks shouldn't need to re-request per subprocess launch.
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Start by reproducing the prompt and running `log show --predicate 'process == "tccd"'` while recording the parent and child subprocess PIDs. Compare the spawned processes' code-signing identity and TCC behavior around `kTCCServiceSystemPolicyAppData`. Done means an idle app no longer prompts every 2–3 minutes and an Allow or Don't Allow decision persists across subprocess launches.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- macos, python
- Domaine
- desktop, operating-systems, security
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Active
- Clarté
- Plutôt claire
- Accessibilité débutants
- 48/100