Create, correct and export a local AI slide deck

Agent-Native Slides documents a route from a prompt to an editable deck and a standalone HTML export. This guide is for readers comfortable with Node and terminal commands. It uses your own factual text to make three slides, corrects one named item, then checks the downloaded file. The steps are based on the product's documentation and inspected source code; we did not run the app or test an export.

The big change

• What changed: A generated deck can be edited as slides and downloaded as one HTML file for viewing.
• Why it matters: A source-to-slide check and one exact correction keep the reader responsible for factual content. The decisive check is in the exported file.
• What to watch: Local hosting covers the app, while the chosen model connection determines where prompt content is processed and what charges may apply. No fixed per-deck price or package-to-commit parity was established here.

Prepare the source and local app

1. Write a short source passage that you can verify. Keep its attribution, exact figures and dates alongside it. Mark one sentence or figure you intend to correct after generation, and write down the exact replacement. Use material you have permission to send to your chosen model provider. The local development server does not make a cloud model call local.
2. Install Node.js 22.22 or later and make pnpm available. In a terminal, run:

   npx --yes @agent-native/core@0.209.2 create my-slides --standalone --template slides
   cd my-slides
   corepack enable
   pnpm install

The pinned 0.209.2 is the npm package checked for this recipe. The repository code inspected below is a separate commit; we have not established that the published package contains precisely that code.

3. Connect a model before asking the agent to build the deck. For the documented OpenAI route, add OPENAI_API_KEY to the generated app's server-side .env now. Then run pnpm dev, open the printed local URL and choose Continue as local dev on Welcome. The port can change if 8080 is busy. Choose the model in Settings. Alternatively, start the app and use Custom keys to add a personal or organization credential. Keep the key out of prompts, screenshots and VITE_ variables, which can be exposed in browser code. Check your provider's access and pricing before sending the source: the framework's open-source license does not cover model usage.

Build and check three slides

4. Click New deck. Paste your source passage into the agent request and ask for exactly three slides using only those facts. Specify each slide's purpose in the request: the subject, the key facts, and the conclusion supported by the source. Ask the agent to preserve citations or attribution in the deck where needed. These are constraints for your own source, not a guarantee that generation will obey them.
5. Count the slides and compare every factual line against the original passage. Remove anything the source cannot support. Check that figures, dates, names and qualifications survive, and inspect the visible layout for clipped text. Do this before the planned correction so you can distinguish that one change from other errors.
6. Open the slide containing your marked item and double-click its text. Replace only that item with the exact wording or value you prepared. Read the corrected slide and the other two again. Slides also documents Revise with AI for selected text, but direct editing keeps this single correction bounded and avoids another model request.
7. In the editor, open Export and select Download HTML. Open the downloaded .html file in a browser. Count three slides, navigate forward and back, find the corrected text, and compare each slide's visible layout with the editor. Check the exported file itself: seeing the correction in the editor does not establish that it reached the download. The documented HTML format is a self-contained viewing file with keyboard navigation, not an editable PowerPoint file. Google Slides uses a separate PPTX import route.

If the export control is disabled, check that the deck contains slides. If installation reports a peer dependency error, the Getting Started guide suggests npx clear-npx-cache before retrying. For an unwanted edit, the Slides features guide documents version history and restore; verify the restored text before exporting again. These are documented recovery paths, not failures we observed.

Sources & further reading

• Getting Started gives the Node and pnpm requirements, local development steps, Welcome choice and setup recovery.
• Slides overview documents the scaffold command, New deck and deck generation.
• Slides features describes direct text editing, version restore and standalone HTML output.
• Environment Variables explains OpenAI key placement, Custom keys, model selection and browser-exposed variables.
• Pinned Export menu source shows Download HTML and its disabled state for an empty deck. This inspected repository commit is not proof of the npm package's exact contents.