Add Google Drive native document sessions - #296
Draft
ndisidore wants to merge 2 commits into
Draft
Conversation
ndisidore
marked this pull request as draft
August 21, 2026 17:48
ndisidore
force-pushed
the
feat/gk-google-drive-native-sessions
branch
from
August 21, 2026 22:46
c00730f to
2f03ae2
Compare
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.
This extends in-scope Google Drive bindings with read-only nested sessions for native Google Docs and Google Sheets. Agents can open a native file only after a fresh metadata lookup, immutable account/shared-drive/file scope enforcement, and observation authorization; Docs return Markdown, Sheets retain bounded A1 range reads, and each child capability is independently disposable. Account and exact-file grants gain the content-specific read scopes while shared-drive grants keep
drive.readonly, and no Drive path gains writes, blob extraction, or shortcut traversal. The change also gives Docs requests a 30-second timeout and 10 MiB successful-response ceiling, preserves Sheets' existing bounds, redacts provider prose while logging bounded reason codes, and adds coverage for scoping, observer ordering, OAuth upgrades, RPC ownership, streamed limits, and agent-facing declarations.