Transcribe Meeting

Transcribe Meeting

A recording becomes a usable brief in three tool calls. Each one produces a file the next one reads — nothing is passed inline, because a 46-minute meeting is ~135,000 characters against a 60,000-character tool-result budget, and a summary built from the truncated half looks finished rather than truncated.

Procedure

1. Confirm the file exists, and set expectations. If the path is not there, say so and quote it — never describe a recording from its filename. Measured on a 46-minute recording: ~6 min to transcribe, ~4 min to separate the voices, ~1-2 min to name them and summarize — about 11-12 minutes, or roughly 4x realtime. Say that before you start, not after the user has waited.

2. Transcribe. transcribe_media(file_path). Pass output_path to write elsewhere, language to skip auto-detection. The transcript is written before anything downstream runs, so it survives a later failure; if the call errors, report its message as given — it names the missing component and the command that installs it.

   preview is the first 1200 characters, for identifying the recording only. low_confidence_spans and low_confidence_span_count are informational — step 3 does the correcting. Do not repair them yourself.

3. Refine — one call, and it is not your work to redo. refine_transcript(transcript_path) groups the transcript by the voices already separated from the audio, puts names to them where the conversation supports it, writes the result and indexes it. You do not work out the speakers yourself, do not rewrite wording, and do not write a transcript file. Summarizing the raw transcript instead produces a brief with no owners on the action items.

   It needs the timings saved alongside the raw transcript. If it reports they are missing, re-run transcribe_media on the original media rather than trying to segment the text yourself — turn boundaries guessed from prose are invented, not observed.

4. Report both paths, every time. State the raw transcript_path and the refined_path in your reply — even when the user only asked for action items, even if a later step fails. Transcription costs minutes of compute; a user who does not know the files exist pays for it twice.

5. Summarize. refine_transcript already indexed the file, so go straight to summarize_document(refined_path, summary_type='detailed'), which folds the whole transcript forward in sections so the brief covers the entire meeting.

6. Remember the outcome, not the transcript. remember a short record of the meeting: what it was, when, who was in it, the decisions, and any action item the user personally owes. Two or three sentences.

   The transcript is already indexed — that is what detailed questions read from. Memory is for the durable facts that should surface without being asked, weeks later, when the user says "what did I commit to?" or a related topic comes up in a different conversation.

   Do not store the transcript, long quotes, or the full brief in memory. That duplicates the index, crowds out everything else the user asked to be remembered, and gets recalled in conversations it has nothing to do with. Store nothing when the recording turned out to be something other than a meeting.

7. Invite the follow-up. Close by telling the user they can ask questions about the meeting and you will answer from the indexed transcript. They will not discover this on their own.