Repository navigation
feat(google): add read-only Gmail across connector surfaces - #493
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
adampeterhiggins
force-pushed
the
ah/add-gmail-google-connector
branch
from
October 26, 2026 12:08
ad6307d to
b62af78
Compare
adampeterhiggins
marked this pull request as ready for review
October 26, 2026 12:22
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.
The fork's Google connector supports Drive and Calendar but cannot supply Gmail context. Add read-only Gmail conversations to the same environment-owned connection, including native Gmail search syntax, bounded message snapshots, citations, thread links and change watches.
Web and desktop gain a Gmail picker tab and searchable palette actions. Mobile gains source tabs, Gmail search and conversation chips through the existing attachment, link and citation paths. Agents and scheduled tasks use the existing shared services and MCP tools (
search_google_fileswithsource: "gmail",read_context_link, and link/watch tools). Existing RPC permissions and environment routing apply to local and remote connections; providers consume the same context snapshots.When Google reports a missing scope, the error now has its own
permissionreason and asks the user to reconnect, rather than saying the document cannot be read. A disabled or not-yet-propagated API (SERVICE_DISABLED) shows Google's own explanation. Combined searches and the People directory still fall back silently.Enable the Gmail API and reconnect existing Google connections to grant
gmail.readonly. Drive and Calendar searches remain available without Gmail permission. Attachments stay in Gmail; snapshots contain attachment names. HTML-only messages include bounded HTML source. Hexadecimal Gmail conversation links are supported; opaque browser-only links must be found using search first. Update the user guide and fork differences.Validation:
vp run check:changedafter rebasing onmain: format, both Knip passes, GraphQL generation and typechecking of all 30 affected packages pass. Server, contracts and link tests pass (174 tests).main: lint reportsno-array-index-keyinGoogleFileDetails.tsx(the lines are unchanged here), andCommandPalette.focus.browser.test.tsxfails to import because itsuseThememock lacksgetRenderedAppearance.gmail.readonly). The Gmail tab, placeholder and palette actions render. The Gmail tab shows the reconnect message, confirmed against Google's realACCESS_TOKEN_SCOPE_INSUFFICIENTresponse. After reconnecting withgmail.readonly, the Gmail tab lists real conversations. The mobile app was not exercised.Model: gpt-6.1-sol, then Claude Opus 5.5 for verification and the permission fix. Harness: Codex and Claude Code in T3 Code.
🤖 Generated with Claude Code