Skip to content

Meeting prep: inline attendee notes under upcoming meetings#636

Open
Gagancreates wants to merge 3 commits into
devfrom
feat/meeting-prep-card
Open

Meeting prep: inline attendee notes under upcoming meetings#636
Gagancreates wants to merge 3 commits into
devfrom
feat/meeting-prep-card

Conversation

@Gagancreates

Copy link
Copy Markdown
Collaborator

What

Adds meeting prep to the Meetings view: for an upcoming meeting, it resolves the attendees against the knowledge base and shows each person's person.md inline — deterministically, no LLM in the hot path.

  • The next meeting auto-expands its prep; every other meeting with attendees gets a ✦ Prep toggle that resolves lazily on open.
  • Notes-first: attendees with a note render as expandable rows (rendered markdown + "Open note"); the rest collapse into a "N others — no notes yet" row with a Create note action that hands off to the Copilot (scheduled-meeting attendees are exempt from the note-creation email-reply gate, so this generally succeeds).
  • Companies: external organizations in the meeting (resolved from attendee email domains, excluding your own domain) are surfaced as their own notes.

How it works

  • New core resolver resolveMeetingPrep() (packages/core/src/knowledge/meeting_prep.ts) + meeting-prep:resolve IPC. Matches email-exact first, then an unambiguous name/alias match (display names normalized to strip (via …) suffixes).
  • Reads a cached knowledge index instead of rescanning the whole knowledge/ dir on every resolve; the cache is invalidated whenever a file under knowledge/ changes (wired to the workspace watcher).

Incidental fix

extractField in the knowledge index consumed newlines after a field label, so an empty field (e.g. **Role:**) bled the next line's value. Restricted it to spaces/tabs so empty fields resolve to undefined. Also strips the folder prefix from link targets for display (Organizations/Rowboat LabsRowboat Labs).

Test

Open the Meetings view; prep appears under the next meeting, and any meeting row exposes a Prep toggle. Verified: npm run deps, tsc --noEmit (main + renderer), and npm run lint all clean (no new errors).

Notes / follow-ups

  • A PLAN.md at the repo root documents the design decisions.
  • Not in scope (discussed): an opt-in LLM-synthesized brief (recent activity + agenda) and a proactive pre-meeting nudge.

Resolve a meeting's attendees against the knowledge base and render each
attendee's existing person.md inline beneath the next upcoming meeting in
the Meetings view. Deterministic (email-exact match, then unambiguous
name/alias), no LLM in the hot path.

- core: resolveMeetingPrep() + meeting-prep:resolve IPC
- renderer: notes-first rows with expandable person.md; unmatched attendees
  collapse into a 'no notes yet' row with a Create note action that hands
  off to the Copilot
- prep re-resolves when a People note changes
Add a Prep toggle to every eligible meeting row, not just the next one.
The next meeting still auto-expands; other meetings resolve their attendee
notes lazily when their toggle is opened. All-day and solo events get no
toggle.
#2 Matching: resolve the meeting's external companies from attendee email
domains (and matched people's Organization field), excluding the user's own
domain, and surface those org notes in a Companies section. Normalize display
names (strip '(via ...)' suffixes) before name/alias matching.

#3 Perf: meeting prep reads a cached knowledge index instead of rescanning the
whole knowledge dir on every resolve; invalidated whenever a file under
knowledge/ changes (wired to the workspace watcher).

Fix: extractField in the knowledge index consumed newlines after the label, so
an empty field (e.g. **Role:**) bled the next line's value. Restrict it to
spaces/tabs so empty fields resolve to undefined. Also strip the folder prefix
from link targets for display (Organizations/Rowboat Labs -> Rowboat Labs).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant