Trigger.dev’s Post

Most AI chat backends run every conversation through one shared server, with a hard timeout on every request. chat.agent gives each conversation its own real machine instead. It boots on the first message and runs for as long as the work takes. The turn is just a task: streamText on the server, useChat on the client, no API route in between. The session outlives the process serving it. Refresh mid-response and the stream replays from where you stopped reading. Close the tab, come back a week later, it’s still there. A turn has no timeout. And a suspended turn (waiting on a human approval, say) isn’t billed, so it can sit open for days for free.