#6933·screenpipe

Meeting summaries: missing decisions, owners and deadlines despite complete capture

Author: louis030195Created Sep 6, 2026Updated Sep 6, 2026

Problem

A user on Screenpipe 2.7.21, macOS 15.7.3, using Google Meet reports that the transcript and screen capture are available, but the first meeting summary omits or incompletely extracts decisions, owners, deadlines and unresolved questions. Repeated "Summarize again" attempts produced descriptions rather than an actionable meeting outcome. Supporting context was present in the transcript but not surfaced clearly.

This is a user-reported output-quality failure, not a locally reproduced model result. The original meeting content and generated notes remain private. The exact model/preset and selected summary pipe are not yet established; do not assume a particular model is at fault.

Code evidence and investigation boundary

The shipped buildMeetingSummarizeInstructions asks for topics, decisions and action items and preserves notes under ## Summary, but does not specify a complete outcome checklist. The inspected main version retains that general instruction. A selected/custom pipe may add instructions, so inspect the effective pipe and transcript coverage before concluding that changing this prompt alone fixes the report.

Existing prompt tests check routing, media boundaries and output streaming, not a semantic outcome scorecard.

Proposed reproduction and acceptance

Use an owned, synthetic meeting fixture, not customer recordings:

  1. Include one explicit decision, one task with a named owner and deadline, one task without an owner, and one unresolved question. Put some evidence near the end to detect truncated context.
  2. Run the ordinary first-summary flow with the shipped default and current effective pipe/preset. Record model, pipe revision, transcript rows/time range and any truncation, without raw private content.
  3. The first output should cover the categories below when supported. Unknown owners/deadlines must remain explicitly unspecified; do not invent them.
  4. Make supporting transcript timestamps navigable. Test empty/partial transcripts and conflicting statements.
  5. Preserve user-authored notes, respect custom summary instructions, and do not send the summary externally without approval.
Complete transcript + bounded screen evidence
                    |
                    v
             First summary
   +------------------------------------+
   | Decisions          | evidence time |
   | Action | Owner     | Due | evidence|
   | Open questions     | evidence time |
   | Unknown fields stay unspecified    |
   +------------------------------------+

Success means a useful first result on the fixture without repeated regeneration, with an explicit incomplete-data state when evidence is missing. Playback clarity is a separate issue; this report does not establish capture loss.