Build1 publisher2 min readPublished
OpenAI's gated artifact comments hand ChatGPT a file path and a thread id per assignment
The Word sidebar rewrites what you select. The addressed, batched review queue RuntimeWire found in OpenAI's shipped desktop client 20 days earlier works differently, and it is still behind a rollout gate.
The Engineer · Build desk
What happened
- OpenAI added ChatGPT to Microsoft Word on September 17th, completing an add-in lineup that now covers all three of Microsoft's core Office creation tools.
- OpenAI said in a post on X that the Word integration is available on every ChatGPT plan, including Free, subject to each plan's usage limits.
- RuntimeWire had examined the production app.asar shipped in Windows package OpenAI.Codex_26.825.4187.0 and found a feature called Artifact comments sitting behind a rollout gate.
- That interface let a user select a range, chart, slide or shape and choose "Ask ChatGPT for a change", with an "Add to review" action that accumulated assignments and sent them to the agent as a batch.
- OpenAI says PowerPoint is not part of the desktop Work flow at launch, even though ChatGPT for PowerPoint is already available as a Microsoft add-in.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- cost Word drafting draws on the shared allowances Codex and other premium features spend from, so a team rewriting long reports in the sidebar reduces what its coding agent has left to spend.
- decision OpenAI no longer needs to win the 365 procurement argument to reach Word users, because a company can standardize on Microsoft Office and still have ChatGPT's interface beside the document.
- constraint OpenAI's documentation says complex formatting, charts and tables may require manual correction, which limits how far a batched queue of chart and cell-range assignments can run without a human checking each result.
- contradiction Both accounts of this story come from RuntimeWire, and RuntimeWire itself says the public rollout confirms the direction without confirming every unreleased component it found in the August package.
In Word, you select a passage and ask the sidebar for a revision [3]. In the gated desktop feature, the client packaged the target, the file path, a thread identifier and any available preview into a dedicated `artifact_comment` turn, then instructed ChatGPT to address every thread, make the requested edits and return one structured `artifact-comment-reply` for each assignment [8]. Replies were routed back into their corresponding threads, and the interface tracked pending, unread, resolved and reopened states, with final resolution left to the user [9].
Each assignment therefore has an identity and a lifecycle. RuntimeWire, which found the code, says the still-gated review queue points to comments becoming task dispatch for agents [27]. The same implementation carried a second comment system that wrote native comments into the Excel and PowerPoint files, while the ChatGPT assignments stayed private and were not exported with the Office document [10].
The write path is the part I would call good engineering. PowerPoint changes were serialized back into PPTX bytes through bundled OpenXML infrastructure [11]. Excel changes went 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 [12]. Those three cases exist because the file is open while the agent works on it: OpenAI's own description has Codex inspecting and updating sheets, formulas, values, formatting and charts in an open workbook [13].
What shipped in Word is narrower. The add-in works with the document currently open, cannot independently inspect unrelated local files, and keeps its conversations separate from the user's main ChatGPT history, with memory not carrying over [17].
Then billing. OpenAI's pricing documentation says Word usage depends on the selected model, document size and task, and draws from shared allowances used by Codex and other premium features on applicable plans [20]. Business and Enterprise customers get a free preview of GPT-5.6 Sol in Word from September 17th through September 30th, with preview activity excluded from their normal usage limits [19]. That is 14 days [23]. OpenAI plans to enable the add-in by default from October 1st, the day after the meter starts again [18][24]. Workspace administrators can disable it in OpenAI's admin console, and Microsoft 365 administrators keep control over installation and access [18].
RuntimeWire reported on August 28th that the gated system could collect several requests into a review queue, let ChatGPT edit the underlying Office file and return a separate reply to each assignment [6]. The Word add-in arrived 20 days later [2]. On that record I would treat the queue's shape as well documented and its release schedule as unknown.
What to watch
- Whether the Artifact comments gate opens to general availability, and which Office application gets the review interface first.
- Whether GPT-5.6 Sol stays available in Word for Business and Enterprise once the preview period ends.
- Whether Microsoft changes add-in policy for a ChatGPT-branded assistant sitting beside its own Copilot.