rem CLAUDE.md

rem - CLI for macOS Reminders

Non-Negotiables

• Conventional Commits: ALL commits MUST follow Conventional Commits. Format: type(scope): description. Types: feat, fix, docs, style, refactor, test, chore, build, ci, perf. No exceptions.

What is this?

Go CLI wrapping macOS Reminders. Uses go-eventkit (cgo + Objective-C EventKit + private ReminderKit bridge) for fast reads AND writes (<200ms) as a single binary — including reminder CRUD, list CRUD, and flagged operations. AppleScript only for the default list name query. Provides CRUD for reminders/lists, natural language dates, and import/export. For programmatic Go access, use go-eventkit directly.

Architecture

• cmd/rem/commands/ - Cobra CLI commands (one file per command); huh_helpers.go has shared interactive utilities
• internal/service/ - Service layer: reminders.go and lists.go wrap go-eventkit client. executor.go runs osascript for the default list name query only.
• internal/reminder/ - Domain models: Reminder, List, Priority
• internal/export/ - JSON/CSV import/export
• internal/skills/ - Agent skill install/uninstall/status logic
• internal/update/ - Background update check (GitHub releases, 24h cache)
• internal/ui/ - Table (olekukonko/tablewriter v1.x), plain, JSON output
• skills/rem-cli/ - Embedded agent skill files (go:embed'd into binary)

Critical: Architecture Rules

• ALL reads AND writes go through go-eventkit (github.com/BRO3886/go-eventkit/reminders) — in-process EventKit via cgo, <200ms
• Single binary — go-eventkit's cgo code compiled into the binary
• AppleScript only for: default list name query (nothing else)
• Flagged is read/written via go-eventkit using the private ReminderKit bridge (same mechanism as URL attachments). EKReminder.flagged doesn't exist, but REMReminder.flagged does. Read via KVC (valueForKey:, not isFlagged selector — it's a dynamic property). Write via REMSaveRequest.updateReminder: change item, then changeItem.flaggedContext.setFlagged:, then saveSynchronouslyWithError:. Refetch the EKReminder after save so the returned dict reflects the new value. See journal 011. Graceful degradation (#44): like tags, flagged is set via a separate UpdateReminder call after the core create/update — if the private API is unavailable, rem warns on stderr and the reminder still succeeds. FlagReminder/UnflagReminder delegate to UpdateReminder(id, {"flagged":bool}) so all four flagged paths (add/update/flag/unflag) share one degradation policy: a private-API write failure warns + exits 0, a genuine error (not found) stays fatal. Requires go-eventkit ≥ v0.10.0 (v0.9.0 swallowed the flagged write failure silently). See journal 014.
• go-eventkit field names: Title (not Name), Notes (not Body), List (not ListName), native URL field
• URL field goes to REMURLAttachment, NOT EKCalendarItem.URL: EKCalendarItem.URL is a public property that's disconnected from the Reminders.app UI (Apple bug/limitation). go-eventkit v0.5.0+ writes to the real UI-visible URL field via a private ReminderKit bridge (REMSaveRequest → attachmentContext.setURLAttachmentWithURL:), guarded by respondsToSelector: with fallback to EKCalendarItem.URL. See journal 009.
• List CRUD via go-eventkit: CreateList (auto-discovers source), UpdateList (ID-based), DeleteList (ID-based). Immutable lists are rejected.
• List moves (#50): plain moves are native and ID-stable (public EventKit calendar reassignment; go-eventkit ≥ v0.11.0 also has a ReminderKit reparent rescue). Moves involving a shared list cannot be done natively — ReminderKit refuses at the account-capability level, and even Apple's paths (Reminders.app, AppleScript move) are copy+delete under the hood. rem detects the boundary via the sharing booleans on List (IsShared/SharedToMe/IsOwnedByMe, go-eventkit ≥ v0.12.0, read from the private REMList since public EventKit exposes no sharing state) and does copy+delete itself (moveViaCopy in internal/service/reminders.go), warning on stderr that the reminder gets a new ID. Because the ID changes, rem update prompts before a shared-list move (confirmSharedMove in update.go; skip with --force/-y/--yes, non-TTY errors without it — same convention as delete). Detection failures fall through to the native move. rem lists marks shared lists.
• Tags use the private ReminderKit hashtag API (REMHashtag, REMReminderHashtagContext). Title #hashtag parsing happens in rem only (not go-eventkit). Tags are written as a separate UpdateReminder call after the core create/update — if the private API is unavailable, rem warns on stderr but the reminder still succeeds. Pure-numeric fragments like #42 are filtered out by isNumeric() to avoid treating issue references as tags.
• Location reminders (#47) use PUBLIC EventKit (EKAlarm.structuredLocation + proximity, go-eventkit ≥ v0.13.0 — no private API, CoreLocation framework added for CLLocation). --location "lat,lng" + --radius + --on-arrive/--on-leave on add/update; proximity defaults to arrive. Coordinates only, no geocoding (CLGeocoder is async + needs network). Domain AlarmLocation lives on reminder.Alarm.Location; parseLocationAlarm() in filters.go. update --remind-me and update --location manage separate alarm buckets (splitAlarmsByTrigger()) — each replaces only its own kind, so --remind-me none keeps the geofence and vice versa. Geofences save without Location Services but never fire without it.
• Priority: 0=none, 1-4=high, 5=medium, 6-9=low
• due date and remind me date are independent
• rem add --due auto-attaches a zero-offset alarm by default (matches Apple Reminders.app). Use --silent to suppress. The alarm decision logic lives in buildAlarms() in filters.go — both CLI and interactive add paths call it. Do NOT pass --remind-me 0m to enable — it's the default.