Skip to main content
Development snapshot: the repository’s root package reports 0.9.1-beta, but GitHub does not currently have a v0.9.0-beta tag. The Electron package still reports 0.9.0-beta. These notes describe main as reviewed on July 20, 2026; they are not final release notes.
The main branch is 65 commits ahead of the published v0.9.0-beta tag. Work in this snapshot focuses on Template V2 consolidation, generation and editing workflows, MCP access, export runtime maintenance, and the application interface.

At a glance

Template V2

Generation, rendering, editing, and template identification now converge on the Template V2 model.

Focused MCP

The self-hosted MCP server exposes a restricted presentation-generation workflow with authentication support.

Editing experience

Ongoing work improves chat-assisted editing, autosave, element handling, and dashboard workflows.

Changes since v0.9.0-beta

  • Refactored presentation generation around Template V2 and removed obsolete template-processing code.
  • Unified template identification across generation and rendering.
  • Removed obsolete PDF/PPTX slide-processing endpoints while retaining PPTX and PDF presentation export.
  • Added a restricted MCP workflow for synchronous generation, asynchronous generation, and task-status polling.
  • Added bearer-token verification for MCP when application authentication is configured.
  • Kept MCP disabled in the Electron desktop app to avoid its authentication conflicts.
  • Improved chat and presentation-memory handling, slide UI editing, autosave, and image-editor behavior.
  • Updated the presentation export runtime to v0.4.2.
  • Updated the dashboard and presentation-management interface.

API compatibility

The self-hosted API remains under /api/v1/, but internal cleanup removed obsolete routes and changed implementation details. The current generation request supports:
  • Prompt content, optional slide Markdown, and additional instructions
  • Tone, verbosity, optional web search, slide count, and language controls
  • Template selection, title and table-of-contents controls, and uploaded files
  • PPTX or PDF export
  • Optional webhook triggering
Cloud v3 and self-hosted v1 are separate APIs. Do not copy a Cloud request into a self-hosted integration without adapting its URL, authentication, endpoint, and schema.

Before testing this snapshot

  1. Back up /app_data.
  2. Use an explicit commit SHA if you intentionally test main.
  3. Re-test Template V2 creation, presentation generation, editing, MCP authentication, and both export formats.
  4. Wait for a published tag before treating v0.9.0-beta as a release artifact.

Compare v0.9.0-beta with main

Review the complete commit and file diff for this development snapshot.

Open the latest commit reviewed

Inspect the repository state used for this documentation audit.

Published release

For a tagged artifact, use v0.9.0-beta and its version-specific documentation instead of these development notes.