Add calendar awareness to Pulse summaries

[2witstudios]

Pulse now includes calendar event data when generating AI summaries,
enabling time-sensitive observations like upcoming meetings, events
in progress, and pending RSVP invitations.

Changes:

• Query calendarEvents and eventAttendees in both on-demand and cron
  generation routes to fetch events happening now, upcoming today,
  and tomorrow
• Include pending RSVP invitations as context for gentle nudges
• Add calendar section to AI context data with categorized events
• Update system prompt with calendar awareness message type examples
• Add calendar stats (upcomingToday, pendingInvites) to GET /api/pulse
  response for real-time stat display
• Update PulseResponse type to include calendar stats

https://claude.ai/code/session_01X2zYjFPfB2Ha2k6HRYb2FT

Summary by CodeRabbit

• New Features
  • Pulse now provides calendar-aware insights by incorporating upcoming calendar events.
  • Events happening now, later today, and tomorrow are integrated into pulse content to improve relevance.
  • Pulse summaries now surface calendar statistics (upcoming today, pending RSVPs) and include a small sample of events.
  • Calendar visibility respects personal and shared drive permissions when showing events.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds calendar awareness to Pulse: new calendar-context module, system prompt extraction, calendar queries and counts, and integration of categorized calendar events into cron, on-demand generation, response payloads, and the pulse summary schema.

Changes

Cohort / File(s)	Summary
Calendar context module apps/web/src/app/api/pulse/calendar-context.ts	New fetchCalendarContext and PulseCalendarEvent interface: builds visibility filters, queries calendar events and attendee rows, deduplicates, sorts, and returns categorized lists (happeningNow, upcomingToday, tomorrow), pendingInvites, and allEvents.
Pulse generation (cron & on-demand) apps/web/src/app/api/pulse/cron/route.ts, apps/web/src/app/api/pulse/generate/route.ts	Import fetchCalendarContext and PULSE_SYSTEM_PROMPT; compute endOfTomorrow; inject calendar data into contextData and system prompt payloads; add "CALENDAR EVENTS" section and include sample events and counts in final summary.
Pulse API response & counts apps/web/src/app/api/pulse/route.ts	Adds stats.calendar (upcomingToday, pendingInvites) to PulseResponse; implements visibility-aware DB queries for upcoming events and pending invites and includes counts in responses.
System prompt extraction apps/web/src/app/api/pulse/pulse-prompt.ts	New exported PULSE_SYSTEM_PROMPT constant containing the workspace-assistant system prompt; replaces large in-file prompt strings in generators.
Schema / DB types packages/db/src/schema/dashboard.ts	Extends PulseSummary.contextData JSONB type to optionally include a calendar object with counts and an events array (title, startAt).
Manifest / package manifest_file, package.json	Minor manifest/package metadata updates referenced by diffs (unchanged public APIs).

Sequence Diagram(s)

sequenceDiagram
  participant Cron as Cron Job
  participant Generate as Generate API
  participant Calendar as fetchCalendarContext
  participant DB as Database
  participant AI as AI Model
  participant Store as Pulse Store

  Cron->>DB: load users / drives
  Cron->>Calendar: fetchCalendarContext(userId, driveIds, now, endOfTomorrow)
  Calendar->>DB: query calendar_events & event_attendees
  DB-->>Calendar: return categorized events & invites
  Cron->>AI: send context + PULSE_SYSTEM_PROMPT + calendar section
  AI-->>Cron: generated pulse summary
  Cron->>Store: persist pulse summary (contextData includes calendar)

Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• Add calendar event management API and UI components #334: Related calendar/events and websocket broadcasting changes that the new calendar-context and queries rely on.
• Add AI-powered Pulse summaries with scheduled generation #326: Directly modifies the same Pulse generation endpoints and schema; likely a precursor or companion to these calendar-aware changes.
• Add Google Calendar integration with OAuth and sync #369: Google Calendar sync integration that supplies calendar_events data used by fetchCalendarContext.

Poem

🐰 I scoped the day with a twitch and a hop,
Events and invites in a neat little hop—
I fetched what’s happening, tomorrow, and soon,
Poured them in pulses under moon and sun—
A rabbit-approved summary, short and bright! 🥕📅

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'Add calendar awareness to Pulse summaries' directly and clearly summarizes the main change: integrating calendar event data into the Pulse AI summary generation system.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch claude/add-calendar-awareness-CyYxk

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 4

🤖 Fix all issues with AI agents

In `@apps/web/src/app/api/pulse/cron/route.ts`:
- Around line 660-768: The calendar logic (calendarVisibility,
upcomingCalendarEvents, attendeeEventRows, pendingRsvps, merge/dedup, sorting,
and categorization) is duplicated and also ignores per-drive visibility
(PRIVATE) for non-creators; extract these into a shared helper (e.g.,
fetchCalendarContext(userId, driveIds, now, endOfToday, endOfTomorrow)) that
returns merged, deduped, sorted events plus pending RSVPs, then replace the
duplicated blocks in both cron/route.ts and generate/route.ts with calls to that
helper; while extracting, update the calendarVisibility construction used by
upcomingCalendarEvents and attendeeEventRows to explicitly exclude
calendarEvents with visibility = 'PRIVATE' unless eq(calendarEvents.createdById,
userId) or the driveId is in driveIds (i.e., only include drive events with
non-PRIVATE visibility or creator access), and ensure the helper accepts the
same parameters and enforces the same time bounds and limits used by
pendingRsvps.
- Line 32: The import symbol `lte` is unused in this module; remove `lte` from
the import list where it's declared (so the import statement no longer includes
`lte`) to eliminate the dead import and keep the file lint-clean—verify no other
references to `lte` (e.g., in functions or exports) exist before removing.

In `@apps/web/src/app/api/pulse/generate/route.ts`:
- Line 33: The import symbol `lte` is unused in the pulse generate route; remove
`lte` from the import list (the line that currently includes `lte`) so there are
no unused imports in the module and the linter stops flagging it.

In `@apps/web/src/app/api/pulse/route.ts`:
- Around line 172-203: The calendarVisibility logic currently uses driveIds to
include any event in those drives but ignores calendarEvents.visibility, leaking
PRIVATE/ATTENDEES_ONLY events; update the calendarVisibility construction so
that for the driveIds branch you only include drive-scoped events with
visibility = 'DRIVE' (or drive events the creator owns) and always exclude
calendarEvents with visibility = 'PRIVATE' unless eq(calendarEvents.createdById,
userId); additionally ensure ATTENDEES_ONLY events are not exposed via this
visibility filter (they should be returned only via attendeeEventRows or
eventAttendees joins) — update the calendarVisibility variable and the analogous
logic in the cron/generate handlers to combine checks on
calendarEvents.visibility, calendarEvents.createdById, driveIds, and membership
(via eventAttendees) so PRIVATE is creator-only and ATTENDEES_ONLY is limited to
creator and attendees.

🧹 Nitpick comments (1)

apps/web/src/app/api/pulse/generate/route.ts (1)

97-100: System prompt is duplicated across cron and generate routes.

Both PULSE_SYSTEM_PROMPT constants are identical (including the new calendar awareness section). This is a pre-existing concern amplified by the calendar additions — any future prompt tweak must be applied in two places. Consider extracting the prompt to a shared module (e.g., @/lib/ai/pulse-prompt.ts).