Repository navigation
feat(hub): mailbox send to an agent triggers its deployment and keeps the person's Sent copy (CL-8437) - #871
Merged
Merged
Conversation
… the person's Sent copy (CL-8437) A person's message to an agent now goes through their own mailbox: the Sent copy is durable, and the hub's deliver seam hands the frame to stock's workflow trigger route instead of the mail persist path, which has no endpoint for a human sender. The mailbox sender address is the stock human form <refId>@<domain>, so the Sent copy and the agent's reply share one identity. The chat UI reads both sides from the mailbox and the localStorage sent cache is gone.
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.
A person's message to an agent is now ordinary mail from their own mailbox, so it leaves a durable Sent copy.
Hub (Corbits block only)
senderAddressForreturns the stock human address form<principal.refId>@<domain>(drizzle lookup onprincipal), so the Sent copy and the agent's reply share one identity.deliver(newapps/hub/src/mailbox-send.ts) splits recipients: a run address is fired through stock's ownPOST /api/tenants/:t/workflows/:runId/mail(replaying the caller's session against the hub app, so grants and signing are stock's); everything else keeps thepersistMailpath. Failures are reported throughreportErrorand thrown, never swallowed.Web
startChat/replyInChatpost to/mailbox/me/inbox/sendwithto: [agentAddress]andinReplyToon replies.workbench.chat.sent.<tenantId>localStorage cache is gone; a chat is now every mail turn on one agent's run, read from the mailbox (Sent+INBOX), and a chat's id is the agent's run id.Known gap
@corbits/mailbox(pinned 8cb5db96) does not list theSentfolder:LIST_FOLDERSinmount.tsisINBOX | Archive | Trash, soGET /me/inbox?folder=Sentanswers 400 and the person's own turns will not render until the library allows it. Send, Sent persistence and the trigger path are complete.