Fix Google Workspace creation routing#329
Open
Aismit wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed and why
The current Google Drive plugin bundle routes generated Google Slides decks through local PPTX creation and
import_presentationby 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_fileplus_batch_update_presentationwhen those actions are available. Local.ppt,.pptx, and.odpconversion still usesimport_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.6to0.1.7so the corrected bundle can roll forward.Previous behavior
Example old Slides flow:
import_presentationto convert the PPTX to native Slides.New behavior
Happy path:
_create_file._batch_update_presentation.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 --checkpython3 -m json.tool plugins/google-drive/.codex-plugin/plugin.jsonrg -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