feat(blog): add 'Your agent's inbox is storage, not transport' - #1007
Merged
Conversation
Argues inbox polling is a transport problem, not a discipline problem, and lays out e2a's four inbound delivery channels (signed webhooks, WebSocket with no public URL, REST polling, MCP) plus e2a listen for the laptop case.
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
Adds today's blog post, "Your agent's inbox is storage, not transport", following the existing blog pattern:
web/src/app/blog/inbox-is-transport/page.mdx- the post (~500 words)web/src/app/blog/posts.ts- registry entry (date 2026-09-05, 3 min read); sitemap picks it up automaticallyAngle
An agent that polls its inbox every 30 minutes is checking a PO box - that's a transport problem, not a discipline problem. Webhooks fix the latency but demand a public HTTPS endpoint, so agents on laptops, homelabs, or behind firewalls fall back to polling. The post lays out e2a's four inbound delivery channels (signed webhooks with
construct_eventone-call verification, WebSocket with no public URL and unread-drain on reconnect, REST polling kept on purpose, MCP tools) pluse2a listenbridging to a local handler / OpenAI Responses endpoint. Every claim grounded in the repo README; no competitor named.Verification
npm run build(static export) succeeds; the new page prerenders at/blog/inbox-is-transport/blogNot merged - review and merge when ready. Note: prod serves a pinned release, so the post won't be live until a release is cut and promoted.