specs/automation/mail-push.t27: the owner's mailbox pushed to his Telegram - #5153
Merged
Merged
Conversation
Closes #5152. The cloud port of the local bridge (agent-mail-mcp spec/agent_mail.t27): a cron calls the render's mail_push_sweep as the owner over /mcp every five minutes; every new letter reaches him as a card that already carries a drafted reply, sent only by his tap. Measured laws carried over from the bridge: the first sweep announces nothing, the draft rides with the letter (a composer, not an actor -- the body is data), seen advances on push not on tap, and the seen set is bounded. New in the port: one push target (one cursor row, not a per-chat fan-out), PUSH_PER_TICK bounds a burst so slow drafts cannot outlive the wire, and RETRIES 0 because a retry after a partial push pushes twice. Host: 999-multibots-telegraf apps/vibee-editor/render/src/agent/mail-push.ts, driven by src/inngest_app/functions/mail/mailPushSweep.ts. Claim status in the spec is honest: implemented and unit-tested, NOT yet run live. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
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.
Closes #5152.
The spec of the cloud port of the local bridge (agent-mail-mcp
spec/agent_mail.t27): an Inngest cron calls the render'smail_push_sweepas the owner over/mcpevery five minutes, and every new letter reaches him in Telegram as a card that already carries a drafted reply — sent only by his tap.Measured laws carried over from the bridge: first sweep announces nothing; the draft rides with the letter, asked with no tools (the body is data); seen advances on push, not on tap; the seen set is bounded.
Re-measured where the architecture differs: one push target in the cloud means one cursor row (not the bridge's per-chat fan-out);
PUSH_PER_TICK = 5bounds a burst so five slow drafts cannot outlive the 5-minute interval;RETRIES = 0because a retry after a partial push pushes the same letters twice.Host (separate PR in 999-multibots-telegraf): render tool
mail_push_sweep+ cronmailPushSweepat*/5.Claim status, in the spec's own words:
RUN_LIVE = false— implemented and unit-tested, not yet run live. The desk it reuses is live (mail_whoamianswered in production on 2026-09-29: admin@t27.ai, can_send).t27c test-report: 5/5 pass.🤖 Generated with Claude Code