Transcripts → tasks

A meeting changes the plan: new work comes up, dates move, something gets dropped. sprintrr reads the transcript and proposes those changes against the project you're in — new tasks, updates to existing tasks, and removals — and nothing touches the plan until you approve it.

How it works

1. Open a project and click Paste transcript in the project header, or press ⌘K and choose Paste a transcript. The window that opens is Paste a call transcript.
2. Get the transcript in:
   • Fireflies connected? Click Browse meetings and pick one of your recent meetings — the transcript loads with speaker labels, no copy-paste. Connect Fireflies once in Settings → Integrations → Fireflies with your API key (Fireflies → Integrations → Fireflies API). It's read-only: sprintrr lists your recent meetings and pulls the one you pick, and disconnecting deletes the stored key.
   • Anything else: paste the transcript — anywhere from a 30-line snippet to ~60k characters (a full hour-long meeting). Zoom, Teams, Meet, Otter and Granola transcripts all paste in as text.
3. Pick Quality or Speed (the current models are named in AI generation), or your own AI key if you've added one, then click Extract tasks (⌘↵).
4. sprintrr returns, for you to review:
   • A short summary of what the meeting was about.
   • New tasks — title, description, priority, category, a suggested due date and, when someone was named, an assignee hint.
   • Updates to existing tasks — a new status, priority, due date or milestone, each with the reason ("marked done in standup").
   • Removals — existing tasks the meeting made obsolete.
   • Risks it heard — blockers and concerns, kept separate from the plan.
5. Review each proposal. New tasks and updates start ticked; removals start unticked, so nothing is deleted unless you tick it. Edit titles, untick anything wrong, pick the real milestone and assignee, then click Apply changes. Flagged risks go to the risk register only if you add them.

Proposals show the line from the transcript they came from, so you can check each one against what was actually said before you apply anything.

Costs

1 AI Credit per extraction, charged only when it works (unlimited on your own AI key): the credit is taken when extraction starts and given back if it fails. It comes from the project's workspace: the team's pool when you hold a seat in that team, otherwise your own balance. Applying the changes afterwards is free — there's no second credit. See Plans & credits.

What works well

• Transcripts with speaker labels (Fireflies, Otter, Zoom, Teams, Meet): speaker attribution helps the assignee hint ("Sarah: I'll take the design review by Friday." → assignee hint: Sarah, due Friday).
• Granola exports: copy the "Notes" pane. Granola already pre-summarises to a structured outline, which the extractor handles well.
• Hand-typed notes: even rough bullets work. "- Sarah → design review, Fri" extracts cleanly.

What works less well

• Transcripts with no clear speakers and no clear verbs ("we talked about X"). The extractor is tuned for precision over recall — it skips vague intents rather than inventing tasks.
• Extremely long transcripts (60k+ characters are truncated). Split a half-day workshop into several extractions.

MCP usage

For Claude Desktop / Cursor users, extraction is also exposed via MCP. Over MCP it returns proposed new tasks and risks; updates and removals are reviewed in the app.

POST /api/mcp/transcripts/extract
{
  "projectId": "<uuid>",
  "transcript": "[paste here]",
  "mode": "quality"
}
 
→ { proposals: [...], risks: [...], summary: "...", meta: {...} }

Then, to create the ones you keep:

POST /api/mcp/transcripts/create-tasks
{
  "projectId": "<uuid>",
  "tasks": [ { "title": "...", "priority": "High", ... }, ... ]
}

Requires the write:tasks scope (default for new MCP keys).

Trust + data

• sprintrr reads only what you paste or the Fireflies meeting you pick; Fireflies is pulled on demand with your API key, read-only.
• Extraction doesn't save the transcript to your project — only the changes you apply are saved.
• Calls on your own AI key go directly to the provider you chose, with your key.
• Every extraction is logged in the activity feed with honest attribution: whether it ran on sprintrr credits or your own key, and which model.