Repository navigation
feat(replies): send a reply through the Gmail it came in on, after your yes - #611
Merged
Merged
Conversation
…ur yes
Send on the Replies page (Undo for a few seconds) or Keep in Gmail drafts,
for admins, when the email came in through a Gmail connection an admin let
send: in the email's thread, without citations, never with something left
to confirm. POST /recordings/{id}/reply/send needs a signed-in session;
agents ask with the MCP tool send_reply, which waits in Approvals and sends
the text it showed. Threat model updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Xa7Hz2SLg6sNrGksMEzBaz
…-4cz7ul # Conflicts: # threat-model.md
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.
Requested by Adeel · project thread
Description
Before: an email reply (#565, #604) could only be copied or opened in the person's own mail app.
After: when the email came in through a Gmail connection an admin let send (write), the Replies page has Send and Keep in Gmail drafts. The reply goes from that mailbox, in the email's thread, without its citations. Send waits a few seconds with Undo, and the status line then says who sent it, with an Open in Gmail link. A draft with a
[to confirm: …]mark left, or without a valid To address, can't be sent, and the button says why. Agents can't send: the MCP toolsend_replyfiles an approval that waits in Approvals with all of the message shown, and approving it sends exactly the text that was approved (a later edit means asking again).How:
responder.outgoing/ask/sendreuse the Gmail write half from #552 (connection_tools.outgoing_mail,send_mail,mail_preview). NewPOST /recordings/{id}/reply/sendaccepts only a signed-in web session (API keys and apps get 403 and are pointed tosend_reply).ai_tools._carry_outhandles thesend_replyapproval. Reply statuses addsavedandsent, withsendssaying whether the email's connection may send.Motivation and Context
The last step of the email responder's first version: drafts, then the page, then sending after the person's yes.
Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.changelog.d/send-reply.md.Done questions (AGENTS.md)
send_replyover MCP files the approval. Sending itself is the person's pick.sentfield on existing rows. Nothing to migrate.test_replies.py, 2 new page tests,docs/email-replies.md"Sending",docs/mcp.md, requirements rows,make openapioutput.Local checks:
test_replies.py,test_mcp.pyandtest_approvals.py(41 passed), tsc, the page's jest suite (12 passed),ci/check_requirements.py,ci/validate_threat_model.py --base origin/main, andmake openapi(no diff).Generated by Claude Code