Hand a Hedy Deck 2.0 project to Presenter

Use Studio for the current V2 format. No Hedy admin connector or account is needed for local authoring. Read the V2 specification and agent tools first.

A browser that can click, type, and read

Open /studio. Its source editor accepts a complete V2 JSON document. Its Agent command desk form lets you select a hedy2_* tool, paste its JSON arguments, and run the same operation exposed through WebMCP. Read the visible result before taking the next action. A browser agent does not need WebMCP to fill the source or request field and click the corresponding button.

Create or import a source project, inspect the slide previews and diagnostics, revise it, then render it for presentation. Download the editable .hedydeck package as the durable handoff. A browser-only agent can also open an existing package using the file picker when its browser tools support file upload.

WebMCP or page JavaScript

Discover tools on the page. Use hedy2_instructions for the current contract, hedy2_create or hedy2_import to create a project, hedy2_read to inspect it, and hedy2_edit for precise revisions. The same tools are callable through window.hedyDecks.tools.call(name, input) where that interface is listed.

These operations run in the browser containing the project. A different browser session has different local data. Merely sharing the Studio URL does not grant access to another device's drafts.

An agent with file tools

Write the source JSON described by the specification, or assemble the documented ZIP package using ordinary ZIP tools. Give the user a real file attachment. Open it in Studio for structural checks, browser layout checks, and visual inspection before claiming that it is ready to present.

Use a .json filename for readable monolithic source and .hedydeck for the ZIP package. Exporting from Studio is the easiest way to obtain the canonical package and asset hashes. Keep the editable package even after successful presentation.

For remote HTTP delivery of a ZIP file use Content-Type: application/zip and Content-Disposition: attachment; filename="your-title.hedydeck". The extension alone does not install an operating-system file association.

An expiring link across browsers

Use Studio's temporary handoff control or hedy2_handoff({id,expectedRevision,idempotencyKey?}) to upload a saved source snapshot and receive an open link and a download link after completion. This is an explicit optional upload: it sends editable source, assets, and notes to server storage. The limit is 25 MiB and the default lifetime is 24 hours. Anyone with the complete link can retrieve that snapshot until expiration or revocation. Later local edits are not synchronized.

An agent with HTTP and file tools can publish a complete V2 JSON file or ZIP directly using POST /api/handoffs, the returned upload instructions, and completion. See temporary handoff for the exact protocol, runnable Python and curl examples, retries, revocation, and capability handling. This transfer API does not require WebMCP or an existing browser project.

An ordinary chat conversation

A chat agent can draft a complete V2 JSON source or an editing request. A person copies it into Studio, runs the operation, and returns the visible diagnostics to the conversation. To revise an existing deck, start from its exported or copied source, including its IDs and revision. Do not invent the current revision or claim an edit succeeded without observing the result.

Current boundaries

  • V2 authoring has no public REST editing endpoint and no separate remotely connected MCP server. The temporary handoff HTTP API transfers complete files; it does not edit browser projects.
  • The existing /api/validate, temporary CAPTCHA-protected dropbox, and compressed #deck= link are legacy HTML workflows. They are not V2 ZIP or source APIs. See V1 handoff if deliberately using that earlier path.
  • TURN and live room codes support presentation connectivity. They do not authorize editing a Studio project and do not pair two Studio sessions.
  • A saved source project is local to this browser. Export it for durable backup, or explicitly create an expiring handoff for transfer. Closing a chat session is not an export or upload.
  • Speaker notes travel in the existing playback bundle. Do not include confidential notes in a presentation being distributed to viewers.