Repository navigation
v1.22.0
Changed
- Under Claude Code, CheICalMCP becomes its own responsible process for Calendar and Reminders (#343, v1.22.0): macOS charges an EventKit request to the responsible process the kernel assigned at spawn time, not to the binary, and Claude Code's background daemon launches sessions two ways: a spare-claimed session inherits the app that launched the daemon (on the reporting machine, VS Code), while a worker the daemon starts through
ClaudeCode.app(for example after Claude Code is restarted) is its own responsible process at~/.local/share/claude/versions/<ver>, which has no Calendar or Reminders purpose string, so macOS never shows a prompt and the session cannot read the calendar. When the responsible process macOS reports is Claude Code (its native executable under~/.local/share/claude/versions/<ver>, orClaudeCode.app), the binary now re-execs in place withposix_spawn+POSIX_SPAWN_SETEXEC+responsibility_spawnattrs_setdisclaim(the call Claude Desktop'sdisclaimermakes; looked up withdlsym), keeping its pid, argv and stdio, so macOS checks theCheICalMCPgrant and Claude Code updates no longer invalidate it (#170). This covers the MCP server,--cli,--print-tcc-pathand--setup;--setupalso re-execs under any host, because it is the foreground action that creates CheICalMCP's own grant. Every other host (Terminal, VS Code, Ghostty, ssh, cron, CI) keeps the behavior before this change: the host's grant is checked and nothing is re-exec'd, because a host's grant can be the only one that works while CheICalMCP's own is still empty.--version,--helpand--self-updatenever re-exec; Claude Desktop's.mcpbserver is already its own responsible process and is unchanged. Migration: under Claude Code theCheICalMCPgrant may be empty, so after upgrading allow the macOS prompt for CheICalMCP once, or run~/bin/CheICalMCP --setupin the foreground; a background session without a GUI cannot show the prompt. Trade-off: where the re-exec happens, macOS checks CheICalMCP's grant, so once it is allowed, any process Claude Code launches that execs this binary (including--cli) reads Calendar and Reminders under that grant without a separate consent, the same property Claude Desktop's.mcpbhas throughdisclaimer. SetCHE_ICAL_MCP_NO_DISCLAIM=1to restore host attribution (the behavior before v1.22.0); setCHE_ICAL_MCP_FORCE_DISCLAIM=1to re-exec under any host, for someone who wants CheICalMCP's own grant everywhere (NO_DISCLAIMwins over it). A missing private API or a failed re-exec prints one stderr line and continues under the host's attribution; an inheritedCHE_ICAL_MCP_DISCLAIMEDwhile Claude Code is still the responsible process also prints one. Not verified: CI does not cover reading the calendar through the new path under Claude Code, and the only path where a prompt has been seen is--setup; server mode and--cliunder Claude Code are unconfirmed. On the maintainer's machine the host (Ghostty) held a workingfullAccessgrant while CheICalMCP's own status wasnotDetermined, which is why other hosts are left alone.
Fixed
- TCC diagnostics name the process macOS checks (#343):
--print-tcc-pathprints aTCC attributionblock from the kernel (responsibility_get_pid_responsible_for_pid) before the status; the parent chain is relabeledProcess tree (parent chain — not what TCC checks), and its note no longer says the status reflects the chain. The startup banner's #175 check looked for aversions/path on the parent chain and blamed that host even when another process was responsible; it now reports the responsible process (hostAttributedUngranted) with advice for its kind. The access-denied message no longer tells users to "Enable access for the MCP server or Terminal": it names CheICalMCP, Claude Code (cannot be prompted) or the app whose grant is checked.--setupprints the authorization target before asking.
Plugin shell
The troubleshoot-tcc skill, /check-tcc and the plugin docs describe the new attribution; see plugin/CHANGELOG.md.