Google Drive plugin can create/read Google Docs but exposes no document-edit action

What version of the Codex App are you using (From “About Codex” dialog)?

ChatGPT desktop 26.901.22334 (build 7746); bundled codex-cli 0.153.0

What subscription do you have?

ChatGPT Business

What platform is your computer?

macOS — Darwin 25.6.0 arm64

What issue are you seeing?

In the ChatGPT/Codex desktop app, the installed and enabled Google Drive plugin can create a native Google Doc and read it back, but it exposes no action capable of editing Google Doc content. The available connector surface includes create_file and get_document, but no batch-update, insert-text, replace-text, or equivalent Docs content-write action. As a result, the agent can authenticate, create, and read the document, then must stop before inserting or editing any text. Reinstalling and reconnecting the plugin does not change this. No API error is produced because the required write tool is absent from the task tool inventory. A related Sheets report exists as #24373; this report is specifically for Google Docs.

What steps can reproduce the bug?

1. Install and enable the curated Google Drive plugin in ChatGPT/Codex desktop.
2. Connect a Google account and grant the requested read/write access.
3. Start a new Codex task and explicitly invoke Google Drive.
4. Ask: “Create a dummy Google Doc, read it back, edit it, and write it back.”
5. Observe that the plugin successfully creates a native Google Doc.
6. Observe that get_document successfully reads the new document and returns its document ID, revision ID, tab ID, and body.
7. Inspect the Google Drive actions exposed to the task: no Google Docs batch-update or other content-editing action is present.
8. The agent cannot insert or replace text, despite successful authentication and file creation.

What is the expected behavior?

When Google Drive is connected with write access, the plugin should expose the Google Docs content-write action documented by its own workflow (for example, batch_update_document) so Codex can insert, replace, and delete text, then verify the result by reading it back. If Docs editing is intentionally unsupported, the plugin UI and documentation should state that clearly before installation.

Additional information

Plugin inspection showed it is installed, enabled, user-enabled, and has no unresolved app dependencies. The app-specific permission inherits the account default (“Allow low-risk actions”). Authentication is demonstrably working because create and read operations both succeed. This does not involve the Google Drive for desktop application. No document URL, account ID, or session transcript is included here to avoid exposing private data.

The report names no repository files or tests; start by locating the curated Google Drive plugin's action inventory and the get_document/create_file entry points. Confirm where Docs content-write actions are exposed, then verify that an authenticated task can insert or replace text and read the updated document back.