Claude Desktop already ships the schema for handing meeting follow-ups to agents

RuntimeWire reports that shipped Claude Desktop builds contain the full specification for an unreleased, Mac-first meeting recorder codenamed Parka, which turns meeting transcripts into follow-up actions destined for Cowork, Claude Code, or a person, with the feature disabled and its native implementation and interface missing from public packages ^[1]. The consequential part is not the recording. It is that the routing decision has already been given a data structure.

According to RuntimeWire, Claude Desktop 1.32885.1 carries an extensive Parka interface contract covering meeting creation and deletion, system and microphone audio capture, calendar metadata, transcription keyterms, live speaker-attributed transcript events, summaries, notes, granular editing, and error states ^[2]. The action schema gives each follow-up a title, description, owner, full prompt, execution type, an autoRunnable value, and an optional Claude session URL ^[3]. The execution types are cowork, code, and manual ^[4].

Read that field list as a product decision rather than a data model. A title and description are what a notetaker produces. A full prompt, an owner, an execution type and an autoRunnable flag are what a dispatcher produces: two of the three destinations are automated lanes and one is a human ^[1]. The optional session URL implies the artifact of a meeting is a link to work already in progress ^[3]. Everyone selling transcription is selling the summary. This schema is specified to skip the summary and start the job.

The evidence that it is not close to shipping is equally specific. RuntimeWire says packaged builds force parkaMeetings to an unavailable status ^[5], and that the gate returns unavailable before it ever reaches the macOS 13-or-later support check ^[6]. The native Parka loader in both the Mac and Windows packages is an empty 551-byte stub ^[7]. When RuntimeWire used Chrome DevTools Local Overrides to change the renderer's two Parka bootstrap values to supported, Claude loaded normally but showed no meeting interface and no navigation item, made no observable listParkaMeetings call, and fetched no Parka-specific JavaScript chunk ^[8]. Three separate pieces are therefore absent at once, and the interface contract is effectively the only part of Parka that customers have actually received ^[2].

On the transcription engine, RuntimeWire is careful. It identified Anthropic-controlled Titanium hosts with names resembling Deepgram's Nova-3 and Flux speech models ^[9], and notes that Parka's keyterms argument resembles Deepgram's Nova-3 Keyterm Prompting interface ^[10]. The desktop package contains no Deepgram hostname, SDK, credential, or other vendor attribution, so RuntimeWire treats the connection as unconfirmed ^[11].

The work was done by reverse engineering, and RuntimeWire says it independently reproduced the core finding across the macOS universal DMG, the Windows x64 archive, and a renderer asset retrieved on August 19, 2026 ^[12][13]. It compared the recovered behaviour against public documentation from Anthropic, Apple, Notion, Granola, and Deepgram ^[14].

Watch three things in the next renderer asset: whether a Parka-specific chunk appears at all, whether the native loader grows past 551 bytes on Windows as well as Mac, and what autoRunnable is permitted to default to. A meeting tool that can silently start a Claude Code session on your repository because someone said "let's fix that" is a different product from one that writes it down.