← Plugin catalog
Productivity

Word in Chat

Alex Pickett v0.1.4

Publisher description

From the marketplace listing

Open DOCX documents in a page-layout editor. Read, search, and rewrite text with chat while keeping existing styles. Apply formatting, edit tables, and adjust page layout. Highlight text and choose Add to chat. Review comments alongside the document. Download an edited copy of an uploaded attachment. Host-managed files save through the host when writing is permitted.

Language: English · Automatically detected from descriptions.

Publisher keywords

Search terms declared by the publisher.

Files & skills

File archives

Plugin package10 files · 37.4 KBBrowse files →
Skill instructions
word-editor4.8 KB

View saved version →

---
name: word-editor
description: View and edit Word .docx files in the Word editor. Use when the user wants to see, review, or change a .docx file, or when a .docx file is open in the Word editor.
---

# Word editor

The Word editor shows a .docx file with Word page layout. The user and you edit the same open document. Host-managed files autosave. Uploaded attachments are edited copies: use **Download DOCX** to keep the result.

## Show a document

1. In ChatGPT web or mobile, attach a DOCX and call `open_word_document` with ChatGPT's file object: `download_url`, `file_id`, and optional `file_name` and `mime_type`. Copy these values from the attachment. With the locally installed plugin, its opener instead accepts `{"file":{"name":"report.docx","resourceUri":"file:///absolute/path/report.docx"}}`. Host file viewers use `open_word_resource` with the granted resource URI.
2. Check the editor panel or its model context to confirm that the file opened. The panel shows the file name, save status, and chat connection status. `open_in_codex` is also available, but its `queued` acknowledgement alone does not confirm that the host launched the editor.
3. An absolute file link is useful for locating the document, but the host can route attachment and review links to its built-in document preview. That preview supports annotations; the Word editor has an editing toolbar.

If tools or editor context are unavailable, inspect the existing Word panel through the `mcpapps` browser backend when available. Report its actual connection status. The local mock host tests the editor bridge separately and saves changes in memory. Its success does not verify a live Codex session.

## Edit the open document

The MCP server advertises `word_document_*`. They run against the open editor through its live connection. Each call requires the `editorSessionId` returned by the opening tool. Preserve this private identifier; use the ID for the intended file. Confirm opening with `word_document_inspect` using that ID. The editor keeps that ID when reconnecting. Opening another document supplies its own ID.

Choose the path from the request:

- **Wording edits:** call `word_document_project` in `text` mode, then `word_document_patch` with the changed line ranges and the projection's revision. These two calls are the complete content path. Text mode is the default and returns compact line references. Keep the same story, cursor, and window limits on the patch. Existing styles remain in place.
- **Formatting or layout edits:** inspect the document, then call the individual edit tool using the observed revision and references. For example, `word_document_format_paragraph` sets paragraph alignment or style. Each tool publishes its own input schema. `inspect` with `kind: "read"` returns detailed formatting; `context` returns compact text across stories. Request spatial information only for page geometry tasks.
- **Heading or list structure edits:** explicitly use `md` mode with project and patch, or the relevant detailed edit operation. Markdown markers can change those structures.

When a result reports `needs_sync`, or asks you to inspect again, refresh the text projection or inspection before the next edit.

Do not save the file yourself. Do not write to the .docx file with other tools while it is open in the editor, because the user can have unsaved edits there.

After an edit, report the returned save status. Uploaded copies remain in the editor until the user chooses **Download DOCX**. A host-managed file reports **Saved** after its write succeeds. Confirm text and formatting in the exported or reopened DOCX when verifying the result.

## Requests that use another service

Email delivery uses an email service or the user's mail app. Software purchases use the vendor's checkout. Drive account searches use a connected Drive service. Explain which service the request needs. Word in Chat opens, inspects, edits, and exports the selected DOCX.

## Work with highlighted text

On mobile, the user can turn on **Select text**, drag across a passage, and tap **Add to chat**. When active, the button says **Selection on**. Tap **Selection on** to resume scrolling. The user can also highlight text and click **Add to chat**, or right-click the selection and choose **Add to chat**, the first menu item. The editor adds the selected text, revision, and exact run ranges to model context. Use these ranges when the user says "this section" or "the highlighted text." For wording changes, refresh the text projection and use its compact block references to locate the selected paragraph. Change only the selected text within that line. For detailed operations, inspect the selected references before editing. The library reports up to 64 text ranges. If the context reports `possiblyTruncated: true`, inspect the surrounding section and establish the full selection before a bulk rewrite.
wordinweb-documents2.23 KB

View saved version →

---
name: wordinweb-documents
description: Read and edit DOCX documents open in Word in Chat, including text, formatting, tables, page layout, and comments.
---

# Edit the open document

Use this skill for document operations in the Word in Chat editor. Use the
`word-editor` skill to open a DOCX and work with highlighted text.

Every document tool call requires the `editorSessionId` returned by the opening
tool. Use the session for the intended file. When the editor
reconnects, keep the same session ID. Opening another document supplies its own ID.

## Choose the editing path

- For wording changes, call `word_document_project` in `text` mode, then
  `word_document_patch` with the returned revision and changed line ranges.
  Keep the same story and projection window. Existing styles remain in place.
- For formatting, tables, page layout, or comments, inspect the target with
  `word_document_inspect`, then call its individual edit tool, such as
  `word_document_format_paragraph` or `word_document_comment_run`. Each tool
  exposes its own operation fields, revision, and editorSessionId.
- For heading or list structure changes, use `md` mode explicitly with project
  and patch, or use the relevant structured operation.

Read [references/inspect-edit.md](references/inspect-edit.md) for inspection,
text patches, and individual edits. Read
[references/interface.md](references/interface.md) for operation fields and
reference types. Use each runtime tool schema as the authority for a call.

## Keep edits scoped

1. Locate the requested text or object in the current document.
2. Use the revision and references returned by the latest relevant read.
3. Apply related changes in one bounded call.
4. Refresh the projection or inspection after a stale-revision error.
5. Re-inspect after structural changes before using new references.
6. Check the affected text, formatting, or page geometry.
7. Confirm the returned save status. Host-managed files show Saved. Uploaded attachments show Edited copy ready to download; the user chooses Download DOCX to export the result.

Use compact text projections for prose. Request detailed formatting or spatial
inspection when the requested edit needs it. Preserve content and formatting
outside the user's requested change.

Referenced files: 3

Publisher release notes

Expose each document edit as an individual tool with its description, input schema, and annotations. Give the uploaded-file and host-file openers distinct display names. Keep the compact project-and-patch path for wording edits.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
Alex Pickett
Keywords
See publisher keywords
Declared availability
No country restrictions declaredPublication setting in this package; live availability may differ. This is not the publisher's country.
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Publisher review scenarios
5 positive · 3 negativeDeclared scenarios, not independently verified test results.

Declared capabilities

  • Interactive
  • Read
  • Write

Package observed Oct 9, 2026.

Technical details
First seen
Oct 9, 2026 · 18:00 UTC
Last seen
Oct 9, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6ac409ab2018819185f146d60ae60640

Download plugin data (JSON)

Before you connect Word in Chat

How do I connect it?

Open the publisher's marketplace listing to check current availability and follow its connection instructions. This directory does not install plugins. Check the requested access and any account requirements before connecting.

Check marketplace availability ↗

Does it require paid access?

We have not established the pricing or subscription requirements for this plugin. An absent price does not mean free access.

Compare researched pricing and access models →

How can I evaluate it?

Check the declared skills and available files, then try a small task whose result you can verify. Our archived descriptions and instructions establish publisher claims, not tested runtime quality. Review sources and coverage limits.