[FEATURE] Scheduled tasks created by Claude Code/Cowork show as "bash - unidentified developer" in macOS Login Items

Resolved 💬 2 comments Opened Mar 1, 2026 by Onegin0 Closed Mar 29, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When Claude Code or Cowork creates scheduled tasks (launchd agents), each one appears in macOS System Settings → Login Items as a separate "bash - Item from unidentified developer" entry. This is because the plist files invoke /bin/bash directly, which isn't code-signed with an Apple Developer ID.

This creates a confusing user experience — multiple identical opaque entries with no indication they came from Claude. Users may not know what these are or whether they're safe.

Environment:

  • macOS (Sequoia / Sonoma)
  • - Claude Code / Cowork creating launchd agents in ~/Library/LaunchAgents/

Proposed Solution

Ship a signed helper binary or launcher with an Apple Developer ID certificate so that scheduled tasks appear as something like "Claude Code" or "Claude Cowork" in Login Items, rather than generic unsigned bash entries.

Instead of having the launchd plist invoke /bin/bash directly, it could invoke a small signed wrapper binary that then runs the actual bash command. This way macOS would display a recognizable, trusted name in System Settings → Login Items.

Alternative Solutions

No good workaround currently exists. Users can manually dismiss the Login Items entries, but they reappear whenever tasks are recreated. The only alternative is to not use scheduled tasks, which defeats the purpose of the feature.

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

<img width="714" height="1369" alt="Image" src="https://github.com/user-attachments/assets/5ebb4bd2-299b-4eda-8a51-d993f2041760" />

  1. User creates several scheduled tasks via Claude Code or Cowork (e.g., daily inbox check, weekly report)
  2. 2. Each task creates a launchd plist in ~/Library/LaunchAgents/ that invokes /bin/bash
  3. 3. User opens macOS System Settings → General → Login Items
  4. 4. They see multiple "bash - Item from unidentified developer" entries with no way to tell which is which or that they came from Claude
  5. 5. User is confused or alarmed, may disable them thinking they're malware
  6. 6. With this fix, they'd instead see "Claude Code" or "Claude Cowork" entries — immediately recognizable and trustworthy

Additional Context

Screenshot of the macOS Login Items showing the "bash - unidentified developer" entries attached.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗