Codex keeps a talk consistent across formats
Pierry reports using Codex around a 35-slide talk to update repeated content, preserve speaker notes and versions, and check its PowerPoint and companion formats.
crispierry.com
Original prompt
Shared by the source author. See source notes for context.
Use a single text box for all bullets within the same list.
Reach people exploring AI agents
See placements →What happened
Pierry reports using Codex around a 35-slide talk to update repeated content, preserve speaker notes and versions, and check its PowerPoint and companion formats.
Reported by Cristiano PierryHow the agent did it
- Keep the PowerPoint, narrative page and HTML deck as related editable sources.
- Have Codex trace an idea across repeated text and speaker notes.
- Update the affected versions and preserve numbered artifacts.
Where a person stepped in
Pierry checks editability, application rendering and narrative quality. Mechanical validation cannot decide whether the presentation serves the audience.
Cristiano Pierry describes presentation work in which the same talk exists as a PowerPoint, a narrative web page and an HTML deck. His sixty-minute Brown Bag presentation had reached PowerPoint version 101, with 35 slides and speaker notes for every slide. A late change could affect several artifacts, so editing the visible slide alone left other versions behind.
Codex works with the files surrounding the presentation to trace repeated ideas, update elements, transfer notes and preserve numbered versions. The project's checks inspect the PowerPoint package, numbering, hyperlinks, typography, footer positions and header geometry. The handoff also requires opening the exact final file in PowerPoint after a clean launch, because a valid package can still be repaired or rendered differently by the application.
Pierry also changed his generation instructions after reviewing a deck with separate text boxes for individual bullets. He asks for logical text groups that remain easy to move and revise. The reusable detail is to treat editability and consistency across formats as delivery requirements. Mechanical checks cannot decide whether the talk earns attention or whether the ending contains too much material; those decisions remain with the presenter. The source describes a real maintained presentation project, but does not independently quantify time saved or establish that every cross-format change is caught.
Prompt
Original prompt
Source: Blog · Cristiano Pierry
Frequently asked questions
Why is changing one slide insufficient?
The same idea can occur in speaker notes, the narrative page and the HTML deck, so a local edit can leave companion versions inconsistent.
Why open the exact final file?
A valid PowerPoint package can still trigger application repair or render differently; the handoff includes a clean application launch.
What remains a presenter’s judgment?
Attention, pacing, reading load and whether the ending contains too many conclusions are outside mechanical checks.
More details
Remaining steps
- Check package structure, numbering, links, typography and geometry.
- Open the exact final file in PowerPoint and review the talk as its presenter.
About this account
Codex inspects related files, propagates revisions, transfers notes and runs mechanical presentation checks before the human delivery review.
Firsthand account by Cristiano Pierry; original publication date verified against Article byline August 18, 2026. Outcomes are the author’s reports, not independently reproduced. Original excerpt from the author’s reusable presentation prompt; not the full template.
Credit: Cristiano Pierry
Source published 18 Aug 2026
Source checked 14 Oct 2026
Tools and topics
Codex · PowerPoint · HTML deck · Speaker notes · Package checks
Cross-format revisions · Editable text groups · Presentation versioning
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.