- Популярные видео
- Авто
- Видео-блоги
- ДТП, аварии
- Для маленьких
- Еда, напитки
- Животные
- Закон и право
- Знаменитости
- Игры
- Искусство
- Комедии
- Красота, мода
- Кулинария, рецепты
- Люди
- Мото
- Музыка
- Мультфильмы
- Наука, технологии
- Новости
- Образование
- Политика
- Праздники
- Приколы
- Природа
- Происшествия
- Путешествия
- Развлечения
- Ржач
- Семья
- Сериалы
- Спорт
- Стиль жизни
- ТВ передачи
- Танцы
- Технологии
- Товары
- Ужасы
- Фильмы
- Шоу-бизнес
- Юмор
your ai agent has an inbox can you trust the reply
Your AI Agent Has an Inbox — Can You Trust It?
TLDR: 1:03, 5:53 and 6:32 (live demos).
Cloudflare launched Email Sending to public beta on April 16, 2026 as part of Agents Week — and the Cloudflare Agents SDK has matching primitives for HMAC-signed email routing. In this video I wire up three Cloudflare Agents that coordinate an incident-response workflow entirely over email — then I try to hack them by forging replies, and watch the resolver stack refuse every attempt.
This is early ideation — a conceptual build to test the idea, not production code. The routing pattern is real and worth learning from; the remediation logic, the single shared-secret model, and the in-memory security log are deliberately simplified for the demo. More videos will follow with deeper dives into asymmetric-key rotation, multi-tenant routing, and real remediation integrations. This is just the exploration.
⚠️ This is a conceptual build, for entertainment and demonstration only. The code is provided AS IS, without warranty of any kind. Not intended for production use.
What You'll See in This Video:
Three Cloudflare Agents with email addresses : TriageAgent classifies inbound alerts with Workers AI, RemediationAgent proposes fixes and handles human approval, SecurityLogAgent records blocked forgery events. Each is a Durable Object with its own state.
HMAC-signed routing on every hop : X-Agent-Sig headers for bot-to-bot hand-offs, HMAC embedded in the email sub-address for human replies. The signature lives in the address because Gmail strips custom X-* headers on reply but preserves the recipient — so the signature survives the round-trip.
Live dashboard : Topology animates through workflow phases (classifying → proposing → reviewing → approving). One-click "forge a reply" button so the forgery demo stays on one screen. Forgery events flash in real time.
Two forgery attacks, two different gates : Forged X-Agent-Sig header, forged sub-address signature. Each blocked by a different resolver. The security invariant: reply-shaped mail must pass a signed resolver or it dies.
Tools & Technologies Used:
Cloudflare Workers
Cloudflare Durable Objects
Cloudflare Agents SDK (agents@0.11.2)
Cloudflare Email Routing (inbound)
Cloudflare Email Sending (outbound, public beta)
Workers AI (severity classification)
Web Crypto — HMAC-SHA256
TypeScript + Wrangler
Code & Resources:
GitHub repo: https://github.com/talkitdoit/agents-with-inboxes
Cloudflare Agents — Email API reference: https://developers.cloudflare.com/agents/api-reference/email/
Cloudflare blog — Email for Agents: https://blog.cloudflare.com/email-for-agents/
Cloudflare blog — Email Sending public beta: https://blog.cloudflare.com/email-service/
Cloudflare Email Routing docs: https://developers.cloudflare.com/email-routing/
Cloudflare Email Workers: https://developers.cloudflare.com/email-routing/email-workers/
Cloudflare Agents SDK (GitHub): https://github.com/cloudflare/agents
Cloudflare Workers AI: https://developers.cloudflare.com/workers-ai/
Cloudflare Durable Objects: https://developers.cloudflare.com/durable-objects/
HMAC — recommended reading:
Cloudflare Learning — What is HMAC?: https://www.cloudflare.com/learning/access-management/what-is-hmac/
RFC 2104 — HMAC: Keyed-Hashing for Message Authentication: https://datatracker.ietf.org/doc/html/rfc2104
MDN — SubtleCrypto.sign() (the Web Crypto API used in the demo): https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/sign
Timestamps:
0:00 - Start
0:14 - Introduction
1:03 - Live Demo: Forgery Attempt
1:29 - Framing The Solution
5:04 - Solution Deck
5:53 - Live Demo: happy path (reject)
6:32 - Live demo: happy path (approve)
6:56 - Agent Logs
7:21 - Cloudflare Objects
8:01 - Outro
8:57 - End
#CloudflareAgents #CloudflareEmailRouting #CloudflareEmailSending #DurableObjects #WorkersAI #AIAgents #HMAC #EmailSecurity #EdgeCompute #Serverless #AgenticAI #talkitdoit #AIEngineering #TypeScript #Cloudflare
Видео your ai agent has an inbox can you trust the reply канала TalkitDoit
TLDR: 1:03, 5:53 and 6:32 (live demos).
Cloudflare launched Email Sending to public beta on April 16, 2026 as part of Agents Week — and the Cloudflare Agents SDK has matching primitives for HMAC-signed email routing. In this video I wire up three Cloudflare Agents that coordinate an incident-response workflow entirely over email — then I try to hack them by forging replies, and watch the resolver stack refuse every attempt.
This is early ideation — a conceptual build to test the idea, not production code. The routing pattern is real and worth learning from; the remediation logic, the single shared-secret model, and the in-memory security log are deliberately simplified for the demo. More videos will follow with deeper dives into asymmetric-key rotation, multi-tenant routing, and real remediation integrations. This is just the exploration.
⚠️ This is a conceptual build, for entertainment and demonstration only. The code is provided AS IS, without warranty of any kind. Not intended for production use.
What You'll See in This Video:
Three Cloudflare Agents with email addresses : TriageAgent classifies inbound alerts with Workers AI, RemediationAgent proposes fixes and handles human approval, SecurityLogAgent records blocked forgery events. Each is a Durable Object with its own state.
HMAC-signed routing on every hop : X-Agent-Sig headers for bot-to-bot hand-offs, HMAC embedded in the email sub-address for human replies. The signature lives in the address because Gmail strips custom X-* headers on reply but preserves the recipient — so the signature survives the round-trip.
Live dashboard : Topology animates through workflow phases (classifying → proposing → reviewing → approving). One-click "forge a reply" button so the forgery demo stays on one screen. Forgery events flash in real time.
Two forgery attacks, two different gates : Forged X-Agent-Sig header, forged sub-address signature. Each blocked by a different resolver. The security invariant: reply-shaped mail must pass a signed resolver or it dies.
Tools & Technologies Used:
Cloudflare Workers
Cloudflare Durable Objects
Cloudflare Agents SDK (agents@0.11.2)
Cloudflare Email Routing (inbound)
Cloudflare Email Sending (outbound, public beta)
Workers AI (severity classification)
Web Crypto — HMAC-SHA256
TypeScript + Wrangler
Code & Resources:
GitHub repo: https://github.com/talkitdoit/agents-with-inboxes
Cloudflare Agents — Email API reference: https://developers.cloudflare.com/agents/api-reference/email/
Cloudflare blog — Email for Agents: https://blog.cloudflare.com/email-for-agents/
Cloudflare blog — Email Sending public beta: https://blog.cloudflare.com/email-service/
Cloudflare Email Routing docs: https://developers.cloudflare.com/email-routing/
Cloudflare Email Workers: https://developers.cloudflare.com/email-routing/email-workers/
Cloudflare Agents SDK (GitHub): https://github.com/cloudflare/agents
Cloudflare Workers AI: https://developers.cloudflare.com/workers-ai/
Cloudflare Durable Objects: https://developers.cloudflare.com/durable-objects/
HMAC — recommended reading:
Cloudflare Learning — What is HMAC?: https://www.cloudflare.com/learning/access-management/what-is-hmac/
RFC 2104 — HMAC: Keyed-Hashing for Message Authentication: https://datatracker.ietf.org/doc/html/rfc2104
MDN — SubtleCrypto.sign() (the Web Crypto API used in the demo): https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/sign
Timestamps:
0:00 - Start
0:14 - Introduction
1:03 - Live Demo: Forgery Attempt
1:29 - Framing The Solution
5:04 - Solution Deck
5:53 - Live Demo: happy path (reject)
6:32 - Live demo: happy path (approve)
6:56 - Agent Logs
7:21 - Cloudflare Objects
8:01 - Outro
8:57 - End
#CloudflareAgents #CloudflareEmailRouting #CloudflareEmailSending #DurableObjects #WorkersAI #AIAgents #HMAC #EmailSecurity #EdgeCompute #Serverless #AgenticAI #talkitdoit #AIEngineering #TypeScript #Cloudflare
Видео your ai agent has an inbox can you trust the reply канала TalkitDoit
Комментарии отсутствуют
Информация о видео
21 апреля 2026 г. 1:46:49
00:08:58
Другие видео канала




















