Skip to content

Fix Google Workspace creation routing#329

Open
Aismit wants to merge 1 commit into
mainfrom
aismit/FS-google-workspace-write-routing
Open

Fix Google Workspace creation routing#329
Aismit wants to merge 1 commit into
mainfrom
aismit/FS-google-workspace-write-routing

Conversation

@Aismit

@Aismit Aismit commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator

What changed and why

The current Google Drive plugin bundle routes generated Google Slides decks through local PPTX creation and import_presentation by default. In the failing ChatGPT traces, that import path returned a blocked/redacted/unusable result, and the model kept rediscovering or retrying import instead of using the connector-native creation path already documented elsewhere in the plugin.

This updates the source Google Drive plugin to make generated net-new Slides use native _create_file plus _batch_update_presentation when those actions are available. Local .ppt, .pptx, and .odp conversion still uses import_presentation; it is just no longer the default for generated decks.

The same routing contradiction existed for Docs: the Google Docs skill supports connector-native blank/basic creation, but the Drive router still described new Docs as mandatory DOCX import. The router now delegates that choice to the Docs skill.

The Google Drive plugin version is bumped from 0.1.6 to 0.1.7 so the corrected bundle can roll forward.

Previous behavior

Example old Slides flow:

  1. User asks ChatGPT to create a Google Slides deck from scratch.
  2. The plugin routes to Presentations/PowerPoint local PPTX authoring.
  3. The model attempts import_presentation to convert the PPTX to native Slides.
  4. If import is blocked, unavailable, or returns no usable Slides URL/id, the model can loop on import/tool discovery and eventually tell the user it cannot create the live deck.

New behavior

Happy path:

  1. User asks for a generated Google Slides deck.
  2. The Google Slides skill reads the new-deck reference.
  3. It creates a native Google Slides file with _create_file.
  4. It populates the deck with _batch_update_presentation.
  5. It verifies the final deck through connector readback and thumbnails.

If the user provides a .ppt, .pptx, or .odp, import remains the correct conversion path. If that conversion action is unavailable, the skill now stops for that file-conversion task rather than spinning. For generated deck tasks, it falls back to native create/update when available.

Validation

  • git diff --check
  • python3 -m json.tool plugins/google-drive/.codex-plugin/plugin.json
  • rg -n "only currently supported|mandatory local|Do not create a blank Google Slides deck|Do not create a blank Google Doc directly|required local Presentations|PPTX-import path" plugins/google-drive/skills/google-drive plugins/google-drive/skills/google-slides

@Aismit Aismit requested a review from a team June 10, 2026 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant