Codex Slides: An Image-Native Deck Studio That Runs Inside Your Coding Agent
🎨 Open-source AI slide studio inside Codex: image-native decks, every slide a full visual canvas. ⚡ 10+ high-quality slides in ~4–5 minutes — Fast mode renders every page in parallel. 🔍 Watch the whole chain live: research → outline → style → render → edit → present → export PDF/PPTX. 🖥️ Browser-first · zero API keys · durable projects.
At a glance
- What is it?
- Codex Slides is an MIT-licensed TypeScript slide studio that installs as a Codex plugin and renders decks as full-slide images on your existing codex login. The trade-off is explicit: high visual fidelity, but exported PPTX files contain pictures, not editable PowerPoint shapes.
- Who is it for?
- Adopt Codex Slides if you want visual-first decks, already run Codex, and accept that PPTX export ships full-slide images rather than editable shapes. Skip it if downstream editors need to move text boxes in PowerPoint, or if you cannot run the Codex plugin commands in your environment.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 57 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The Problem: One-Shot Generators Hide the Deck Until It Is Wrong
Most AI slide tools take a prompt, run an end-to-end task you cannot watch, and hand back a file. The README frames Codex Slides against exactly that pattern: a table contrasts the typical one-shot generator, where you "wait for a hidden end-to-end task" and "discover problems after export", with an approach where the product is open before work begins and requirements, outline, and style are confirmed first. The intended user is a developer already working inside Codex who wants a deck without leaving the agent. The README's example prompt is telling: create a 12-slide market deck about 2026 humanoid robotics, and "let me confirm the questions, outline, and visual direction before rendering". That confirmation step is the product's thesis. If you never want to review an outline, this workflow adds friction rather than removing it.
The Pipeline: Research, Outline, Style, Render, Edit, Present, Export
The README documents a seven-stage chain drawn as a diagram: research, outline, style, render, edit, present, export. In practice the flow starts in a Codex conversation, opens the Codex Slides home in the Codex Browser, and creates a durable project. From there the stages are clarify the brief, optional source-backed research, review and revise the outline, choose a visual direction, watch slides render progressively, then review the finished canvas. Post-render operations listed in the README include chat edits and queued follow-ups, add, duplicate, move, delete and transition operations, mark-based slide edits, Design Files with @ references, saving a project as a reusable template, a Brand and Design System, play mode, and PDF or PPTX export. Projects are written to disk throughout the workflow, and the README states the same project can be opened from Codex and another browser. That shared-project model is the architectural claim worth noting: the agent and the UI are not two histories to reconcile.
Image-Native Rendering and What It Costs You in PowerPoint
Codex Slides is image-native: each slide is composed as a full visual canvas. The README is direct about the consequence, stating that exported PPTX files contain full-slide images rather than individually editable PowerPoint shapes. This is the single most important constraint in the repository, and it is stated rather than buried. If your workflow ends at presenting or at a PDF, the model is fine and arguably better for visual fidelity and rapid iteration. If a colleague must open the PPTX and reposition a text box, recolor a chart, or fix a typo in a bullet, they cannot, because there are no shapes to select. The README also notes Fast mode renders every page in parallel rather than one by one, and gives a figure of 10+ high-quality slides in roughly 4 to 5 minutes. That is a documentation claim, not something verified here. Treat it as a target to confirm on your own machine and network, since render time will depend on your Codex setup.
Installing It: Two Commands and a Prompt
The README gives two installation commands for the Codex plugin marketplace, then a prompt to start a task. The commands are: codex plugin marketplace add nexu-io/codex-slides and codex plugin add codex-slides@codex-slides. After that, the README says to start a new Codex task along the lines of "Open Codex Slides and build me a 6-slide deck about ...". The project advertises zero separate API keys and states it runs on your existing codex login, which matters because it removes a billing and secrets step from setup. The README also lists a CLI and MCP section in its table of contents and an MCP badge reading 38 tools, so an MCP interface exists, but the supplied material does not include the tool names or CLI flags. Do not assume specific subcommands beyond the two plugin commands quoted above. Local development and desktop development sections are also listed in the contents, but their contents are not in the material provided here.
Visual Systems, Scenarios, and Export Options
The README counts 118 ready-made visual systems: 45 curated deck templates across 15 professional categories, plus 73 community styles across 12 groups including reports, infographics, diagrams, data and maps, dashboards, posters, product, brand, architecture, photography, editorial, and illustration. It also lists 24 guided scenarios in 6 groups, covering zero-to-one decks, source-to-slides, data stories, deep research, redesign, localization, training, and keynotes. Export supports PPTX and PDF, with speaker notes preserved according to the README, plus 1K, 2K and 4K render quality and five aspect ratios: 16:9, 4:3, 1:1, 9:16 and 3:4. The community style library has its own README section titled "Community style library and licenses", which suggests those 73 styles carry their own licensing terms separate from the project's MIT licence. The supplied material does not enumerate those terms. If you plan to ship decks commercially, check that section before relying on a community style.
Where It Breaks Down: Editing, Environment, and Hidden Assumptions
The clearest failure mode is downstream editing, covered above: image-native slides cannot be restructured in PowerPoint. A second limitation is environmental. The workflow is browser-first and depends on the Codex Browser and a working codex login. Teams that cannot run Codex plugins, or that work in environments where the in-app browser is unavailable, are outside the supported path. A third is that the README's speed figure depends on parallel rendering in Fast mode; the documentation does not describe what Fast mode sacrifices when it renders every page in parallel, though it says the outline and visual direction stay locked. Whether quality drops on dense slides is not stated. Finally, the material provided here is truncated partway through the "How it works" section, so the architecture and data section, the verification section, and the troubleshooting section are not available to assess. Anyone evaluating durability or data layout should read those sections directly in the repository.
Compared With Gamma: Visible Chain Versus Hosted Convenience
The README positions Codex Slides as an open-source, agent-native alternative to Gamma and Tome, and its own comparison table makes the difference concrete. A hosted generator like Gamma takes a prompt in a web app and returns a deck; the process is a single request, context is re-uploaded per session, and the result lives in that service. Codex Slides inverts several of those properties. The project lives on your disk, the chain from research to export is visible and steerable stage by stage, a successful visual direction can be saved as a reusable project template, and visual bugs can be marked directly on the slide rather than described in prose. The cost of that control is setup and environment: you need Codex, the plugin commands, and the in-app Browser. Gamma needs none of those. If you want a deck in one request and do not care about the intermediate steps, the hosted tool is the shorter path. If you want the intermediate steps to be yours, and to keep the project on your own disk, Codex Slides is built for that.
Licence, Maintenance, and What to Check Before You Commit
The repository is MIT licensed, which permits commercial use, modification and redistribution under the standard terms; this is not legal advice and you should read the LICENSE file yourself. Version history shows v0.1.0, v0.2.0 and v0.2.1 all released on 2026-07-13, with a last push on 2026-07-21. Three releases in a single day suggests rapid iteration rather than a settled API, so pin to a version if you build on the MCP surface. The README lists a Roadmap section, but its contents are not in the supplied material, so upgrade direction cannot be judged from here. Maintenance cost centres on the Codex plugin dependency: when the plugin interface or the Codex Browser changes, the install path changes with it. The two commands to re-run are codex plugin marketplace add nexu-io/codex-slides and codex plugin add codex-slides@codex-slides. Verify first that a rendered 16:9 deck at your chosen render quality exports to PPTX with speaker notes intact, and check the community style library's licence terms for any style you intend to ship.
Editorial conclusion
Adopt Codex Slides if you want visual-first decks, already run Codex, and accept that PPTX export ships full-slide images rather than editable shapes. Skip it if downstream editors need to move text boxes in PowerPoint, or if you cannot run the Codex plugin commands in your environment. Before committing, install it and confirm two things in the rendered output: that the deck's aspect ratio and render quality match your target, and that the exported PPTX opens with speaker notes preserved.
Community notes