Receipts: RuntimeWire mapped OpenAI's Office workflow 20 days early

Why it matters

OpenAI's visible Office expansion validates the workflow RuntimeWire found in production code, while the still-gated review queue points to comments becoming task dispatch for agents.

OpenAI added ChatGPT to Microsoft Word today, September 17th, completing an add-in lineup across Word, Excel and PowerPoint 20 days after RuntimeWire exposed a deeper Office workflow already embedded in OpenAI's desktop software.

The timing is the receipt. On August 28th, RuntimeWire reported that OpenAI had built a gated system for assigning work to ChatGPT from selected Excel cells, charts, PowerPoint slides and shapes. The implementation could collect several requests into a review queue, let ChatGPT edit the underlying Office file and return a separate reply to each assignment.

On September 17th, OpenAI's ChatGPT release notes said Word had joined Excel and PowerPoint through the same Microsoft add-in. Users can revise selected text and change headings or formatting from a ChatGPT sidebar. The Word release gives OpenAI a ChatGPT surface inside each of Microsoft's three core Office creation tools.

That public rollout confirms the strategic direction RuntimeWire identified. It does not confirm every unreleased component found in the August desktop package.

August 28th: the code showed a review queue

RuntimeWire examined the production app.asar distributed with Windows package OpenAI.Codex_26.825.4187.0. The client contained a feature called Artifact comments, protected by a rollout gate.

The implementation supported two comment systems over the same Office file. One wrote native comments into Excel and PowerPoint files. The other created persistent, private assignments for ChatGPT that were tied to a selected object or cell range and were not exported with the Office document.

A user could select a range, chart, slide, shape or other presentation element and choose "Ask ChatGPT for a change." The interface also included an "Add to review" action that accumulated multiple assignments before sending them to the agent as a batch.

Those assignments were not ordinary chat prompts. The client packaged the target, file path, thread identifier and available preview into a dedicated artifact_comment turn. ChatGPT was instructed to address every thread, make requested edits and return one structured artifact-comment-reply for each assignment.

The replies were routed back into their corresponding threads. The interface tracked pending, unread, resolved and reopened states, while leaving final resolution to the user.

RuntimeWire also traced how edits persisted. PowerPoint changes were serialized back into PPTX bytes through bundled OpenXML infrastructure. Excel changes passed through a workbook update system that recalculated the file and materialized a new XLSX version, with handling for write conflicts, external changes and failed saves.

This was an implemented review architecture inside production software, rather than a generic indication that OpenAI wanted ChatGPT to work with spreadsheets someday.

September 17th: Office becomes a product line

OpenAI's Word release follows the broader Office and artifact strategy it began describing publicly after RuntimeWire's report.

OpenAI introduced GPT-6 Astra on September 3rd, six days after the investigation, and said the model could produce documents, spreadsheets and presentations while following templates and adapting to revised instructions. OpenAI's Astra materials now show spreadsheet and presentation work as central professional-use cases.

OpenAI's ChatGPT Work documentation also describes opening supported files beside a conversation, selecting a specific portion and requesting a revision. Through the Excel add-in, Codex can inspect and update sheets, formulas, values, formatting and charts in an open workbook.

The products are separate in ways that matter. OpenAI says PowerPoint is not included in the desktop Work flow at launch, even though ChatGPT for PowerPoint is available as a Microsoft add-in. The gated system RuntimeWire found sat inside the ChatGPT and Codex desktop client and handled Excel and PowerPoint artifacts through a common review interface.

What the public release confirms

The overlap is now clear in four areas.

OpenAI is treating Office documents as active work surfaces rather than static attachments. Instructions can be scoped to selected content. ChatGPT can make edits instead of returning text for users to paste manually. OpenAI is building the resulting interactions around review, with users expected to inspect changes before saving or sharing them.

OpenAI has not publicly documented the specific Artifact comments name, the private assignment layer, the "Add to review" batch queue or the structured protocol that routes one agent response back to each Office comment. OpenAI's public pages also do not establish that the gated desktop implementation RuntimeWire examined is generally available.

That distinction keeps the August findings ahead of the current documentation. The public product now matches the broad workflow, while the code described the machinery OpenAI could use to turn comments into an agent task queue.

The strategic step sits inside that queue. An Office sidebar can answer questions or revise one selection at a time. A comment-driven assignment system converts document review into delegated work: mark the cells, slides or shapes that need attention, send the batch and review the resulting file after ChatGPT completes each thread.

OpenAI's September 17th Word launch rounds out the visible Office push. RuntimeWire's August 28th investigation showed where that push can go next, down to the thread states, file formats and agent-turn protocol.

NOTE TO EDITOR: Objection: this is not a duplicate of the Word launch story. The existing canonical article reports the product launch: ChatGPT added to Word and the Office add-in expanding across Word, Excel and PowerPoint. This draft has a different news peg, evidence base and editorial purpose: OpenAI’s September 17th marketing now publicly demonstrates an Office-native review workflow that closely matches RuntimeWire’s August 28th original reporting. The August 28th story did not simply predict “ChatGPT in Office.” Excel and PowerPoint add-ins were already public. RuntimeWire reported a deeper, then-unannounced review architecture found in production code: private ChatGPT assignments tied to specific Office elements native Office comments batched “Add to review” requests persistent XLSX/PPTX edits per-thread agent replies and review states OpenAI’s September 17th Word marketing now visibly shows ChatGPT: inspecting existing comments and tracked revisions adding anchored review comments preserving saved comments/redlines working through those review items inside an Office document That is new evidence relevant to the accuracy and significance of RuntimeWire’s prior reporting. The story is therefore a receipts / validation follow-up, not another announcement article. It also explicitly preserves the technical caveat: OpenAI has not confirmed that the shipping Word feature uses the exact same internal Artifact comments implementation, batch queue or protocol RuntimeWire found in August. Editorial disposition: do not merge this into the Word launch article. The launch story answers “what did OpenAI release today?” This story answers “what did RuntimeWire uncover 20 days before OpenAI publicly demonstrated this workflow?” Those are distinct stories.