feat: harden Gmail integration - #181
Closed
QueryPlanner wants to merge 1 commit into
Closed
Conversation
- Add private user-scoped Gmail REST tools and OAuth flow - Enforce mailbox, confirmation, sandbox, and revoke safeguards - Add Telegram wiring, docs, and complete regression coverage
4 tasks
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
1 participant
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, with review-driven privacy and failure handling.
Why
Replace the shared Gmail MCP path with a dedicated OAuth boundary that keeps Gmail credentials and message content isolated per private Telegram user.
How
Tests
uv run ruff formatuv run ruff checkuv run mypy .uv run pytest --cov=src(2016 passed, 1 skipped, 100.00% coverage)Related Issues
Closes #85