Dispatch
Trigger.dev launches Chat Agent: one durable machine per conversation, where 1 in 20 turns runs over 36 minutes
Launched on Product Hunt 2026-08-12, Chat Agent gives each conversation its own machine that sleeps when idle and resumes where it left off, removing request timeouts, lost memory between turns, and the usual database/Redis/job-queue scaffolding. It drops into existing AI SDK code (streamText server-side, useChat client-side) and adds automatic tracing with cost and token metrics; users can refresh mid-response. The operational number worth stealing: Trigger.dev says it has run in production since June across millions of sessions and that 1 in 20 turns runs longer than 36 minutes — which is precisely why serverless request/response chat breaks for agents. Apache 2.0 and self-hostable.
Source
↳ Follow the thread