AGNTCon + MCPCon Europe 2026

MCP's new Tasks primitive makes tool calls asynchronous: a request returns a durable handle now, and the result arrives later. That's the right model for work that runs for minutes or hours, like ETL jobs, deep research, or batch reasoning, but the spec leaves the hard parts to implementers.
Where does in-flight work live? How does a task survive a restart? How do you deliver a result exactly once and let multiple clients subscribe to it?

This talk argues that an append-only event log is a natural backend, because a Task is a state machine and a state machine's history is just an ordered log of its transitions. We walk a concrete, vendor-neutral implementation: creation, status, and completion become events, recovery becomes replay, and the server can go stateless, lining up with MCP's roadmap. We dig into the failure modes that bite in production: orphaned tasks, duplicate side effects, and at-least-once versus exactly-once delivery, plus the gaps the 2026 roadmap is still closing around retry and expiry.

You'll leave with a reference architecture you can build on any log or queue, and an honest view of what Tasks gives you today and what it doesn't yet.