OpenAI’s Windows Client Contains Gated Office Task Threads for ChatGPT

OpenAI’s Windows ChatGPT and Codex client contains a gated system that can turn comments on Excel and PowerPoint elements into threaded assignments for ChatGPT. The implementation can pair edits to the underlying Office file with a reply in the relevant thread, pointing to a workflow built for delegated review rather than one-off prompts.

The feature is present in the Windows package identified as OpenAI.Codex_26.825.4187.0, with internal application version 26.825.32147. It sits behind a numeric feature gate, so its inclusion in a production package does not show that ordinary users can access it. The implementation was absent from archived builds through version 26.820.71523 and present by 26.825.32147.

A comment can become a job

Users can target an Excel range or chart, or a PowerPoint slide, shape or other presentation element. The client supports conventional Office comments that are saved into the file, alongside a separate class of persistent ChatGPT-only threads that are not exported with it. Both appear together in one sidebar, despite having different persistence behavior.

• Several agent requests can be accumulated and sent as one review batch instead of individually.
• Each request carries structured task and target information, allowing the agent to associate work with a particular comment thread.
• The agent is required to address every assigned thread and produce one structured reply for each one; the user, not the agent, controls whether the thread is resolved.

Two layers over the same file

The native layer is designed to travel with the document. PowerPoint comments are serialized back into PPTX files. Excel comment operations move through a durable workbook-update path and are exported into a new XLSX file. That means a recipient of an exported file may receive the ordinary Office discussion without receiving the private ChatGPT instructions and responses attached to the same object.

The private layer is more like an internal agent-work queue. It can retain a conversation reference, local artifact path, thread identifier, target metadata and available text or image preview. The implementation also anticipates requests arriving while work is already underway, treating them as additions that must be completed before the agent turn ends.

The rollout questions are operational

OpenAI’s public materials describe file previews, selection-based revisions, separate Excel and PowerPoint add-ins, and browser-page comments in Codex. They do not describe this threaded Office review system, its private comment layer, its batching mechanism or the reply-routing protocol. The examined implementation shows native persistence for Excel and PowerPoint, but not an equivalent path for Word, PDFs, CSV, TSV, HTML or notebook files.

The sharper issue is governance. Native comments can be authored from the signed-in user identity, including an email address, raising a metadata question for files shared onward. Private assignments may include file paths, identifiers, target details and workspace context. The client code does not establish retention periods, whether administrators can disable the feature separately, or how these threads would appear in enterprise compliance records.