Connect project context and upload recordings
Project-aware connector tools, transcript-backed intelligence, browser uploads and a voice-identification choice expanded the workspace.
Read MarkdownDates describe development history and do not verify when changes became available.
Development period: to
Read projects and correct meeting links through MCP
Added project-aware connector tools, including confirming or excluding a meeting’s project link for owners and admins.
Project reads followed the caller’s access. Changing a link also required the appropriate tool scope and an owner or admin role.
Read intelligence with supporting transcript passages
Added a connector tool returning meeting intelligence with timestamps, speaker labels and quoted transcript passages.
Items could have one or more supporting passages, or none. The tool respected the caller’s scope and access to the meeting.
Read project updates from a saved point
Added a connector change feed with a resumable cursor for accessible meetings linked to a project.
The feed also reported excluded links, letting a connector update context when a meeting no longer belonged to the project.
Notify a configured GitHub repository
Added processed-meeting events for repositories configured on active project links.
The event carried meeting and project identifiers and the processing time, allowing a repository workflow to fetch context. Sending the event did not confirm that a GitHub workflow ran.
Upload a recording in the browser
Added a recording upload page with drag-and-drop, file selection and progress states.
The form checked supported audio or video file types and the upload-size limit before starting.
Choose whether to use voice identification
Added an off-by-default voice-identification control, with confirmation before turning it off.
Turning it off withdrew consent and removed stored voice-identification data, rather than meeting transcripts. Deleting a reference clip alone did not turn the setting off.