feat: add user-scoped Gmail API connector - #182
Merged
Conversation
- Replace Gmail MCP with private REST tools - Add encrypted OAuth and per-user credential isolation - Add sandbox spillover and attachment downloads - Enforce safe errors and fail-closed draft sending - Document Blacki storage and integration boundaries
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
Add the private, user-scoped Gmail REST connector and Telegram/ADK integration.
Why
Replace the earlier Gmail implementation with a bounded connector that keeps OAuth credentials and message content isolated to the connected private Telegram user. This reviewed PR supersedes the earlier open PR #181.
How
Tests
uv run ruff format --checkuv run ruff checkuv run mypy .uv run pytest --cov=src --cov-report=term-missing(2,033 passed, 1 skipped, 100% coverage)Related Issues
Closes #85
Supersedes #181